> For the complete documentation index, see [llms.txt](https://resources.atriptech.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://resources.atriptech.com/api-document/product-guides/booking/booking-flows/standard-booking-flow.md).

# Standard booking

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](/api-document/product-guides/booking/booking-step-guides.md) 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

{% stepper %}
{% step %}

### Search

Call [Search](/api-document/product-guides/booking/booking-step-guides/search.md).

Keep `routingIdentifier`.
{% endstep %}

{% step %}

### Verify

Call [Verify](/api-document/product-guides/booking/booking-step-guides/verify.md) before order creation.

Keep `sessionId`.
{% endstep %}

{% step %}

### Optional ancillaries

This step is optional.

Use [Optional ancillaries](/api-document/product-guides/booking/optional-ancillaries.md) before order creation when seat or baggage upsell is part of your product.
{% endstep %}

{% step %}

### Create Order

Call [Create Order](/api-document/product-guides/booking/booking-step-guides/create-order.md).

Keep `orderNo`.
{% endstep %}

{% step %}

### Optional FR confirmation

This step is airline-specific.

Use [Confirm Order (FR only)](/api-document/product-guides/booking/booking-step-guides/confirm-order.md) before payment when the airline requires it.
{% endstep %}

{% step %}

### Payment & Ticketing

Call [Payment & Ticketing](/api-document/product-guides/booking/booking-step-guides/payment-and-ticketing.md).

Payment success does not always mean final ticketing is already complete.
{% endstep %}

{% step %}

### Query Order

Use [Query Order](/api-document/product-guides/booking/booking-step-guides/query-order.md) 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](/api-document/product-guides/booking/booking-step-guides/query-order/post-payment-polling.md) for polling timing and retry guidance.
{% endstep %}
{% endstepper %}

### 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](/api-document/product-guides/booking/booking-overview/booking-decisions.md) when you need to compare this path with Get Offer or Fulfilment.

Use [API Reference](/api-document/api-reference.md) when you need exact request and response fields.