Skip to main content
PUT
Replace assigned tools

Authorizations

Authorization
string
header
required

API key (fam_..., created under Settings → API Keys) or an OAuth 2.0 access token (fam_at_...). REST operations also require API Access for the credential's workspace. Keys can be restricted to scopes such as assistants:read, calls:write, campaigns:write, automations:read, dashboards:read, dashboards:write, leads:write, segments:write, loop:read, loop:write, phone_numbers:write, sip_trunks:write, knowledge:write, voices:read, billing:read, settings:write, platform:read, platform:write; a *:write scope implies the matching *:read. Automation and dashboard endpoints also accept the legacy calls:* scope. Keys without scope restrictions have full access within the workspace's available capabilities.

Path Parameters

id
string<uuid>
required

Assistant ID.

Body

application/json
tool_ids
string<uuid>[]
required

Complete target set of tool IDs to assign.

expected_revision
integer
required

Toolset revision returned by GET /assistants/{id}/tools.

Required range: x >= 1

Response

200 - application/json

The new set of assigned tools and its new revision.

data
object[]
required
meta
object