Introduction to the Channel Manager API

The Channel Manager API lets external sales channels — third‑party booking platforms, online travel agents, resellers — submit orders for tickets that are issued by the Channel Manager. The API is intentionally compact: partners send a full order in a single call, and the Channel Manager handles item resolution, ticket issuance, and wallet creation. Each issued wallet ships back with a manifestUrl that renders the wallet shell; delivering the wallet to the customer (by email, by the partner’s own app, or any other channel) remains the partner’s responsibility.

Orders: a single resource

Channel manager orders are the only resource exposed by this API. Each order is owned by a partner (identified by partnerId) and is keyed end‑to‑end by the partner’s own sellToOrderReference. The combination must be unique per partner; duplicate submissions are rejected.

An order carries one or more items, each pointing at a Business Central item number. The Channel Manager classifies the item at issuance time:

  • a package item (configured with an Item Add‑On) expands into multiple component admissions, optionally with a per‑component wallet.componentSchedule that fixes each component to its own visit date and time;
  • an individual ticket issues one wallet per unit of quantity;
  • a group ticket issues exactly one wallet for the line, with the line’s quantity interpreted as the group size.

Lifecycle

Ticket issuance runs synchronously inside createOrder and replaceOrder, so the response carries the order’s final state directly — no polling required. Most orders land in Issued (when paymentReference is supplied) or Draft (when it is not, in which case the partner calls confirmOrder to release the order). Replacement and cancellation are restricted by status — see Orders for the full transition matrix.

What the API does not do

  • The Channel Manager API does not browse the catalog, look up capacity, or quote prices. Items must already exist in Business Central and partners are expected to know which item number to sell. For catalog and capacity queries, use the Ticketing API.
  • The API does not perform admission validation. Once tickets are issued, the standard Tickets and Speedgate endpoints take over.