Skip to main content

Assign Ticket to Me

POST 
/api/support/agent/tickets/:ticket/assign-to-me

Assigns the ticket to the calling agent. A no-op (still 200) if the ticket is already assigned to them. The response is the updated ticket. 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, and ai — the latest completed triage and draft runs that are not withheld. 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.

Required scope: support:write

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

Authentication: Bearer token with the support:write scope, or an authenticated session, from a caller with an active support role that can work tickets.

Request​

Responses​

OK

Response Headers
    Content-Type