API & Integrations
Questions in this category.
Total: 22
Yes, your booking engine picks up new blocks on its own, so you do not have to load routes one by one. The API runs off the same live search your staff use on screen. You send ....
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 ....
Yes, the API is built to carry a sale all the way through, not just the search. Your booking engine can pull live FD & Series Fares (Fixed Departures and Series Fares) listing ....
Yes, you can. eazyPNR has an API that lets your own booking engine, website or mobile app search and sell the same FD & Series Fares (Fixed Departures and Series Fares) listin ....
Yes, on most blocks the seat is confirmed the moment your engine sends the booking through, but whether it is instant or on request depends on the seller and on how that parti ....
Yes, those dates come through with the listing. When your booking engine asks the eazyPNR API for what is available, it does not just get the net fare and the routing, it also ....
Yes, and you should. No sensible integration goes straight to live traffic. When you register on eazyPNR and ask for API access, the right order of work is for your developer ....
Yes, they can sit side by side in the same search results. The eazyPNR API returns FD & Series Fares (Fixed Departures and Series Fares) listings as structured data, so your d ....
Yes, in the normal flow the name list goes out and the PNR comes back over the same API connection, so your team does not have to drop into email for the routine steps. When y ....
No, you do not need a separate connection for each consolidator. One API link to eazyPNR gives your booking engine access to the FD & Series Fares (Fixed Departures and Series ....
Saved.