Delete an agent
Authentication
Path parameters
UUID of the agent to delete. An id from another workspace answers 404; a value that is not a UUID answers 400.
UUID of the agent to delete. An id from another workspace answers 404; a value that is not a UUID answers 400.
Deletes an agent. The steps run in this order:
active campaign that uses the agent is set to paused.delete version is recorded.The agent’s history (calls, conversations, change versions) is kept.
Side effects. Pauses campaigns, calls the voice engine (unbind numbers, delete agent), disables the agent’s widgets, posts an in-app notification and writes an audit entry. Inbound calls to numbers that pointed at the agent stop being answered until another agent is assigned.
Idempotency. Safe to retry: a second call answers 404 AGENT_NOT_FOUND. Retrying after a 502
re-attempts the provider deletion.
Webhook events. audit.log_recorded (when subscribed). See Webhooks.
Access
full. Admin-only: API keys with write are refused; signed-in users need the owner or admin role.Workspace API key: jl_ followed by 64 lowercase hex characters, created by the workspace owner in the
dashboard (Settings → API Keys) and sent as Authorization: Bearer jl_.... The plaintext is shown once,
at creation; Jelliu stores only a SHA-256 hash. A workspace can hold up to 25 active keys.
Operations restricted to admins or owners reject keys without the full scope with 403, and say so in
their description. No key, whatever its scope, can mint or revoke API keys or rotate a webhook secret —
that requires a signed-in owner session. A revoked key stops authenticating within about 10 seconds.
See Authentication.