For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
    • Introduction
    • URL Structure
    • API Key
    • Errors
    • Versioning
    • Pagination
    • Replication
    • Rate Limits
    • Webhooks
  • System Services
    • Companies
    • Hello World
  • Accounts
  • Ticketing
    • Getting started
    • Catalog
    • Capacity
    • Tickets
    • Reservations
    • Schedule
  • Memberships
    • Catalog
    • Membership
    • Member
    • Card
    • Payment Method
    • Lifecycle
    • Miscellaneous
    • Points
  • Speedgate
  • Attraction Wallet
  • OTA Channel Manager
    • Getting started
    • Orders
  • POS
    • POS Sale
    • POS Entry
    • POS Unit
    • POS Store
    • Salesperson
    • External POS Sale
    • Global POS Entry
  • Restaurant
  • Inventory
    • Barcodes
    • Items
    • Item Ledger Entries
    • Item Categories
    • Item Variants
    • Item Translations
  • Coupon
  • Vouchers
    • Vouchers
  • Sales Documents
    • Ecommerce
  • Finance
    • General Ledger Account
    • General Ledger Entries
    • General Ledger Journal
  • Customers
    • Customers
    • GDPR
  • Retail Print
    • Print Price Labels
  • PDF Designer
LogoLogo
On this page
  • The status lifecycle

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.
Was this page helpful?
Previous

Getting Started

Next
Built with