---
title: "Update Journey Application"
method: PUT
path: "/journeys/{journey_token}/applications/{journey_application_token}"
tags: ["Journeys"]
---

# Update Journey Application

`PUT /journeys/{journey_token}/applications/{journey_application_token}`

This endpoint has 3 different use cases:

  * Send the additional or updated data required to advance the application.
    * Only available if one or more entity applications have the statuses `pending_documents`, `pending_step_up`, or `data_request`.
  * Send new, additional entities to be processed.
    * Only available if the parameter `do_await_additional_entities` was set to `true` in the POST request to create the journey application.
  * Inform the system that the user has finished sending all additional entities by passing the parameter `has_finished_sending_additional_entities` with value `true`.
    * Only available if the parameter `do_await_additional_entities` was set to `true` in the POST request to create the journey application.

Any of the headers used with the original application (ex: `alloy-sandbox`) will also be used here.

## Parameters

- `#/paths/~1journeys~1%7Bjourney_token%7D~1applications/parameters/1` — unresolved $ref

## Request body

- Schema — unresolved $ref

## Other responses

- `200` — unresolved $ref
- `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)