Services · APIs
A flight booking API that carries the whole ticket lifecycle
Showing fares is the easy part. A flight booking API earns its keep after the customer clicks 'book': holding the seat, issuing the ticket before the time limit, and handling the schedule change that arrives three weeks later. Avunzo, Voraal's unified travel API, gives your product one booking model for GDS, NDC and low-cost carrier (LCC) content.
Built for
- OTAs
- Corporate booking tools
- Banks & wallets
- Super-apps
- Agencies with developers
In brief
What is a flight booking API?
A flight booking API is a programmable interface that lets software create, pay for, ticket and service airline reservations, not just display fares. Voraal's Avunzo exposes one REST/JSON booking flow for Amadeus, Sabre and Travelport GDS content, NDC airline offers and low-cost carriers, with webhooks for ticketing, schedule-change and refund events, so your platform never has to speak each channel's native protocol.
By the Voraal team · Updated
Booking is a state machine, not a single call
Teams new to air often model a booking as one request that returns 'confirmed'. In practice a flight reservation moves through states: an offer is selected, re-priced, held as a PNR or an airline order, paid, ticketed (or fulfilled, for NDC), and then lives on through voids, refunds, reissues and involuntary changes. Each transition has its own failure modes and deadlines, and each channel names them differently.
A flight booking API worth integrating gives you one set of states for every source. Avunzo normalises the order so that a GDS PNR, an NDC order and an LCC booking reference all surface as an order with the same fields, status values and documents. Your code checks one status field; Voraal's core tracks which underlying system holds the record. For the shopping side of the problem (caching, volatility, ranking), see the flight search and pricing API.
The booking flow, call by call
Endpoint names follow Avunzo's illustrative flow. What happens behind each call depends on the channel.
| Step | Call (illustrative) | GDS content | NDC airline | Low-cost carrier |
|---|---|---|---|---|
| Re-price | POST /v1/offers/price | Fare re-quoted against current availability and fare rules | Offer re-priced by the airline; offer ID may change | Basket price re-checked on the carrier's site or API |
| Create order | POST /v1/orders | PNR created with segments, names, contacts and a ticketing time limit | Airline order created; payment may be due immediately | Booking made; most LCCs take payment at booking |
| Fulfil | POST /v1/orders/{id}/issue | Ticket issued through the GDS and reported to BSP where applicable | Airline issues the ticket or electronic document | Confirmation and booking reference returned |
| Retrieve | GET /v1/orders/{id} | PNR read and mapped to the order model | Order retrieved from the airline | Booking retrieved from the carrier |
| Service | Webhook + order calls | Void, refund, reissue and schedule change | Order change or cancel, by airline capability | Change or cancel, subject to carrier rules |
Coverage per supplier, including which servicing actions are automated, is confirmed during discovery.
How a booking runs through Avunzo
- 01
Lock the offer
Re-price the chosen offer immediately before collecting passenger data. If the price or availability moved, the response tells you, and you show the new total rather than failing at payment.
- 02
Create the order with an idempotency key
Avunzo accepts idempotent booking requests. Send the same key on a retry after a timeout and you receive the original order instead of a duplicate seat and a duplicate charge.
- 03
Pay and issue within the time limit
GDS holds carry a ticketing deadline. Your platform takes payment, then calls issue. For agencies on Rezencia, rule-based ticketing decides which GDS issues for a given airline.
- 04
Listen for what changes later
Webhooks push ticketing, schedule-change and refund events to your endpoint, so you learn about a retimed flight from the API, not from the traveller at the airport.
What the flight booking API gives you
One order model
GDS, NDC and LCC bookings share one schema for passengers, segments, fares, taxes, ancillaries and documents.
Ticketing and cancellation
Book, ticket and cancel in one flow, with the ticket numbers or airline documents attached to the order.
Event webhooks
Booking status, ticketing, schedule-change and refund events sent to your system as they happen.
Idempotent requests
Safe retries on booking calls, so network timeouts do not create double bookings.
Fare families and ancillaries
NDC offers include fare families and ancillaries where the airline provides them.
Scoped credentials
Separate keys per environment and channel, with usage reporting and rate limits per key.
Business applications
An OTA uses the booking API behind its own checkout and keeps its brand, payment page and customer account. A wallet or bank sells flights inside an app customers already trust; the wallet handles payment while Avunzo handles content and fulfilment. A corporate booking tool books within policy and needs reliable change and refund handling because business trips move. An agency with its own developers can build a branded front end on the same content Voraal's Rezencia platform uses.
If you sell from Pakistan and need BSP ticketing context, the flight booking API provider page for Pakistan covers the local set-up.
Implementation process
- 01
Discovery
Agree routes, channels, payment model and who issues tickets. Supplier coverage and the commercial set-up (Voraal's agreements or your own credentials) are confirmed here.
- 02
Sandbox build
Approved teams receive sandbox keys, test data and the OpenAPI specification. An integration engineer works with your team through build and testing.
- 03
Scenario testing
Run one-way, return, multi-city, infant, ancillary, void and refund scenarios end to end, including your webhook receiver.
- 04
Production
Production credentials are issued after testing. Start with limited traffic and watch error codes and ticketing completion before widening.
Common challenges and how to handle them
Where flight bookings go wrong
- Price changes between search and payment
- Duplicate bookings from client retries
- Missed ticketing time limits on held PNRs
- Name or passport data rejected after booking
- Schedule changes nobody sees until departure
What to build in
- Re-price immediately before checkout and show the new total
- An idempotency key on every booking request
- Pay-then-issue logic that runs well before the deadline
- Validation of names and documents before the order call
- A webhook handler that stores events and alerts operations
How Voraal delivers this
The products behind it.
Does a flight booking API also issue the ticket?
With Avunzo, yes: booking and issuing are separate calls in the same flow, so you can take payment between them. Whether tickets are issued under your own IATA set-up or another arrangement is agreed during discovery.
What happens to a held booking that is never paid?
GDS holds carry an airline ticketing time limit; if the ticket is not issued in time, the airline may cancel the segments. Your platform should either issue or cancel well before that deadline. LCC and many NDC bookings require payment at the point of booking instead.
How are NDC orders different from GDS PNRs for my code?
Behind the scenes they are different records with different servicing rules. In Avunzo both come back as an order with the same fields and statuses; differences such as which changes an airline allows are shown as capabilities on the order.
Can we receive schedule changes automatically?
Yes. Schedule-change events are delivered by webhook, together with booking status, ticketing and refund events, so your system can notify the traveller or open a task for your operations team.
What should we do if the booking call times out?
Retry with the same idempotency key. Avunzo returns the order created by the first attempt if it succeeded, rather than creating a second booking.
Can we book ancillaries such as bags or seats?
Where an NDC airline provides fare families and ancillaries in its offers, Avunzo returns them. Ancillary coverage differs by airline and channel, and is confirmed per supplier during discovery.
Let’s build what comes next.
Tell us how your travel business works. We’ll recommend the right products and walk you through them on your own use case.