NDC API

Airline NDC fares, from inside your own system

The same content and servicing the NDC Deals portal gives an agent, over an API your booking engine, ERP or app can call. One sign-in, two headers, seven routes. Search, price, book or hold, pay and retrieve real offers from the airlines live on NDC Deals. Build on the sandbox first, then pay to go live.

Register for API access Read the guide

Small surface, whole booking flow

The API is deliberately narrow. Everything that makes NDC hard to integrate directly with an airline, from office ids to payment methods to which service a message goes to, is handled on our side.

One sign-in
A JSON call with your account id and secret returns a bearer token that lasts a day. Cache it, refresh it before it expires.
Two headers
The token and the content type. Which office, service and resource a message goes to is our job, not yours.
Seven routes
Each NDC message is a POST to its own route. The body is the message, the answer is the airline's, as it returns it.
Agency Credit
You send the amount. We attach the payment and draw it from your agency's wallet. No card gateway to integrate.
The booking flow

Seven routes, two ways through

Book and pay in one call, or hold the order under the airline's time limit and pay it later. Retrieve reads either kind back at any point.

  1. POST /flights/searchAirShopping. One route, one date, a passenger mix. Every airline's offers in one response.
  2. POST /flights/priceFlightPrice. The exact fare of the offer the traveller picked; the answer is the input to OrderCreate.
  3. POST /orders/bookOrderCreate with payment. Airlines that ticket instantly return the e-ticket numbers here.
  4. POST /orders/holdOrderCreate without payment. The PNR is held until the airline's payment time limit.
  5. POST /orders/repriceOrderReshop. Confirm a held order's price before paying it.
  6. POST /orders/payOrderChange. Pay the held order with Agency Credit; the airline tickets it.
  7. POST /orders/retrieveOrderRetrieve. Status, time limits, passengers, flights, price and ticket numbers.

Offers expire on the airline's clock: minutes to price, minutes to book, days to pay a hold. Every answer carries its own time limits.

Build it with an LLM

A working integration in 7 minutes

The guide is written for a coding assistant as much as for a person. We gave the files to Claude Code and it went from an empty folder to a ticketed sandbox booking in 7 minutes. Codex and Cursor take the same files.

  1. Download two files

    The guide as one Markdown file, generated for your account: your sandbox endpoints, every route, every transcript from a real exchange with the sandbox, and an implementer checklist. Plus the reference script, which has booked and ticketed on the sandbox.

  2. Put your credentials in .env

    Two variables: your account id and the secret an admin reveals on the Account page. The reference and the prompt both read them.

  3. Paste one prompt

    Open the assistant in that folder and paste the prompt from the guide. It reads the guide, ports the reference to your stack, runs it against the sandbox and shows you a ticket.

Register for API access See the prompt
A developer's desk by a window overlooking an airport apron at dusk
Your stack, your language. The reference is Python; the assistant ports it.

From sandbox to live

Nothing is issued by hand at registration. The sandbox is yours as soon as the fee is paid; going live is a second step you take when the integration is ready.

  1. 1

    Register online

    Company details, a WhatsApp OTP, the upfront fee. Your sandbox agency and wallet are created and your admin sets a password.

  2. 2

    Generate credentials

    An admin generates the API user from the Account page and reveals the secret once. Reveal again and it rotates.

  3. 3

    Build and book

    Real airlines answer on the sandbox. Search, price, book, hold and pay against your sandbox wallet until the flow is right.

  4. 4

    Pay and go live

    Pay the go-live fee from the portal. Your live agency is registered and live credentials are issued to your admin; switch endpoints and you are selling.

Two fees, priced for your region

An upfront fee opens the sandbox account. A go-live fee moves you to live. Both are set per region, in your currency, and shown in the registration wizard before you pay. A coupon code, if you have one, comes off at payment.

API access
Paid once at registration. Sandbox agency, wallet, portal login, credentials on demand, the guide and the reference script.
Go live
Paid when your integration is ready. Live agency, live credentials, the airlines on the partner list at the airline's own fares.

Common questions

The technical detail is in the guide, which opens once you are registered and signed in.

Open the guide
Agencies and travel technology companies that run their own booking engine, back office or app and want NDC content and servicing inside it. If you sell from a browser, the portal already does all of this without any integration.
JSON over HTTPS. Each message body is the NDC message in JSON, and the airline's answer comes back the same way. Every example in the guide is a captured exchange, not a hand-written one.
No. Agency Credit is the form of payment: NDC Deals extends credit to your agency, you send the amount, and the booking is drawn from your wallet. There is no card flow in the integration.
The airlines that are live on NDC Deals answer on the sandbox through their own test systems, so a sandbox booking looks exactly like a live one: a PNR, a payment time limit, ticket numbers.
Yes. The account admin signs in to the portal by email, password and WhatsApp OTP, and is the one who generates and reveals credentials. The credentials themselves are for your software.

Ready to build?

Register, open the sandbox, and hand the guide to your team or your coding assistant.

Register for API access How NDC works