Export Journey List

The Journey List API enables you to export detailed information for all journeys created in Architect. This endpoint provides metadata such as journey name, status, creation and execution dates, tags, conversion goals, and exit criteria — allowing you to easily audit, analyze, or back up journey configurations externally.

It’s particularly useful for teams that want to integrate Architect data with external analytics platforms or maintain synchronized journey catalogs.

Endpoint and Headers

GET https://architect-analytics.api.useinsider.com/v1/journeys/export

Visit our Postman collection to test this request.

Headers

Header	Sample Value	Description
Authorization	Bearer 1a2b3c4d5e6f	This key is required to authorize your request. Refer to API Authentication Tokens to generate your token. You should enter the word Bearer followed by the API key you generated.
Accept	application/json	You should enter it as application/json at all times.

Query Parameters

Parameter	Description	Sample Value	Required
statuses	Filters journeys by status. Allowed values are active, test, passive, sunset.	?statuses[]=active&statuses[]=test	No
ids	Filters by specific journey IDs	?ids[]=1&ids[]=2&ids[]=3	No
search	Returns journeys whose names partially match the provided text.	?search=welcome	No
tags	Filters journeys by their assigned tags. Each tag must exist in the tags table.	?tags[]=cart%20abandonment&tags[]=retention	No
limit, page	Pagination for the export. You can determine which page and for what limit you want to get an export for. You can get at most 300 journeys per export.	?limit=100&page=1 → Brings the 100 journeys of the first page. If you have 900 journeys, and you want to get an export for all of them, you need 3 API calls: ?limit=300&page=1 ?limit=300&page=2 ?limit=300&page=3	No

Sample Example

Sample Query

Before sending the request, make sure:

To replace the authorization value with your own API key.
To replace the sample values in parameters with your own values in the required data type.

curl -X GET "https://architect-analytics.api.useinsider.com/v1/journeys/export?status[]=active&tags[]=welcome" \
-H "Authorization: Bearer INS.1a2b3c4d \
-H "Accept: application/json"

Sample Responses

200 OK

{
  "journeys": [
    {
      "journeyId": 5756,
      "journeyName": "Demo Journey",
      "status": "active",
      "createdAt": "2025-10-14T11:42:29.000000Z",
      "startDate": "2025-10-14T11:44:53.000000Z",
      "endDate": "2025-11-13T11:42:45.000000Z",
      "tags": ["Demo"],
      "description": null,
      "starterType": "on-event",
      "languages": ["ar_AE", "ja_JP", "ka_GA"],
      "reEligibility": {
        "rule": "Users re-enter after 3 day",
        "value": 3
      },
      "conversionGoals": [
        {
          "id": 216,
          "event": "confirmation_page_view",
          "eventParameters": [
            {
              "display_name": "Event Source",
              "key": "source",
              "operator": "eq",
              "type": "string",
              "values": ["crm", "mobile"]
            }
          ]
        }
      ],
      "exitCriteria": [
        {
          "event": "item_added_to_cart",
          "parameters": {
            "name": "item_added_to_cart",
            "type": "event",
            "params": [],
            "identifierParameter": "",
            "hash": "item_added_to_cartnacntstring3/4 Sleeve Kimono DressProduct Name",
            "consistencyStatus": false,
            "groupPartners": [],
            "value": "item_added_to_cart"
          }
        },
        {
          "event": "login",
          "parameters": {
            "name": "login",
            "type": "event",
            "params": [],
            "identifierParameter": "",
            "hash": "login",
            "consistencyStatus": false,
            "groupPartners": [],
            "value": "login"
          }
        }
      ],
      "campaigns": [
                {
                    "id": 64592,
                    "name": "Demo Journey Web Push 1",
                    "channel": "Web Push"
                },
                {
                    "id": 64596,
                    "name": "Demo Journey Web Push 2",
                    "channel": "Web Push"
                },
                {
                    "id": 64595,
                    "name": "Demo Journey SMS 2",
                    "channel": "SMS"
                },
                {
                    "id": 64599,
                    "name": "Demo Journey SMS 1",
                    "channel": "SMS"
                },
                {
                    "id": 64591,
                    "name": "Demo Journey On-Site 1",
                    "channel": "On-Site"
                }
            ]
    }
  ]
}

401 Unauthorized

{
    "error": "Invalid API key"
}

Limitations

The request must be executed with an HTTPS GET request.
The API Key should be provided as the authorization key on the request header. If the key is incorrect, the operation will not be executed and an authorization error will return in the response.
You can send 100 requests per minute with the same API Key. If you exceed the rate limit, you will receive a 429 error.

The default limit shown here is a standard baseline. If your use case requires higher capacity, feel free to reach out to the Insider One team — we can adjust it to fit your needs.