Skip to main content
PATCH
Update Built-in Tools

Authorizations

Authorization
string
header
required

Your API key (ta_live_…) from Settings → API keys, sent as Authorization: Bearer <key>. Keep it on a server: it can message every customer you have. A key is full, build or read-only; a request its level does not allow is refused with 403.

Headers

Thinnest-Workspace
string

Developers only: the customer workspace this request acts in — its org_… id from POST /customers. Leave it out to act in your own workspace.

Example:

"org_3fKq9TzQ1mN8vB2xR7cLpA"

Path Parameters

id
string
required

The agent's id (ag_…).

Body

application/json

Send at least one field. Changes apply in order (tools, recall, verifyByCode, handOver) and stop at the first refusal; what came before it is kept, and the refusal says so.

tools
object

Tool id to true or false. Switchable: capture_lead, escalate_to_human, schedule_callback, call_them_now, send_whatsapp, reply_by_email.

recall
enum<string>

How much of a recognised customer's history the agent may use: trusted (all of it), two_tier (the default) or verified (only once they are confirmed).

Available options:
trusted,
two_tier,
verified
verifyByCode
boolean

Confirm a customer with a one-time WhatsApp code instead of their email.

handOver
object

Fields you leave out keep their saved value.

Response

The tools as saved, with any notes.

agent
string
required

The agent (ag_…).

tools
object[]
required

Searching the web. Shown, never switchable here.

recall
enum<string>
required

How much of a recognised customer's history from other channels the agent may use.

Available options:
trusted,
two_tier,
verified
verifyByCode
boolean
required

Whether a customer is confirmed with a one-time WhatsApp code rather than their email.

handOver
object
required

How a hand-over to a person happens.

messages
string[]
required

Notes from the changes applied, in order; often empty.