Can my developer test the API with dummy bookings before we switch it on for my live website?

API & Integrations
0
Asked by Suresh Sinha 📅 Nov 4, 2026 6:06 AM

Can my developer test the API with dummy bookings before we switch it on for my live website?

Answer

0
Answered by eazyPNR Team 📅 Nov 4, 2026 6:15 AM

Yes, you should always test before you go live, and the normal way is to ask for test access at the time you set up your API connection rather than pointing a new booking engine straight at live inventory. Learning on real seats is how agents end up with holds they did not mean to make, names sent in the wrong format, or seats sitting unused until the release date passes.

Use the test stage to walk through the whole journey your staff and customers will actually follow with FD & Series Fares (Fixed Departures and Series Fares). That means searching, reading what comes back for each listing, holding a seat, sending the passenger name list before the name list deadline, correcting a name, and cancelling. Check that your engine displays the agent fare with your markup on it and never shows the net fare to the traveller, and that it reads the release date, the cut-off and the ticketing time limit from each listing instead of assuming one rule for everything, because those terms depend on the airline and on the seller's contract.

Also test what your engine does when something does not work. A hold can fail, a cut-off can pass while your customer is still deciding, and a seller can change terms on a block. Your engine should pass that message back to the agent clearly rather than quietly confirming a booking that was never made, since confusion at this stage is what later turns into disputes or an ADM.

To get started, register on eazyPNR to see the live seats, then ask for API access so your developer can test the full flow before you open it to your agents.

Saved.

New routes and seller tips, every week

One short email. Unsubscribe any time.