Skip to main content

Add Ticket Link

POST 

/api/support/agent/tickets/:ticket/links

Links the ticket to an external reference — a Dev HQ issue, an error tracker event, another ticket, an internal record, or an arbitrary URL (a PR or deploy is url). Linking the same (kind, ref) pair again is a no-op update rather than a duplicate. Only record links are shown to the customer; the rest (devhq, sentry, ticket, url) are agent-only.

Required scope: support:write

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

A devhq link puts the ticket's resolution clock on the engineering hold (once the ticket has had its first response) until the link is removed or the ticket is resolved, counts the ticket as a confirmed defect, and feeds List Issue Requesters.

Request body:

  • kind (required, string) — one of: devhq, sentry, record, ticket, url. jira is still accepted as a legacy alias and is stored as devhq (Jira was replaced by SKU Dev HQ on 2026-10-27; keys are unchanged).
  • ref (required, string, max 255) — an issue key (ENG-1234), event id, or record id
  • url (optional, string, valid absolute URL, max 2048) — for a devhq link, omit it to get https://devhq.sku.io/issues/<ref>; a Jira browse URL is rewritten to the Dev HQ issue with the same key
  • label (optional, string, max 255) — defaults to ref when omitted

Response (data): id, kind, kind_label (e.g. "Dev HQ issue"), ref, url, label, created_at.

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

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​

Created

Response Headers
    Content-Type