# Booking Overview

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

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

Use this section for the end-to-end booking flow.

<figure><img src="/files/DqGxAvaOLqUya9iuYXgU" alt=""><figcaption><p>Booking flow from search to payment and follow-up</p></figcaption></figure>

### Pages in this section

* [Search](/api-document/readme/booking-overview/search.md)
* [Get Offer](/api-document/readme/booking-overview/get-offer.md)
* [Verify](/api-document/readme/booking-overview/verify.md)
* [Create Order](/api-document/readme/booking-overview/create-order.md)
* [Confirm Order](/api-document/readme/booking-overview/confirm-order.md)
* [Payment & Ticketing](/api-document/readme/booking-overview/payment-and-ticketing.md)
* [Query Order](/api-document/readme/booking-overview/query-order.md)
* [Seats & Baggage](/api-document/readme/booking-overview/seats-and-baggage.md)

### What this section covers

* Search for flight offers
* Retrieve offers through an independent Get Offer flow
* Verify fares and routing
* Create orders
* Confirm FR orders when required
* Pay and issue tickets
* Retrieve booking details
* Run advanced search flows
* Query seats and luggage

### Typical flow

{% stepper %}
{% step %}

### Standard search path

Search for available offers and keep the returned identifiers.
{% endstep %}

{% step %}

### Verify

Recheck fare, routing, and booking requirements before order creation.
{% endstep %}

{% step %}

### Order

Create the booking with passenger, contact, and ancillary details.
{% endstep %}

{% step %}

### Optional FR confirmation

Most airlines skip this step.

If the airline is FR, call `orderCommit.do` and wait for user confirmation before payment.
{% endstep %}

{% step %}

### Pay

Complete payment and wait for ticketing to finish.
{% endstep %}
{% endstepper %}

### Alternate flow

Use this path when you already know the target itinerary or need an independent price check.

{% stepper %}
{% step %}

### Get Offer

Call `getOffers.do` and keep the returned `OfferId`.
{% endstep %}

{% step %}

### Optional ancillaries

Query `getLuggage.do` or `seatAvailability.do` only when baggage or seat choice matters before booking.
{% endstep %}

{% step %}

### Order

Create the booking with `order.do`.
{% endstep %}

{% step %}

### Pay

Complete payment with `pay.do`.
{% endstep %}
{% endstepper %}

### Main APIs

* `search.do`
* `getOffers.do`
* `verify.do`
* `order.do`
* `orderCommit.do`
* `pay.do`
* `queryOrderDetails.do`
* `smartSearch.do`
* `seatAvailability.do`
* `getLuggage.do`

### Use this when you need

* A standard search-to-ticket flow
* An independent offer lookup and price-check flow
* FR order confirmation support when applicable
* Seat and baggage selection
* Real-time or smart search options

### Full API reference

Use endpoint-level details here:

[Booking APIs](/api-document/api-reference/booking-apis.md)

### Related pages

* [Quick Start](/api-document/readme/quick-start.md)
* [Get Sandbox Credentials](/api-document/readme/quick-start/making-requests.md)
* [Error Codes](/api-document/troubleshooting-and-support/errors-handing.md)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://resources.atriptech.com/api-document/readme/booking-overview.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.