> This page is for API Reference.

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.navipartner.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.navipartner.com/_mcp/server.

# Introduction to the OTA Channel Manager API

The OTA Channel Manager API lets external sales channels — online travel agents, third-party
booking platforms, resellers — create orders for tickets and packages. A single call submits a full
order; the OTA Channel Manager handles item resolution, ticket and coupon issuance, and wallet
creation. Delivering each issued wallet to the customer (by email, by your own app, or any other
channel) is the partner's responsibility.

## The status lifecycle

`createOrder` and `replaceOrder` are asynchronous. The endpoint accepts the order,
persists it with `status = Submitted`, and returns immediately. The order is then processed in the
background, transitioning through `Scheduled → Processing` to a terminal state — `Issued`, `Draft`,
or `Error`.

To consume the result, partners can:

* **subscribe to the `ota_cm_order_processed` webhook** — fired once when the order settles to a
  terminal state, carrying `orderId`, `buyFromOrderReference`, and the final `status`; or
* **poll `getOrder`** until `status` is one of `Issued`, `Draft`, or `Error`.