Resume a journey enrollment from a node
Advance one contact’s journey enrollment from a named node. The JSON body carries contact_id, recipient_address, next_node_id, and a stringified journey_definition (validated at the boundary before execution; optional enrollment_id improves terminal-state detection). Called by the scheduling infrastructure when a wait node’s timer fires; a non-2xx response signals the scheduler to back off and retry rather than clear the resume state. Operator callers may also use it to un-stick a contact manually.
Authorizations
Dashboard JWT token from Clerk
Headers
Stripe-style idempotency token. Pass a stable, client-generated value (1-255 chars) to dedupe retries on transient timeouts. The same key+credential+path replays the original response for 24h on 2xx (5min on 4xx, 30s on 5xx). Returns 409 if a concurrent request with the same key is already in flight; replayed responses include the Idempotency-Replay: true response header.
1 - 255Sandbox opt-in for Clerk-session-authenticated requests. Set to true to route the call through the test-mode pipeline: no real provider delivery, no credits deducted, response meta.test_mode: true. Ignored for live API keys (dv_live_sk_*) — server-to-server clients must use a test-prefixed key (dv_test_sk_*) to exercise sandbox. Test-prefixed keys unconditionally enable sandbox regardless of this header.
true, false Path Parameters
Response
Successful response.