curl --request POST \
  --url https://api.getvero.com/api/v2/journeys \
  --header 'Authorization: <api-key>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "name": "Welcome series",
  "trigger": {
    "type": "event",
    "event_name": "signed_up"
  }
}
'

{
  "id": 42,
  "name": "Welcome series",
  "description": null,
  "status": "draft",
  "trigger": {
    "type": "event",
    "event_name": "signed_up"
  },
  "nodes": [
    {
      "id": 1,
      "temporary_id": "start",
      "type": "enter"
    },
    {
      "id": 2,
      "temporary_id": "wait",
      "type": "delay",
      "delay": {
        "delivery_option": 1,
        "duration": 1,
        "duration_unit": "days",
        "delay_property": null,
        "property_type": null,
        "preferred_delivery_time": null
      }
    },
    {
      "id": 3,
      "temporary_id": "welcome",
      "type": "email",
      "title": "Welcome email",
      "message": {
        "id": 100,
        "from": null,
        "reply_to": null,
        "contents": [
          {
            "id": 200,
            "locale": null,
            "is_default": true,
            "subject": null,
            "preheader_text": null
          }
        ]
      }
    },
    {
      "id": 4,
      "temporary_id": "done",
      "type": "exit"
    }
  ],
  "edges": [
    {
      "from": 1,
      "to": 2
    },
    {
      "from": 2,
      "to": 3
    },
    {
      "from": 3,
      "to": 4
    }
  ],
  "created_at": "2026-03-01T10:00:00Z",
  "updated_at": "2026-03-01T10:00:00Z"
}

{
  "errors": [
    {
      "message": "<string>"
    }
  ]
}

Journeys

Create a journey

Creates a draft journey with a name, an event trigger and, optionally, a full graph of nodes and edges. Omit both nodes and edges to start from a graph of one enter node connected to one exit node. When submitting nodes, each node carries a temporary_id that edges refer to. The response returns each temporary_id beside the node’s new id. Use the id when using the node deletion endpoint. Messaging nodes (email, sms or push) need a provider for that channel in your project. Once created you can add content to a message node using the “Journey Message Contents” endpoints. Nothing is created if the request is rejected. Returns the journey in the same shape as GET /journeys/{id}.

POST

journeys

curl --request POST \
  --url https://api.getvero.com/api/v2/journeys \
  --header 'Authorization: <api-key>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "name": "Welcome series",
  "trigger": {
    "type": "event",
    "event_name": "signed_up"
  }
}
'

{
  "id": 42,
  "name": "Welcome series",
  "description": null,
  "status": "draft",
  "trigger": {
    "type": "event",
    "event_name": "signed_up"
  },
  "nodes": [
    {
      "id": 1,
      "temporary_id": "start",
      "type": "enter"
    },
    {
      "id": 2,
      "temporary_id": "wait",
      "type": "delay",
      "delay": {
        "delivery_option": 1,
        "duration": 1,
        "duration_unit": "days",
        "delay_property": null,
        "property_type": null,
        "preferred_delivery_time": null
      }
    },
    {
      "id": 3,
      "temporary_id": "welcome",
      "type": "email",
      "title": "Welcome email",
      "message": {
        "id": 100,
        "from": null,
        "reply_to": null,
        "contents": [
          {
            "id": 200,
            "locale": null,
            "is_default": true,
            "subject": null,
            "preheader_text": null
          }
        ]
      }
    },
    {
      "id": 4,
      "temporary_id": "done",
      "type": "exit"
    }
  ],
  "edges": [
    {
      "from": 1,
      "to": 2
    },
    {
      "from": 2,
      "to": 3
    },
    {
      "from": 3,
      "to": 4
    }
  ],
  "created_at": "2026-03-01T10:00:00Z",
  "updated_at": "2026-03-01T10:00:00Z"
}

{
  "errors": [
    {
      "message": "<string>"
    }
  ]
}

This endpoint is in alpha and is subject to change at any time. Email support for access.

Authorizations

Authorization

string

header

required

Accepts either a raw API key or Bearer <key>.

Headers

revision

string

Optional dated API revision for the request. Must use YYYY-MM-DD format.

Pattern: ^\d{4}-\d{2}-\d{2}$

Example:

"2026-03-01"

Body

application/json

Create a draft journey. Send nodes and edges together to build the graph, or omit both to start from a graph of one enter node connected to one exit node.

name

string

required

Journey name. Trimmed before validation; must be non-blank.

Required string length: 1 - 255

trigger

object

required

The event that enters people into the journey.

Show child attributes

nodes

object[]

The journey's nodes. A graph needs exactly one enter node, which has no incoming edges, and at least one exit node. Every node must be reachable from the enter node, and the graph must not contain cycles. Each branch and random_split arm must end in an exit or rejoin the other arm at the first node both arms reach. A random_split arm cannot contain a branch, an exit, or another random_split.

Maximum array length: 1000

Show child attributes

edges

object[]

The journey's edges. A branch or random_split node has exactly two outgoing edges, with branch_index 0 and 1. An exit node has none, and every other node has exactly one.

Maximum array length: 2000

Show child attributes

Response

Journey created.

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.

integer

required

name

string

required

Journey name.

description

string | null

required

Optional journey description. May be null.

status

enum<string>

required

Journey lifecycle status.

Available options:

draft,

active,

paused,

archived,

cancelled

trigger

object | null

required

The event that enters people into the journey. null when none is set.

Show child attributes

nodes

object[]

required

Show child attributes

edges

object[]

required

Show child attributes

created_at

string<date-time>

required

updated_at

string<date-time>

required

Track API

Campaigns API

Create a journey

Authorizations

Headers

Body

Response