Skip to main content
GET
Get a journey

Authorizations

Authorization
string
header
required

Personal Access Token or OAuth 2.1 access token, sent as a bearer credential (Authorization: Bearer inf_pat_...). Read operations require a token with the READ scope; write operations (POST/PATCH/DELETE) require WRITE.

Path Parameters

id
string
required

Journey (campaign) id.

Response

The journey.

data
object

As Journey, but the single-journey read keeps schedule and always omits dynamicList. That field carries the list's compiled SQL, which is not part of the public contract.

meta
object

Envelope metadata present on every response.