Atlas API concepts
Definitions of Atlas API booking flows, identifiers, order lifecycle terms, and integration concepts.
Last updated
Was this helpful?
Definitions of Atlas API booking flows, identifiers, order lifecycle terms, and integration concepts.
This glossary defines the terms used across Atlas API documentation.
Use it to interpret workflow guides, endpoint references, and error guidance consistently.
Atlas API supports flight shopping, booking, payment, ticketing, and post-booking operations.
Start with What is Atlas API? for product capabilities and documentation entry points.
The standard path starts with search.do.
It uses routingIdentifier for verify.do, then sessionId for order.do.
See Standard booking.
Get Offer prices a known itinerary with getOffers.do.
It returns an OfferId used for order creation.
See Get Offer.
Fulfilment API uses getOfferPrice.do to price an offer.
Its flow uses a short-lived OfferId and fast payment after order creation.
See Fulfilment API.
routingIdentifiersearch.do returns this route token.
Pass it to verify.do in the standard booking flow.
sessionIdverify.do returns this booking context.
Pass it to order.do in the standard booking flow.
OfferIdgetOffers.do or getOfferPrice.do returns this offer context.
Use it for order.do in its matching booking flow.
orderNoorder.do returns the Atlas order identifier.
Use it for payment, order queries, ticketing follow-up, and post-booking actions.
See Identifiers for validity periods, flow mapping, and refresh rules.
An order is created with order.do.
Payment and ticketing start through pay.do where the flow requires it. Use queryOrderDetails.do to check order status and ticketing progress.
See Payment & Ticketing and Query Order.
A webhook delivers Atlas event notifications to your endpoint.
Use webhooks for ticketing, void, schedule-change, airline-status, email, and incident notifications.
See Webhook Overview.
Last updated
Was this helpful?
Was this helpful?