---
title: "Exit in-flight users from a Sequence"
method: POST
path: "/api/journeys/exit"
tags: ["Journeys"]
---

# Exit in-flight users from a Sequence

`POST /api/journeys/exit`

## Request

- Base URL: `https://go.urbanairship.com`
- URL: `https://go.urbanairship.com/api/journeys/exit`
- Auth: OAuth 2
  - Client credentials
  - Token URL: `http://oauth2.{domain}.com/token` scopes: `jny`
- TypeScript: <https://skmtc.dev/airship/apis/airship-api/docs/api/journeys/exit/post.ts> (a function with typed inputs; its response is checked against the schema)

Exits in-flight users from a [Sequence](/guides/messaging/messages/sequences/about/) identified by `triggering_id`.  Specify an `entrance_id` to exit only users from that specific entrance, or omit it to exit users that entered without an `entrance_id`.  This is a potentially long-running, asynchronous operation.

## Request body

- object
  - `entrance_id` string: Identifies a specific entrance for exit. If provided, only users that entered with this `entrance_id` are exited. If omitted, only users that entered without an `entrance_id` are exited.
  - `triggering_id` union, required
    - string: Identifier of a Sequence's configured [API Entrance trigger](/guides/messaging/messages/sequences/triggers/#api-entrance).
    - TriggeringId[]

## Response `200`

Returned if the exit request has successfully been sent.  This does not indicate that an existing Sequence successfully received the request.

- OkResponseObject: Returned with 2xx Responses. At a minimum, successful calls return `true` for the `ok` key. If your call includes a verbose response (as with `GET` requests, etc.), the `ok` key will appear in the top-most object, outside the verbose response.
  - `ok` boolean, required: Success.
  - `operation_id` string, uuid: A unique string identifying the operations that modify resources. Use the operation ID to locate and track grouped operations (i.e., a batch push operation may generate multiple `push_id` strings, but a single `operation_id`) or operations that change an existing resource.

## Other responses

- `400`: There was a parsing or validation error in the request. Bad Request errors typically include `path` and `location` in the response to help you find the cause of the error.
- `401`: Authentication information (the app key and secret or bearer token) was either incorrect or missing.
- `403`: Authentication was correct, but the user does not have permission to access the requested API, e.g., if the feature in question is not included in your pricing plan.
- `429`: Too many requests hit the API too quickly. For example, if we are not ready to create a channel for this payload; e.g., it is rate limited. You should wait before retrying the channel creation.

## Changes

- **2026-06-24** `38241778b0c1`: 1 info
  - endpoint added
  - …this revision’s changelog is incomplete

[Operation history](https://skmtc.dev/airship/apis/airship-api/changes/api/journeys/exit/post.md)

---

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