Booking paths
End-to-end booking paths for standard shopping, known-itinerary offer lookup, and Fulfilment API.
Last updated
Was this helpful?
End-to-end booking paths for standard shopping, known-itinerary offer lookup, and Fulfilment API.
Use this section for end-to-end Atlas API booking paths.
🆕 Featured new path: Use 🆕 Fulfilment API when you start with getOfferPrice.do and can begin payment immediately after order creation.
Start here when you need to:
compare the three booking paths
decide whether to start with search.do, getOffers.do, or getOfferPrice.do
match the journey to your payment and ticketing constraints
Use 🆕 Fulfilment API when you need broader offer visibility and can start payment immediately after order creation.
Start with getOfferPrice.do.
Follow the stricter Fulfilment API timing rules.
Use Standard booking when Atlas is your main shopping layer.
Start with search.do.
Then continue with verify.do before order.do.
Use Get Offer when the itinerary is already known or when you need an independent price check.
Start with getOffers.do.
Then continue with order.do using OfferId.
Need help choosing between entry paths?
Use Search vs Offer and Get Offer vs Fulfilment API.
Each path page contains the full end-to-end step sequence for that path.
Use Booking decisions for restart choices, API boundaries, and edge cases.
Use Booking Overview.
Use Booking steps.
Use Optional ancillaries.
Last updated
Was this helpful?
Was this helpful?