Publish a journey
Publishes a journey’s current draft as a new version, making it live for new runs. Pass a version instead to roll back to an earlier one.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Headers
A unique key that makes this request idempotent. If Courier receives another request with the same Idempotency-Key, it returns the stored response from the first request without performing the operation again (including the original status code and any error). Use it to safely retry POST requests after network failures without risking duplicate sends. The key is scoped to this endpoint.
How long the idempotency key remains valid, as a Unix epoch timestamp in seconds or an ISO 8601 date string. Only applies when Idempotency-Key is provided. If omitted, the key is retained for 25 hours; the maximum is 1 year.
Path Parameters
Journey id
1Body
Request body for publishing a journey. Pass version to roll back to a prior version; omit to publish the current draft.
^v\d+$Response
Published journey
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
- Add to Digest
- Exit
- JourneyBranchNode