Skip to main content

Link Ticket Requester to User

POST 
/api/support/agent/tickets/:ticket/link-requester

Links the ticket's requester — typically someone who wrote in from another environment (beta, demo, dev) and was matched only by email — to a SKU.io user. This only sets who the requester is on this ticket; it never merges or changes user accounts. An internal requester_linked event is recorded.

Required scope: support:write

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

Linking to the user the ticket is already linked to is a no-op (still 200). A ticket already linked to a different user is refused with a 422 — it is never re-pointed.

Path parameters

  • ticket (integer) — the ticket id.

Request body

  • user_id (integer, required, min 1) — the SKU.io user to link (see Search Users).

The response is the refreshed customer context for the ticket, exactly as Get Ticket Customer Context returns it.

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​

OK

Response Headers
    Content-Type