Assign Ticket to Me
POST/api/support/agent/tickets/:ticket/assign-to-me
Claims the ticket for the calling agent and takes it over from whoever held it — including the AI agent. This is Claim Agent Ticket with force always on: the caller becomes the owner (assignee and work.owner), the first claim ever stamps work.picked_up_at / work.picked_up_by_user_id and records a customer-visible picked_up event, a ticket still at the received stage moves to picked_up, an open ticket moves to in_progress, and the ticket leaves the triage queue. Taking a ticket over from the AI agent also records a released event (reason take_over). A no-op (still 200) if the ticket is already assigned to the caller. The response is the updated ticket.
support:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
The agent view adds group_key, external_ref, note_count, merged_into_ticket_id, sla_policy_id, created_by_user_id, sla_paused_at, snoozed_until (with is_snoozed, true while that moment is still in the future), follow_up_at (the agent's own reminder, or null), the agent-facing status_label, the assignee's email, ai — the latest completed AI runs — and work (see Get Agent Ticket). first_response_sla_status and resolution_sla_status report the ticket's two SLA clocks: one of on_track, breaching_soon (past the policy's warning point, by default 75% of the way from creation to the due date), breached, paused (the ticket is waiting on the customer, so neither clock warns), met (responded / resolved before the due date). merged_into is {id, number} once the ticket has been merged into another, otherwise null.
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.
If this ticket was merged into another ticket, the request is refused with a 422 whose merged_into (id, number) names the live ticket — send the action there instead.
Request
Responses
- 200
- 401
- 403
- 404
- 422
- 429
OK
Response Headers
Unauthorized
Response Headers
Forbidden
Response Headers
Not Found
Response Headers
Unprocessable Content
Response Headers
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.