> 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/what-is-atlas-api.md).

# What is Atlas API?

Atlas API documentation for flight shopping, booking, ticketing, post-booking servicing, webhooks, and integration support.

Atlas API supports flight shopping, booking, payment, ticketing, and post-booking operations.

Use it to integrate air-travel booking workflows into your product. The documentation covers implementation guidance, endpoint schemas, and operational support.

### Explore Atlas API capabilities

Build a complete flight-shopping and fulfilment experience. Start with the capabilities that create choice, conversion, and payment flexibility.

#### Product capabilities

<table data-view="cards"><thead><tr><th>Capability</th><th data-card-target data-type="content-ref">Guide</th></tr></thead><tbody><tr><td><strong>Fare choice and Fare Family</strong><br>Return flight offers and, where supported, multiple fare families for the same flight. Let travellers compare price and included benefits before booking.</td><td><a href="/api-document/api-reference/booking-apis/search.md">Search</a></td></tr><tr><td><strong>Baggage and seat selection</strong><br>Show included baggage, sell eligible baggage, and offer seats during booking. Availability depends on the airline, itinerary, and current order context.</td><td><a href="/api-document/product-guides/booking/optional-ancillaries.md">Optional ancillaries</a></td></tr><tr><td><strong>Atlas VCC rebate and payment choice</strong><br>Pay eligible Atlas fares with your Atlas balance to receive Atlas VCC rebates directly in the quoted price. Customer-owned VCC pass-through is a separate payment method and does not include this rebate.</td><td><a href="/api-document/support-and-reference/troubleshooting-and-support/faqs/atlas-api-payments.md">Payments</a></td></tr></tbody></table>

#### Choose an integration path

The booking paths are different entry points into the same product capability set.

<table data-view="cards"><thead><tr><th>Path</th><th data-card-target data-type="content-ref">Guide</th></tr></thead><tbody><tr><td><strong>Search</strong><br>Use Atlas as your main shopping layer. Search, verify the selected offer, then create and pay for the order.</td><td><a href="/api-document/product-guides/booking/booking-flows/standard-booking-flow.md">Standard booking</a></td></tr><tr><td><strong>Get Offer</strong><br>Use a known itinerary or flight selection to retrieve an independent, current offer before booking.</td><td><a href="/api-document/product-guides/booking/booking-flows/get-offer-flow.md">Get Offer</a></td></tr><tr><td><strong>Get Offer Price</strong><br>Use Fulfilment when you already hold the fare or order context and need Atlas to complete verification and ticketing.</td><td><a href="/api-document/product-guides/booking/booking-flows/fulfillment-flow.md">Fulfilment API</a></td></tr></tbody></table>

#### Full lifecycle capabilities

<table data-view="cards"><thead><tr><th>Capability</th><th data-card-target data-type="content-ref">Guide</th></tr></thead><tbody><tr><td><strong>Post-booking servicing</strong><br>Manage refunds, voids, eligible ancillary purchases, and booking records after purchase.</td><td><a href="/api-document/product-guides/post-booking.md">Post-booking</a></td></tr><tr><td><strong>Notifications and operations</strong><br>Receive booking updates, reconcile final order status, and run event-driven operational workflows.</td><td><a href="/api-document/product-guides/extensions-and-integrations/webhook-overview.md">Webhook Overview</a></td></tr><tr><td><strong>Data and special integrations</strong><br>Build local shopping experiences with Atlas data and support airline-specific business flows.</td><td><a href="/api-document/product-guides/extensions-and-integrations.md">Extensions &amp; integrations</a></td></tr><tr><td><strong>Integration delivery</strong><br>Set up sandbox access, validate UAT, prepare production, and use implementation tools.</td><td><a href="/api-document/readme-1.md">Integration Guides</a></td></tr></tbody></table>

### What can you build with Atlas API?

Atlas API supports these core workflows:

* Search and price flight offers.
* Create, pay for, and follow flight orders.
* Manage refunds, voids, ancillaries, and booking records.

### How do I start an Atlas API integration?

Start with [Quick Start](/api-document/readme-1/quick-start.md). It leads through sandbox access, development, UAT validation, and production go-live.

Use [Integration Guides](/api-document/readme-1.md) for the complete implementation lifecycle.

### Which Atlas API booking flow should I use?

Choose a path based on your shopping model and booking requirements.

* Use [Standard booking](/api-document/product-guides/booking/booking-flows/standard-booking-flow.md) for the main search-to-order journey.
* Use [Get Offer](/api-document/product-guides/booking/booking-flows/get-offer-flow.md) for known itineraries.
* Use [Fulfilment API](/api-document/product-guides/booking/booking-flows/fulfillment-flow.md) for its offer-pricing path.

See [Booking Overview](/api-document/product-guides/booking/booking-overview.md) before implementing a flow.

### Where are the endpoint specifications?

[API Reference](/api-document/api-reference.md) contains request schemas, response fields, and endpoint samples.

Use [Product Guides](/api-document/product-guides.md) first for workflow choices. Use API Reference for field-level implementation details.

### Where can I get help?

[Support & Reference](/api-document/support-and-reference.md) covers FAQs, error codes, sandbox test data, and operational utilities.

Start with [Troubleshooting & Support](/api-document/support-and-reference/troubleshooting-and-support.md) when an integration needs diagnosis.

### Explore Atlas API documentation

* [Integration Guides](/api-document/readme-1.md)
* [Product Guides](/api-document/product-guides.md)
* [API Reference](/api-document/api-reference.md)