Create a journey
Create a journey. Defaults to DRAFT state; pass state: "PUBLISHED" to publish on create. Send nodes are not allowed on POST. The standard flow is: create the journey shell here, add notification templates with POST /journeys/{templateId}/templates, then wire them into the journey with PUT /journeys/{templateId}. Call POST /journeys/{templateId}/publish to publish a draft after the fact.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Body
Request body for creating a journey.
11A single node in a journey DAG. Discriminated by type, with a secondary discriminator on some variants (trigger_type for trigger, mode for delay, method for fetch, scope for throttle).
- API Invoke Trigger
- Segment Trigger
- Send
- Delay for Duration
- Delay Until
- Fetch (GET/DELETE)
- Fetch (POST/PUT)
- AI
- Throttle (Static)
- Throttle (Dynamic)
- Batch
- Exit
- JourneyBranchNode
Lifecycle state of a journey.
DRAFT, PUBLISHED Response
Journey created
A journey, with its current draft or published nodes and metadata.
Lifecycle state of a journey.
DRAFT, PUBLISHED A single node in a journey DAG. Discriminated by type, with a secondary discriminator on some variants (trigger_type for trigger, mode for delay, method for fetch, scope for throttle).
- API Invoke Trigger
- Segment Trigger
- Send
- Delay for Duration
- Delay Until
- Fetch (GET/DELETE)
- Fetch (POST/PUT)
- AI
- Throttle (Static)
- Throttle (Dynamic)
- Batch
- Exit
- JourneyBranchNode