Turn AI Agent Back On for Ticket

POST 
/api/support/agent/tickets/:ticket/ai/enable

Make the ticket eligible for the AI agent again. It does not reassign the ticket — the agent claims it on its own if it is still unowned, or hand it back explicitly. Records an internal ai_enabled event; turning it on when it is already on changes nothing.

Required scope: support:write

Grant this scope to your token under Settings → Developer → Personal Access Tokens.

Path parameters

• ticket (integer) — the ticket id.

No request body. The response is the updated ticket in the agent shape (see Get Agent Ticket for every field, including the work control fields ai_paused, ai_paused_by, ai_paused_at, ai_disabled, stop_requested_at, stop_requested_by and pending_instructions).

Authentication: Bearer token with the support:write scope, or an authenticated session, from a caller with an active support role that can work tickets (the viewer role is read-only). No tenant context — this endpoint is central.

Request

Responses

200

OK

Response Headers

Content-Type

401

Unauthorized

Response Headers

Content-Type

403

Forbidden

Response Headers

Content-Type

404

Not Found

Response Headers

Content-Type

422

Validation failed — the body is a field → messages map (Laravel shape) or the platform envelope with a stable machine-readable code. Fix the payload and resubmit.

429

Rate limited — platform limit is 1,000 requests/min; individual tokens may carry lower limits. Honor the Retry-After header before retrying. See the Rate Limits guide.