Add a journey node
Inserts one node into an existing journey, immediately after parent_id. The insert uses
the same splice as the journey editor. type is one of email, sms, push, delay,
branch, random_split, filter, or exit. index selects a branch arm (0 or 1)
and is rejected on a linear parent. The journey keeps its single enter node. Returns the
journey in the same shape as GET /journeys/{id}.
Authorizations
Accepts either a raw API key or Bearer <key>.
Headers
Optional dated API revision for the request. Must use YYYY-MM-DD format.
^\d{4}-\d{2}-\d{2}$"2026-03-01"
Path Parameters
Journey ID.
Body
Response
Node added. Returns the updated journey.
A journey with its full graph — its trigger, nodes and edges. Messaging nodes expose message and content metadata but not content bodies or audience details.
Journey name.
Optional journey description. May be null.
Journey lifecycle status.
draft, active, paused, archived, cancelled The event that enters people into the journey. null when none is set.

