lead_review

Call lead_review.respond

Send a lead their result page and video answer — 'send them their results', 'let that applicant see their page', 'release the answer to them'. Release a lead's result page and the recorded video answer TO THE LEAD. This is visible to someone outside the workspace and cannot be taken back. Calling it raises the approval card showing which reply would go out, which is the operator's confirmation, so it can still be refused after you call it. Never say a lead has been answered unless the result says so. Not for marking the reply approved inside the review queue — that is lead_review.approve. Over the API it answers in two calls: without confirmation_id it proposes — says what would happen, returns a confirmation_id and changes, spends and sends nothing; the same arguments again with that confirmation_id, on a member's own API key, do it.

Every result names the workspace it ran in. Say which workspace the answer is about. When the account has more than one workspace and none is selected, this tool refuses with workspace_ambiguous and lists the choices — offer them, never pick one.

post/api/v1/tools/lead_review.respond

Request

  • Base URL: https://app.goosybear.ai
  • URL: https://app.goosybear.ai/api/v1/tools/lead_review.respond
  • Auth: HTTP bearer

Headers

x-request-idstring

Your own id for this request, echoed back and recorded on the audit trail. 1–128 characters from A–Z a–z 0–9 . _ : -, starting with a letter or digit; anything else is replaced by a generated id.

Request body

response_idstring uuid required

The reply to release.

video_asset_idstring uuid required

The recorded video reply to release with it. Recording it is a browser action the operator takes on the review surface — use the asset id that surface produced, never a guess.

confirmation_idstring uuid

Omit to propose: the first call says what would happen, returns a confirmation_id and changes nothing. To go ahead, send the same arguments again with that confirmation_id, on a member's own API key; a service account's key can propose but never confirm.

workspacestring

Which workspace to run in — its slug. Omit to use your default. With more than one reachable workspace and no default, the call is refused and the choices are listed.

Response

The call was admitted and dispatched. ok says whether the tool succeeded — a refusal the tool itself produced is still a 200, exactly as it is a successful JSON-RPC result over MCP.

OR

Changes

No recorded changes to this operation across all 4 revisions of this API.