Add Ticket Link
POST/api/support/agent/tickets/:ticket/links
Links the ticket to an external reference — an issue tracker item, an error tracker event, a deploy, another ticket, an internal record, or an arbitrary URL. Linking the same (kind, ref) pair again is a no-op update rather than a duplicate. Only deploy and record kinds are shown to the customer; the rest (jira, sentry, ticket, url) are agent-only.
support:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Request body:
kind(required, string) — one of: jira, sentry, deploy, record, ticket, urlref(required, string, max 255) — an issue key, event id, build, or record idurl(optional, string, valid absolute URL, max 2048)label(optional, string, max 255) — defaults torefwhen omitted
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
- 201
- 401
- 403
- 404
- 422
- 429
Created
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.