Order Maintenance
Atlas API order maintenance for order regeneration, ticket stop, and operational order lookup after booking.
Last updated
Was this helpful?
Atlas API order maintenance for order regeneration, ticket stop, and operational order lookup after booking.
💬 Need help? If you're stuck, ask Eva in the Help Center for instant diagnostics.
Use this page for follow-up order actions outside the standard booking flow.
Start here when you need to:
regenerate an expired or failed order
stop ticketing when the flow supports it
look up orders for operational follow-up
Use this page for operational order actions that happen outside the standard search-to-ticket flow.
Use regenerateOrder.do for eligible order regeneration, stopTicket.do when ticketing must be stopped, and orderList.do when you need operational order lookup.
Yes, when the recovery path supports regeneration for that order state.
Confirm the original order is already unusable first.
Keep the fulfillment-flow identity on the regenerated order when the downstream flow expects it.
regenerateOrder.do
stopTicket.do
orderList.do
Regenerate expired or failed orders
Stop ticketing operations when supported
Search operational order lists
Recover eligible getOfferPrice.do orders after cancellation or airline-side payment failure
Use maintenance actions carefully for getOfferPrice.do orders.
Confirm the original order reached a final cancelled or unpayable state before regeneration.
Do not use maintenance actions to stretch the 5-minute ticketing deadline.
Open the exact endpoint page below for request and response details, then reconcile the result with the current order state if needed.
See endpoint-level details here:
Last updated
Was this helpful?
Was this helpful?