SMAO API Documentation
Public APIAssistants

Delete an assistant

DELETE
/assistants/{assistant_id}

Fails with 409 conflict while the assistant is in use: a website widget references it, an open chat is answered by it, one of its calls is still running, or a start-call node in one of the organization's analyses places its calls with it (the message names those analyses). Enterprise assistants, and lines managed for you by the platform, cannot be deleted at all and always answer 409 conflict.

Authorization

bearerAuth
AuthorizationBearer <token>

API key in the Authorization: Bearer <key> header. Keys are created in the SMAO dashboard (Settings → API Keys).

In: header

Path Parameters

assistant_id*string
Match^[a-f0-9]{24}$

Response Body

application/json

application/json

application/json

application/json

application/json

application/json

application/json

application/json

application/json

curl -X DELETE "https://example.com/assistants/65f8fa6f1a9d8e0012ab34cd"
{  "data": {}}

Update an assistant PATCH

Partial update - only included fields are changed. `phone_number` and `carrier` are read-only and cannot be updated via this endpoint. Cross-resource refs are validated to belong to your organization.

List selectable voices GET

Returns the voices the authenticated instance can assign to a new assistant or select during a voice change. Legacy voices retained by existing assistants and voices reserved for internally managed lines are not returned.