---
title: "Create Journey Application"
method: POST
path: "/journeys/{journey_token}/applications"
tags: ["Journeys"]
---

# Create Journey Application

`POST /journeys/{journey_token}/applications`

Create a journey application for one or more entities.

## Request body

- object
  - `entities` union[], required — List of entities to be processed in this Application.
    - union
      - Items — unresolved $ref
      - object
        - `external_entity_id` string — The value used on client's own system to identify the entity. If an entity associated with the value passed in already exists, then the entity application processes for that entity. Otherwise, a new entity is created and associated with the value passed in. This parameter is optional, but strongly encouraged.
        - `data` object, required — Contains the fields for each input attribute of each workflow in the journey that is expected to be processed for the entity.
          - `business_name` string
          - `business_federal_ein` string — Business federal employer ID number for US business entities.
          - `business_registry_id` string — Business registry ID number for non-US business entities.
          - `business_phone_number` string — Business phone number.
          - `business_url` string — Business website.
          - `addresses` object[] — List of addresses for the given entity.
            - `type` string — Allowed values are `"business_primary"`, `"business_secondary"`, `"business_previous"`
            - `line_1` string
            - `line_2` string
            - `city` string
            - `state` string
            - `postal_code` string
            - `country_code` string
          - `representatives` object[] — List of ultimate beneficial owners associated to the business.
            - `name_first` string
            - `name_middle` string
            - `name_last` string
            - `type` string — Allowed values are `"principal_owner"`, `"authorized_signer"`, `"coborrower"`, `"joint"`, `"guarantor"`, or `"director"`.
            - `birth_date` string
            - `document_ssn` string — Social Security number
            - `email_address` string
            - `phone_number` string
            - `ownership_percentage` string
            - `addresses` Items[] — List of addresses for the given entity. — unresolved $ref
          - `meta` object — Any additional metadata to be accessed for decisioning or review purposes that are not sent to a data service can be referenced here.
        - `entity_type` string — If left blank, defaults to `"business"`.
        - `branch_name` string — This value is required for journeys with multiple branches. It must match a journey branch configured from the start node. It is used to determine which steps the entity will be required to complete.
        - `entity_token` string — The token associated with an existing entity. By passing a value for this field, the entity application processes for the existing entity associated with the token.
  - `external_group_id` string — Optional, but if you have an identifier in your system that is unique and that you would like to tie to an Application in a 1:1 relationship, you can include it here. This field will not update the Entity Group object.
  - `external_application_id` string — Optional, but if you have an identifier in your system that refers to an application or an entire account, and you would like to associate it with one or more Journey Applications, you can include it here. We also have a number of endpoints that allow you to reference a Journey Application by external application id instead of by Journey Application token when retrieving, rerunning or updating the Application. Supported characters are: `a-zA-Z0-9_-`
  - `do_await_additional_entities` boolean — If this value is true, additional entities can be sent by using the PUT endpoint that updates a Journey Application. The Journey Application will not complete until the parameter `has_finished_sending_additional_entities` is sent with the value `true` to the PUT endpoint.
  - `application_meta` object — Optional, allows to provide additional metadata applied to all entities in the Application.
  - `external_entity_group_id` string — Optional, but if you wish to associate the entities within this application with an existing entity group or create a new entity group with this identifier, you can include it here. For more information on entity groups, visit our guide: https://developer.alloy.com/public/docs/onboarding-with-entity-groups
  - `entity_group_token` string — Optional, but if you wish to associate the entities within this application with an existing entity group, you can include it here.
  - `entity_group_name` string — Optional, but if you wish to create a new entity group with this name, you can include it here.
  - `entity_group_type` 'business' | 'joint_account' | 'membership' | 'merchant' — Optional, but if you wish to create a new entity group with this type, you can include it here.

## Other responses

- `400` — unresolved $ref
- `401` — unresolved $ref
- `404` — unresolved $ref
- `409` — unresolved $ref
- `429` — unresolved $ref
- `500` — unresolved $ref
- `503` — unresolved $ref

---

[API](https://skmtc.net/alloy/apis/alloy-api.md) · [All operations](https://skmtc.net/alloy/apis/alloy-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/alloy/alloy-api/revisions/405799de4d2a/schema)