Skip to main content
GET
Get Ticket

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.
  • Your own ticket: You must be the ticket’s requester. Not available for system-created tickets or tickets restricted to their team. Returns the requester view: priority, labels, category, escalation and SLA fields are omitted, and related tickets are limited to those you can open.

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

id
string
required

Response

200 - application/json

Success

data
data · object