---
title: "Rerun latest Journey Application by External Application ID"
method: POST
path: "/journeys/applications/ext/{external_application_id}/latest/rerun"
tags: ["Journeys"]
---

# Rerun latest Journey Application by External Application ID

`POST /journeys/applications/ext/{external_application_id}/latest/rerun`

This endpoint reruns the latest (i.e. most recently created) Application associated with the supplied External Application ID.
If the `journeyToken` query parameter is provided, the retrieved Application will be the latest Application associated with that particular Journey and the External Application ID.
Just as with our other rerun endpoint, this will create a new Journey Application.

## Request body

- object
  - `external_application_id` string — Optional, allows to set a different external identifier for the new Application. If not supplied, the value will be copied from the original Application (null if none had originally been provided). Supported characters are: `a-zA-Z0-9_-`
  - `exclude_entity_tokens` string[] — List of entity tokens to be deleted
  - `entities` object[] — List of entities to be processed in this Application.
    - `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.
      - `name_first` string
      - `name_middle` string
      - `name_last` string
      - `birth_date` string
      - `document_ssn` string — Social Security number.
      - `document_national_id` string — National ID number for a non-US person entity.
      - `document_id_card` string — ID card number
      - `document_license` string — U.S. issued driver's license number
      - `document_passport` string — Passport number
      - `email_address` string
      - `gender` string
      - `phone_number` string
      - `ip_address_v4` string
      - `addresses` object[] — List of addresses for the given entity.
        - `type` string — Allowed values are `"primary"`, `"secondary"`, `"previous"`, `"mailing"`, `"shipping"`, `"service"`, `"other"`
        - `line_1` string
        - `line_2` string
        - `city` string
        - `state` string
        - `postal_code` string
        - `country_code` string
      - `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` 'person' | 'business' — If left blank, defaults to `"person"`.
    - `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.
  - `application_meta` object — Optional, allows to provide additional metadata applied to all entities in the Application. If not supplied, the value will be copied from the original Application (null if none had originally been provided).

## Other responses

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

---

[API](https://skmtc.dev/alloy/apis/alloy-api.md) · [All operations](https://skmtc.dev/alloy/apis/alloy-api/llms.txt) · [OpenAPI document](https://skmtc.dev/alloy/apis/alloy-api/revisions/405799de4d2a?raw)