Acknowledge AI Agent Stop

POST 
/api/support/agent/tickets/:ticket/ai/stop/ack

The AI agent confirms that the session a human stopped is gone: clears work.stop_requested_at and work.stop_requested_by and records an internal ai_stopped event. Does not require the AI agent to still own the ticket (it may have been released since the stop was requested). Acknowledging when no stop is pending 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 belonging to the AI agent's own account — any other caller, including support admins, gets a 403. 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.