> 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/readme/booking-overview/verify.md).

# Verify

{% 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 page after offer selection.

{% hint style="info" %}
Use `bookingRequirement` from the verify response as the source of truth for booking input.

It tells you which passenger and document fields are required for `order.do`.
{% endhint %}

Start here when you need to:

* recheck fare and routing before booking
* get the required passenger and document fields
* create a fresh `sessionId` for `order.do`
* keep a valid `sessionId` for `seatAvailability.do`

### FAQ

#### When should I call `verify.do`?

Call `verify.do` after `search.do` and before `order.do`.

Use it to refresh fare, routing, and booking requirements close to booking time.

Use a `routingIdentifier` that is no more than 6 hours old.

#### What should I read from the verify response?

Read `sessionId`, latest fare details, ancillary options, and `bookingRequirement`.

Treat `bookingRequirement` as the source of truth for the order request.

### Main API

* `verify.do`

### Inputs

* `routingIdentifier` from search, valid for up to 6 hours

### Key outputs

* `sessionId` for order creation and seat lookup, valid for up to 2 hours
* Latest fare and routing details
* `bookingRequirement` for required passenger and document fields
* Ancillary options

### What should you keep from verify?

Keep:

* `sessionId` for `order.do`
* `sessionId` for `seatAvailability.do` when seat selection is needed before booking
* `bookingRequirement` for required input fields
* current ancillary options when baggage or seats matter before booking

Use `sessionId` within 2 hours.

Do not reuse an expired `sessionId`.

If your seat request arrives later from an upstream system, keep enough itinerary linkage to match that request back to the current `sessionId`.

### Use this when you need

* Fare recheck before booking
* Final validation of routing details
* Required passenger and document rules for `order.do`

### What comes next?

Use [Create Order](/api-document/readme/booking-overview/create-order.md) with the returned `sessionId`.

If price, inventory, or ancillaries changed, use the verify result as the current source of truth.

### Related pages

* [Search](/api-document/readme/booking-overview/search.md)
* [Create Order](/api-document/readme/booking-overview/create-order.md)
* [Booking APIs](/api-document/api-reference/booking-apis.md)

### Full API reference

See endpoint-level details here:

* [Verify](/api-document/api-reference/booking-apis/verify.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.