> 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-step-guides/create-order.md).

# Create Order

{% hint style="info" %}
💬 **Need help?** If you're stuck, ask Eva in the Help Center for instant diagnostics.

<a href="https://www.atriptech.com/" class="button primary" data-icon="comments">Ask Eva</a>
{% endhint %}

Use this page to place the booking after pricing or verification.

{% hint style="info" %}
Before calling `order.do`, read `bookingRequirement` from the current pricing or verify response.

Use it to decide which passenger and document fields are required for this booking.
{% endhint %}

Start here when you need to:

* create the booking after `verify.do`, `getOffers.do`, or `getOfferPrice.do`
* build the request from the current `sessionId` or `OfferId`
* capture the `orderNo` for payment and follow-up

### FAQ

#### What do I need before `order.do`?

You need a fresh `sessionId` or `OfferId`, the current `bookingRequirement`, passenger details, contact details, and ancillary selections when required.

Use the current booking context without long delay.

If seat selection is included, decide the seat fulfillment handling mode before `order.do`.

#### What should I keep after `order.do`?

Keep the returned `orderNo`.

Use it for payment, order query, and later follow-up.

### Main API

* `order.do`

### Inputs

* `sessionId` from verify or `OfferId` from Get Offer or Get Offer Price
* `bookingRequirement` from the current pricing context
* Passenger details
* Contact details
* Ancillary selections when needed
* Seat fulfillment handling mode when seat selection is included

### Key outputs

* `orderNo`
* Initial booking status
* Airline and pricing details tied to the order

### Common build rules

Use `bookingRequirement` to decide which passenger and document fields are mandatory.

Keep ancillary mapping consistent with the current booking context.

Do not use a stale `sessionId` or `OfferId`.

Do not build the order from stale pricing or verify data.

If seat selection is included, pass the seat fulfillment handling mode in the order request.

Use the same order request to define how Atlas should handle seat fulfillment failure.

If the order comes from the fulfillment flow, create it only when payment can start immediately.

Fulfillment-flow orders use a 5-minute payment and ticketing window after order creation.

Supported modes:

* `STOP_TICKET` — stop ticket issuance, cancel the whole order, and refund it
* `STOP_SEAT` — issue the ticket, remove the seat, and refund the seat amount
* `SIMILAR_SEAT` — issue the ticket with a similar seat selected by operations

For deposit customers, `STOP_SEAT` may require a split fund order and a `credit note`.

### Use this when you need

* Standard order creation
* FR order creation before commit
* Booking with ancillaries

### What comes next?

#### Standard payment path

Continue to [Payment & Ticketing](/api-document/product-guides/booking/booking-step-guides/payment-and-ticketing.md) with `orderNo`.

#### FR flow

If the airline is FR, complete [Confirm Order](/api-document/product-guides/booking/booking-step-guides/confirm-order.md) before payment.

### Related pages

* [Verify](/api-document/product-guides/booking/booking-step-guides/verify.md)
* [Get Offer](/api-document/product-guides/booking/booking-step-guides/get-offer.md)
* [Get Offer Price](/api-document/product-guides/booking/booking-step-guides/get-offer-price.md)
* [Payment & Ticketing](/api-document/product-guides/booking/booking-step-guides/payment-and-ticketing.md)
* [Booking APIs](/api-document/api-reference/booking-apis.md)

### Full API reference

See endpoint-level details here:

* [Create Order](/api-document/api-reference/booking-apis/create-order.md)