Skip to main content
GET
Get Journey

Authentication and permissions

Token requirements: User-based token (OAuth) or Organization-scoped API key or Workspace-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. Workspace keys must allow every workspace checked by the request. OAuth access depends on the user’s roles and resource access. For delegated user tokens, ticket fields are limited to the fields the user can read. Journey aggregates are omitted when they depend on hidden ticket fields. Journey filters and sorting require access to the referenced fields.

Authorizations

Authorization
string
header
required

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

Path Parameters

id
string
required

Journey root ticket UUID.

Response

200 - application/json

Success

data
data · object

A full journey snapshot returned by GetJourney.