Can I run test bookings through the eazyPNR API before I let my real customers book?
API & IntegrationsCan I run test bookings through the eazyPNR API before I let my real customers book?
Can I run test bookings through the eazyPNR API before I let my real customers book?
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 to build and test against test credentials first, confirm that every step behaves the way your booking engine expects, and only then switch over to live listings and real passengers.
The things worth testing are the ones that bite you later. Run a search and see how availability comes back. Hold a seat and watch how the deadlines arrive, because the name list deadline, the release date, the cut-off and the ticketing time limit all have to be visible to your staff and, where it matters, to your customer. Then push a passenger name list through and confirm you get the PNR back cleanly. Just as important, test the unhappy paths. See what your engine does when a deadline has already passed, when the seats you were holding are no longer there, or when a name list is rejected because a spelling does not match the passport. A booking engine that quietly swallows those messages is how agents end up with a half finished booking and an avoidable ADM.
Fare handling deserves a test of its own. The seller publishes a net fare, your engine applies your markup, and your customer sees only your agent fare. Check that logic on a few test cases before anything goes live, and check it again for any seller whose contract works differently, because conditions on changes, names and release do vary by airline and by the seller's own agreement.
Register on eazyPNR, get verified, and ask for API access so your developer can test against it and you can see live seats while the work is going on.
One short email. Unsubscribe any time.