For the complete documentation index, see llms.txt. This page is also available as Markdown.

Standard booking

End-to-end Atlas booking steps from Search through order follow-up for partners who use Atlas as the main shopping and booking layer.

Path: Search → Verify → Order → Payment → Query Order

Use this page when Atlas is your main shopping and booking layer.

This page defines the end-to-end sequence for this path.

Use Booking steps when you need endpoint-level detail for one step.

When to use Standard booking

Use Standard booking when you need to:

  • start from Atlas search results

  • recheck fare and booking requirements before order creation

  • follow the standard booking sequence from search to ticketing

Full sequence

1

Call Search.

Keep routingIdentifier.

2

Verify

Call Verify before order creation.

Keep sessionId.

3

Optional ancillaries

This step is optional.

Use Optional ancillaries before order creation when seat or baggage upsell is part of your product.

4

Create Order

Call Create Order.

Keep orderNo.

5

Optional FR confirmation

This step is airline-specific.

Use Confirm Order (FR only) before payment when the airline requires it.

6

Payment & Ticketing

Call Payment & Ticketing.

Payment success does not always mean final ticketing is already complete.

7

Query Order

Use Query Order as the standard follow-up step after payment.

Keep following the order until it is ticketed or reaches another terminal state.

Use Post-payment polling for polling timing and retry guidance.

Key identifiers

  • Keep routingIdentifier after search.do

  • Keep sessionId after verify.do

  • Keep orderNo after order.do

  • Keep airline PNR and ticketNos after ticketing completes

Decision support

Use Booking decisions when you need to compare this path with Get Offer or Fulfilment.

Use API Reference when you need exact request and response fields.

Last updated

Was this helpful?