Query Order
Atlas API order query flow for booking status, ticketing progress, airline PNR, and final order follow-up.
Last updated
Was this helpful?
Atlas API order query flow for booking status, ticketing progress, airline PNR, and final order follow-up.
💬 Need help? If you're stuck, ask Eva in the Help Center for instant diagnostics.
Use this page to check the latest booking state.
This is the standard follow-up step after pay.do.
If you need polling rules and timing guidance, use Post-payment polling.
Start here when you need to:
track ticketing after pay.do
confirm whether an order is already paid or ticketed
read airline PNR and ticket details after fulfilment
queryOrderDetails.do?Call it after order.do or pay.do when you need the latest order state.
Use it as the main follow-up API until the booking reaches the final state.
Check orderStatus, ticketStatus, airline PNR details, and ticket numbers.
Use these fields to confirm whether ticketing is still in progress or already complete.
queryOrderDetails.do
Poll ticketing progress
Retrieve booking and passenger details
Confirm airline PNR and final status
orderStatus
ticketStatus
Airline PNR details
Ancillary and fare data
Use it to decide:
whether payment should be retried or not
whether ticketing is still processing
whether airline PNR and ticket numbers are already available
whether post-booking actions can start
Use queryOrderDetails.do as the main status source after payment.
Webhook can help, but it should not be your only confirmation path.
If payment may already be in progress or completed, query the order before any retry.
If the order came from getOfferPrice.do, monitor it more aggressively.
Use order query to confirm whether the order is still ticketing, already ticketed, or already cancelled by timeout.
Do not keep retrying payment when the order is already close to the 5-minute fulfilment deadline.
See endpoint-level details here:
Last updated
Was this helpful?
Was this helpful?