When my booking engine books seats through your API, does the PNR come back straight away?
API & IntegrationsWhen my booking engine books seats through your API, does the PNR come back straight away?
When my booking engine books seats through your API, does the PNR come back straight away?
Yes, but what comes back depends on the seller. When your booking engine confirms seats on a block through the eazyPNR API, the response always carries a booking reference for that block on eazyPNR. Where the seller has set the block for instant confirmation, the airline PNR comes back in the same response and you can show it to your customer right away. Where the seller works on request, the API returns the booking as pending and the PNR follows once the seller confirms, so your engine needs to handle both cases cleanly.
The PNR itself sits in the airline system under the seller who holds the block, not under your engine, so the name list rules of that block still apply to you. On many blocks you can confirm seats before you have every passenger name, and the names go in up to the name list deadline. Whether the airline will let a PNR sit with incomplete names, and in what form, depends on the airline and on the seller's contract, so read what the block tells you rather than assuming one rule everywhere.
For that reason, build your engine to read the name list deadline, the release date and the ticketing time limit that come back with the block, and show your customer a held message rather than a plain ticket confirmed until ticketing has actually happened. Release the ticket number only once the seats are ticketed. That habit keeps your agent fare, your markup and your customer promise in line with the net fare rules of the block, and keeps you away from ADM trouble later.
Register on eazyPNR to see live seats, look at how a block and its deadlines come back on a real listing, and then connect your engine to the part you actually need.
One short email. Unsubscribe any time.