Ticket API
Link Tickets
Link two tickets together with a linked relationship. Both tickets must be in the same team. The relationship is symmetric: each ticket shows the other as a related ticket.
POST
Link Tickets
Authentication and permissions
Token requirements: User-based token (OAuth) or Organization-scoped API key or Team-scoped API key. Send a bearer access token for one of these identities. The permissions and resource restrictions below also apply.
Permissions joined by + are all required; or separates alternatives. Full-access keys still cannot call endpoints marked unsupported. Team keys must allow every team checked by the request. OAuth access depends on the user’s roles and resource access.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
The ID of the ticket to link from
Body
application/json
The ID of the ticket to link to. Must be in the same team as ticket_id.
Response
200 - application/json
Success
The response is of type LinkTicketsResponse · object.

