> 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.md).

# Atlas API Documentation Updates

{% 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 track the latest Atlas API documentation updates and jump to the right guide faster.

Use it as the update feed for **Support & Reference** when you want the newest guidance, revised troubleshooting content, or newly added entry points.

{% hint style="warning" %}
**🆕 Featured new product:** [🆕 Fulfilment API](/api-document/product-guides/booking/booking-flows/fulfillment-flow.md) is now available for partners using `getOfferPrice.do` and immediate payment after order creation.
{% endhint %}

It highlights new guides, major troubleshooting improvements, and the next pages to read by use case.

Start here if you need to:

* find the newest Atlas API guides
* see what changed for sandbox, booking, payment, or troubleshooting
* choose the right page to read next

### Featured new product

Start with [🆕 Fulfilment API](/api-document/product-guides/booking/booking-flows/fulfillment-flow.md) when you need the new `getOfferPrice.do` booking path.

Then use:

* [Get Offer vs Fulfilment API](/api-document/product-guides/booking/booking-overview/booking-decisions/get-offer-vs-get-offer-price.md) for flow choice
* [Get Offer Price](/api-document/product-guides/booking/booking-step-guides/get-offer-price.md) for entry-step timing and recovery rules
* [Fulfilment API FAQ](/api-document/support-and-reference/troubleshooting-and-support/faqs/fulfilment-api-faq.md) for fit, coexistence, pricing, and payment questions
* [Get Offer Price](/api-document/api-reference/booking-apis/get-offer-price.md) for request and response fields

### FAQ

#### What changed in the Atlas API docs recently?

Recent updates added booking-flow identifier guidance, clarified when to use `search.do` versus `getOffers.do`, explained `429` versus `110`, added decision guidance for `202` versus `301` versus `308`, clarified the Verify versus Create Order boundary, added polling guidance after `pay.do`, clarified payment-state recovery for `401`, `402`, `404`, `406`, and `615`, documented ancillary `productCode` freshness, added restart guidance for Search versus Verify versus Get Offer, clarified booking input errors `307`, `327`, and `410`, clarified ancillary mapping errors `309` and `409`, documented seat fallback modes, clarified transient verify and order failures `205`, `299`, and `304`, documented duplicate booking handling for `318` and `608`, added request-limit guidance for selected pre-booking APIs, published multi-channel notification setup, updated the ATRIP UAT flow, refined void guidance, and clarified seat-availability calling rules.

Use the change log below when you need page-level detail.

#### Where should a new integration team start?

Start with [Quick Start](/api-document/readme-1/quick-start.md).

Then use [Integration Guides](/api-document/readme-1.md), [Booking Overview](/api-document/product-guides/booking/booking-overview.md), and [Error Codes](/api-document/support-and-reference/troubleshooting-and-support/errors-handing.md).

#### Which pages should I check for request-limit guidance?

Start with [Booking Overview](/api-document/product-guides/booking/booking-overview.md), [Search](/api-document/product-guides/booking/booking-step-guides/search.md), [Search & Booking](/api-document/support-and-reference/troubleshooting-and-support/faqs/atlas-api-search-and-book.md), and [Error Codes](/api-document/support-and-reference/troubleshooting-and-support/errors-handing.md).

### Popular starting points

#### New integration

Start with [Quick Start](/api-document/readme-1/quick-start.md) and [Integration Guides](/api-document/readme-1.md).

#### Booking flow

Start with [🆕 Fulfilment API](/api-document/product-guides/booking/booking-flows/fulfillment-flow.md), [Booking Overview](/api-document/product-guides/booking/booking-overview.md), and [Search & Booking](/api-document/support-and-reference/troubleshooting-and-support/faqs/atlas-api-search-and-book.md).

Use [Identifiers](/api-document/product-guides/booking/booking-overview/identifiers.md) when you need the right token for the next step.

Use [Verify vs Order](/api-document/product-guides/booking/booking-overview/booking-decisions/verify-vs-order.md) when the booking boundary is the main question.

Use [Restart from Search vs Verify vs Get Offer](/api-document/product-guides/booking/booking-overview/booking-decisions/restart-point.md) when the main question is where to restart.

Use [Seat fallback modes](/api-document/product-guides/booking/optional-ancillaries/seats-and-baggage/seat-fallback-modes.md) when paid seat failure behavior must be defined before booking.

#### Troubleshooting

Start with [Error Codes](/api-document/support-and-reference/troubleshooting-and-support/errors-handing.md) and [FAQs](/api-document/support-and-reference/troubleshooting-and-support/faqs.md).

Use [429 vs 110](/api-document/support-and-reference/troubleshooting-and-support/errors-handing/429-vs-110.md) when request frequency or search concurrency is the main issue.

Use [202 vs 301 vs 308](/api-document/support-and-reference/troubleshooting-and-support/errors-handing/202-vs-301-vs-308.md) when you need to know which earlier step must be refreshed.

Use [402 vs 404 vs 406 vs 615](/api-document/support-and-reference/troubleshooting-and-support/errors-handing/402-vs-404-vs-406-vs-615.md) when the main risk is duplicate or unnecessary payment retry.

Use [307 vs 327 vs 410](/api-document/support-and-reference/troubleshooting-and-support/errors-handing/307-vs-327-vs-410.md) and [309 vs 409](/api-document/support-and-reference/troubleshooting-and-support/errors-handing/309-vs-409.md) when order input or ancillary mapping is the main failure area.

Use [401 vs 402 vs 404](/api-document/support-and-reference/troubleshooting-and-support/errors-handing/401-vs-402-vs-404.md) when the main question is whether the order expired or was already paid.

### Latest Atlas API documentation updates

#### VOID airline coverage expansion

Updated the VOID documentation to show the current supported airline scope.

What changed:

* documented 23 supported VOID airlines across the Americas, Europe, Japan, and Korea
* marked `ZG` as supported only for US routes
* added the latest newly supported airlines: `TS`, `Y4`, `EI`, and `VF`

Read next:

* [Void workflow](/api-document/product-guides/post-booking/void.md)
* [Void](/api-document/api-reference/post-booking-apis/void.md)
* [Refund, Query & Post-booking Errors](/api-document/support-and-reference/troubleshooting-and-support/errors-handing/refund-query-and-post-booking-errors.md)

#### Fulfilment API and `getOfferPrice.do` launch

Published the new Fulfilment API product path for `getOfferPrice.do` and updated the main booking entry pages to surface it faster.

What changed:

* added [🆕 Fulfilment API](/api-document/product-guides/booking/booking-flows/fulfillment-flow.md) for the end-to-end product flow
* added [Get Offer Price](/api-document/product-guides/booking/booking-step-guides/get-offer-price.md) for entry-step timing, retry rules, and recovery handling
* added [Fulfilment API FAQ](/api-document/support-and-reference/troubleshooting-and-support/faqs/fulfilment-api-faq.md) for product fit, coexistence with existing interfaces, pricing, and payment questions
* added [Get Offer vs Fulfilment API](/api-document/product-guides/booking/booking-overview/booking-decisions/get-offer-vs-get-offer-price.md) to clarify when to use `getOffers.do` versus `getOfferPrice.do`
* added [Get Offer Price](/api-document/api-reference/booking-apis/get-offer-price.md) under API Reference
* updated [Booking Overview](/api-document/product-guides/booking/booking-overview.md), [Payment & Ticketing](/api-document/product-guides/booking/booking-step-guides/payment-and-ticketing.md), [Query Order](/api-document/product-guides/booking/booking-step-guides/query-order.md), [Create Order](/api-document/product-guides/booking/booking-step-guides/create-order.md), [Orders & Ticketing](/api-document/support-and-reference/troubleshooting-and-support/faqs/atlas-api-order.md), and [API Request Limits](/api-document/product-guides/booking/booking-overview/api-request-limits.md)

Read next:

* [🆕 Fulfilment API](/api-document/product-guides/booking/booking-flows/fulfillment-flow.md)
* [Get Offer Price](/api-document/product-guides/booking/booking-step-guides/get-offer-price.md)
* [Fulfilment API FAQ](/api-document/support-and-reference/troubleshooting-and-support/faqs/fulfilment-api-faq.md)
* [Payment & Ticketing](/api-document/product-guides/booking/booking-step-guides/payment-and-ticketing.md)
* [API Request Limits](/api-document/product-guides/booking/booking-overview/api-request-limits.md)

#### Payment timeout, transient failure, and duplicate-booking clarification pack

Published three new pages for payment deadline recovery, transient booking-stage failures, and duplicate-booking handling.

What changed:

* added [401 vs 402 vs 404](/api-document/support-and-reference/troubleshooting-and-support/errors-handing/401-vs-402-vs-404.md) to distinguish expired payment windows from non-payable or already-paid order states
* added [205 vs 299 vs 304](/api-document/support-and-reference/troubleshooting-and-support/errors-handing/205-vs-299-vs-304.md) to clarify when to retry once, restart from search, or escalate transient verify and order failures
* added [318 vs 608 duplicate booking](/api-document/support-and-reference/troubleshooting-and-support/errors-handing/318-vs-608-duplicate-booking.md) to clarify how to confirm existing booking state before retrying

Read next:

* [Payment Errors](/api-document/support-and-reference/troubleshooting-and-support/errors-handing/payment-errors.md)
* [Verify, Order & Ticketing Errors](/api-document/support-and-reference/troubleshooting-and-support/errors-handing/verify-order-and-ticketing-errors.md)
* [Error Codes](/api-document/support-and-reference/troubleshooting-and-support/errors-handing.md)

#### Input validation and seat fallback clarification pack

Published three new pages for order input troubleshooting, ancillary mapping, and seat failure behavior.

What changed:

* added [307 vs 327 vs 410](/api-document/support-and-reference/troubleshooting-and-support/errors-handing/307-vs-327-vs-410.md) to distinguish generic order-field issues, booking-requirement mismatches, and contact phone formatting errors
* added [309 vs 409](/api-document/support-and-reference/troubleshooting-and-support/errors-handing/309-vs-409.md) to distinguish stale ancillary codes from baggage segment-mapping errors
* added [Seat fallback modes](/api-document/product-guides/booking/optional-ancillaries/seats-and-baggage/seat-fallback-modes.md) to explain `STOP_TICKET`, `STOP_SEAT`, and `SIMILAR_SEAT`

Read next:

* [Create Order](/api-document/product-guides/booking/booking-step-guides/create-order.md)
* [Seats](/api-document/product-guides/booking/optional-ancillaries/seats-and-baggage.md)
* [Error Codes](/api-document/support-and-reference/troubleshooting-and-support/errors-handing.md)

#### Payment-state and ancillary freshness clarification pack

Published three new pages for payment recovery, ancillary reuse safety, and flow restart decisions.

What changed:

* added [402 vs 404 vs 406 vs 615](/api-document/support-and-reference/troubleshooting-and-support/errors-handing/402-vs-404-vs-406-vs-615.md) to clarify when to query order, wait, or avoid another `pay.do`
* added [Baggage and seat productCode freshness](/api-document/product-guides/booking/optional-ancillaries/baggage-and-seat-productcode-freshness.md) to explain when ancillary selections are stale
* added [Restart from Search vs Verify vs Get Offer](/api-document/product-guides/booking/booking-overview/booking-decisions/restart-point.md) to explain the earliest booking step that must be rerun

Read next:

* [Payment & Ticketing](/api-document/product-guides/booking/booking-step-guides/payment-and-ticketing.md)
* [Booking Overview](/api-document/product-guides/booking/booking-overview.md)
* [Error Codes](/api-document/support-and-reference/troubleshooting-and-support/errors-handing.md)

#### Booking recovery and timing clarification pack

Published three new pages for booking-stage recovery decisions and post-payment follow-up.

What changed:

* added [202 vs 301 vs 308](/api-document/support-and-reference/troubleshooting-and-support/errors-handing/202-vs-301-vs-308.md) to explain when to refresh search, refresh verify, or rebuild the booking context
* added [Verify vs Order](/api-document/product-guides/booking/booking-overview/booking-decisions/verify-vs-order.md) to clarify the validation boundary before booking creation
* added [Post-payment polling](/api-document/product-guides/booking/booking-step-guides/query-order/post-payment-polling.md) to explain why payment success does not always mean final ticketing

Read next:

* [Booking Overview](/api-document/product-guides/booking/booking-overview.md)
* [Payment & Ticketing](/api-document/product-guides/booking/booking-step-guides/payment-and-ticketing.md)
* [Error Codes](/api-document/support-and-reference/troubleshooting-and-support/errors-handing.md)

#### Booking flow clarification pack

Published three new pages for common integration questions around flow choice, identifier handling, and request-pressure troubleshooting.

What changed:

* added [Identifiers](/api-document/product-guides/booking/booking-overview/identifiers.md) for `routingIdentifier`, `sessionId`, `OfferId`, `orderNo`, and fresh-identifier rules
* added [Search vs Get Offer](/api-document/product-guides/booking/booking-overview/booking-decisions/search-vs-offer.md) to clarify when to use `search.do` versus `getOffers.do`
* added [429 vs 110](/api-document/support-and-reference/troubleshooting-and-support/errors-handing/429-vs-110.md) to distinguish request-limit governance from search concurrency pressure

Read next:

* [Booking Overview](/api-document/product-guides/booking/booking-overview.md)
* [Search & Booking](/api-document/support-and-reference/troubleshooting-and-support/faqs/atlas-api-search-and-book.md)
* [Error Codes](/api-document/support-and-reference/troubleshooting-and-support/errors-handing.md)

#### QPS and QPM request limit governance

Published new request-limit guidance for selected pre-booking APIs.

What changed:

* documented Atlas error code `429` behavior for over-limit requests
* added shared-pool rules for `verify.do` and `getOffers.do`, and for `seatAvailability.do` and `getLuggage.do`
* added retry guidance for `retryAfter`, request pacing, and duplicate-search reduction

Read next:

* [Booking Overview](/api-document/product-guides/booking/booking-overview.md)
* [Error Codes](/api-document/support-and-reference/troubleshooting-and-support/errors-handing.md)
* [Search & Booking](/api-document/support-and-reference/troubleshooting-and-support/faqs/atlas-api-search-and-book.md)

#### Multi-channel notifications launch

Published the new Atlas notification setup guidance for ATRIP delivery across webhook, email, DingTalk, WeCom, Slack, and Teams.

What changed:

* added a new setup guide for multi-channel notifications in ATRIP
* clarified that webhook is one delivery option in the notification model
* linked airline status updates to the first live multi-channel scenario

Read next:

* [Multi-channel Notifications](/api-document/product-guides/extensions-and-integrations/multi-channel-notifications.md)
* [Webhook Overview](/api-document/product-guides/extensions-and-integrations/webhook-overview.md)
* [Airline Status Update Notification](/api-document/product-guides/extensions-and-integrations/webhook-overview/airline-status-update-notification.md)

#### Standard headers cleanup

Updated the sandbox access guidance to remove an unnecessary standard request header.

What changed:

* removed `Accept: application/json` from the standard headers list
* kept `Accept-Encoding`, `Authorization`, and `Content-Type` guidance unchanged

Read next:

* [Sandbox Access](/api-document/readme-1/making-requests.md)
* [Quick Start](/api-document/readme-1/quick-start.md)

#### UAT Testing flow update

Updated the UAT documentation to reflect the current ATRIP validation flow.

What changed:

* UAT now starts in **UAT Testing**
* partners must choose the target function scope before continuing
* **flight booking** is the required core function
* **Submit Verification** now triggers automatic validation and returns failure reasons directly

Read next:

* [UAT Validation](/api-document/readme-1/uat-submission-guide.md)
* [Quick Start](/api-document/readme-1/quick-start.md)
* [Getting Started](/api-document/support-and-reference/troubleshooting-and-support/faqs/atlas-api-general-information.md)

#### Void workflow and notification updates

Updated the void documentation to reflect the current post-booking flow and webhook handling.

What changed:

* clarified the standard flow: `voidQuotation.do` → `void.do` → `queryVoidOrders.do`
* added stronger guidance for `voidOfferId`, `voidCode`, and void-window checks
* expanded `order.void` webhook coverage, status values, and retry-failure behavior

Read next:

* [Void workflow](/api-document/product-guides/post-booking/void.md)
* [Void](/api-document/api-reference/post-booking-apis/void.md)
* [Void Notification](/api-document/product-guides/extensions-and-integrations/webhook-overview/void-notification.md)

#### SeatAvailability call rules update

Updated the seat-selection guidance to reflect the current `seatAvailability.do` calling rules.

What changed:

* independent mode is no longer available
* `seatAvailability.do` now requires `sessionId` from `verify.do` or `OfferId` from `getOffers.do`
* flight-only seat quote requests are not supported

Read next:

* [Seat](/api-document/api-reference/booking-apis/inflow-seat-and-baggage.md)
* [Seats](/api-document/product-guides/booking/optional-ancillaries/seats-and-baggage.md)
* [Verify](/api-document/product-guides/booking/booking-step-guides/verify.md)

#### MCP-Assisted Development

Read [MCP-Assisted Development](/api-document/readme-1/integration-tools/mcp-assisted-development.md) when you want to use GitBook MCP during Atlas API integration.

Best for:

* teams starting a sandbox build
* developers mapping the booking flow
* teams routing implementation questions faster

Read next:

* [Quick Start](/api-document/readme-1/quick-start.md)
* [API Reference](/api-document/api-reference.md)

#### Sandbox Validation Test Kit

Read [Sandbox Validation Test Kit](/api-document/readme-1/sandbox-development/sandbox-validation-test-kit.md) when you need a no-code sandbox validation run before development or after environment changes.

Best for:

* validate sandbox credentials before coding
* confirm network access and core booking flow readiness
* teams rechecking sandbox health after credential or IP changes

Read next:

* [Sandbox Development](/api-document/readme-1/sandbox-development.md)
* [UAT Validation](/api-document/readme-1/uat-submission-guide.md)

#### Error Codes improvements

[Error Codes](/api-document/support-and-reference/troubleshooting-and-support/errors-handing.md) now works better as the main troubleshooting entry point.

Best for:

* teams handling high-frequency integration failures
* developers defining safe retry behavior
* operations teams checking likely root causes

Read next:

* [Common & Access Errors](/api-document/support-and-reference/troubleshooting-and-support/errors-handing/common-and-access-errors.md)
* [Verify, Order & Ticketing Errors](/api-document/support-and-reference/troubleshooting-and-support/errors-handing/verify-order-and-ticketing-errors.md)

### Start here by use case

#### New Atlas API integration

Start with:

* [Quick Start](/api-document/readme-1/quick-start.md)
* [MCP-Assisted Development](/api-document/readme-1/integration-tools/mcp-assisted-development.md)
* [Booking Overview](/api-document/product-guides/booking/booking-overview.md)

#### Sandbox validation

Start with:

* [Sandbox Access](/api-document/readme-1/making-requests.md)
* [Sandbox Validation Test Kit](/api-document/readme-1/sandbox-development/sandbox-validation-test-kit.md)
* [Sandbox Development](/api-document/readme-1/sandbox-development.md)

#### Booking and payment flow

Start with:

* [Booking Overview](/api-document/product-guides/booking/booking-overview.md)
* [Payment & Ticketing](/api-document/product-guides/booking/booking-step-guides/payment-and-ticketing.md)
* [Hybrid Payment Guide](/api-document/product-guides/booking/booking-step-guides/payment-and-ticketing/hybrid-payment-guide.md)

#### Troubleshooting and support

Start with:

* [Error Codes](/api-document/support-and-reference/troubleshooting-and-support/errors-handing.md)
* [FAQs](/api-document/support-and-reference/troubleshooting-and-support/faqs.md)
* [Webhook Overview](/api-document/product-guides/extensions-and-integrations/webhook-overview.md)

### FAQ

#### What changed in the Atlas API docs recently?

Recent updates added [Identifiers](/api-document/product-guides/booking/booking-overview/identifiers.md), [Search vs Get Offer](/api-document/product-guides/booking/booking-overview/booking-decisions/search-vs-offer.md), [429 vs 110](/api-document/support-and-reference/troubleshooting-and-support/errors-handing/429-vs-110.md), [202 vs 301 vs 308](/api-document/support-and-reference/troubleshooting-and-support/errors-handing/202-vs-301-vs-308.md), [Verify vs Order](/api-document/product-guides/booking/booking-overview/booking-decisions/verify-vs-order.md), [Post-payment polling](/api-document/product-guides/booking/booking-step-guides/query-order/post-payment-polling.md), [402 vs 404 vs 406 vs 615](/api-document/support-and-reference/troubleshooting-and-support/errors-handing/402-vs-404-vs-406-vs-615.md), [Baggage and seat productCode freshness](/api-document/product-guides/booking/optional-ancillaries/baggage-and-seat-productcode-freshness.md), [Restart from Search vs Verify vs Get Offer](/api-document/product-guides/booking/booking-overview/booking-decisions/restart-point.md), [307 vs 327 vs 410](/api-document/support-and-reference/troubleshooting-and-support/errors-handing/307-vs-327-vs-410.md), [309 vs 409](/api-document/support-and-reference/troubleshooting-and-support/errors-handing/309-vs-409.md), [Seat fallback modes](/api-document/product-guides/booking/optional-ancillaries/seats-and-baggage/seat-fallback-modes.md), [401 vs 402 vs 404](/api-document/support-and-reference/troubleshooting-and-support/errors-handing/401-vs-402-vs-404.md), [205 vs 299 vs 304](/api-document/support-and-reference/troubleshooting-and-support/errors-handing/205-vs-299-vs-304.md), and [318 vs 608 duplicate booking](/api-document/support-and-reference/troubleshooting-and-support/errors-handing/318-vs-608-duplicate-booking.md), added QPS and QPM request-limit guidance for selected pre-booking APIs, added [Multi-channel Notifications](/api-document/product-guides/extensions-and-integrations/multi-channel-notifications.md) for ATRIP notification setup, added the new ATRIP **UAT Testing** flow to [UAT Validation](/api-document/readme-1/uat-submission-guide.md), clarified that **flight booking** is required, added automatic verification guidance, expanded the [Void workflow](/api-document/product-guides/post-booking/void.md), changed `seatAvailability.do` call rules, added [MCP-Assisted Development](/api-document/readme-1/integration-tools/mcp-assisted-development.md), published [Sandbox Validation Test Kit](/api-document/readme-1/sandbox-development/sandbox-validation-test-kit.md), and improved [Error Codes](/api-document/support-and-reference/troubleshooting-and-support/errors-handing.md) as a troubleshooting entry point.

#### Which guide should I read first for sandbox integration?

Start with [Quick Start](/api-document/readme-1/quick-start.md). Then use [Sandbox Validation Test Kit](/api-document/readme-1/sandbox-development/sandbox-validation-test-kit.md) to confirm readiness before coding.

#### Where should I start for booking, payment, or troubleshooting?

Use [Booking Overview](/api-document/product-guides/booking/booking-overview.md) for the main flow, [Payment & Ticketing](/api-document/product-guides/booking/booking-step-guides/payment-and-ticketing.md) for payment and polling, and [Error Codes](/api-document/support-and-reference/troubleshooting-and-support/errors-handing.md) for failure handling.

### Full change log

{% updates format="full" %}
{% update date="2026-07-12" %}

## Improved Atlas API documentation discovery

Improved documentation entry points for product discovery, common questions, and integration terminology.

What changed:

* added [What is Atlas API?](/api-document/what-is-atlas-api.md) as the canonical product overview
* added [Atlas API concepts](/api-document/support-and-reference/atlas-api-concepts.md) for booking flows, identifiers, order lifecycle, and webhooks
* added direct-answer FAQ sections to [Product Guides](/api-document/product-guides.md) and [Support & Reference](/api-document/support-and-reference.md)
* improved descriptions for key integration, booking-decision, and operational pages

Read next:

* [What is Atlas API?](/api-document/what-is-atlas-api.md)
* [Quick Start](/api-document/readme-1/quick-start.md)
* [Atlas API concepts](/api-document/support-and-reference/atlas-api-concepts.md)
  {% endupdate %}

{% update date="2026-07-10" %}

## Added Fulfilment API FAQ for product-fit questions

Published a dedicated FAQ for Fulfilment API and linked it from the main Fulfilment decision and guidance pages.

What changed:

* added [Fulfilment API FAQ](/api-document/support-and-reference/troubleshooting-and-support/faqs/fulfilment-api-faq.md) under Atlas API FAQs
* updated [Atlas API FAQs](/api-document/support-and-reference/troubleshooting-and-support/faqs.md) to surface the new page in booking and ticketing questions
* updated [Get Offer vs Fulfilment API](/api-document/product-guides/booking/booking-overview/booking-decisions/get-offer-vs-get-offer-price.md) with business-fit guidance
* updated [Get Offer Price](/api-document/product-guides/booking/booking-step-guides/get-offer-price.md) to link the new FAQ from the step guide
* updated [Booking Overview](/api-document/product-guides/booking/booking-overview.md) and [Orders & Ticketing](/api-document/support-and-reference/troubleshooting-and-support/faqs/atlas-api-order.md) to align Fulfilment API fit, timing, and payment-path entry guidance
  {% endupdate %}

{% update date="2026-07-10" %}

## Increased Fulfilment API visibility across key entry pages

Updated the highest-traffic navigation pages to make the new Fulfilment API path easier to find.

What changed:

* added a featured Fulfilment API callout to [Quick Start](/api-document/readme-1/quick-start.md)
* added a new-product callout to [Product Guides](/api-document/product-guides.md)
* moved [Fulfilment API](/api-document/product-guides/booking/booking-flows/fulfillment-flow.md) to the top of [Booking paths](/api-document/product-guides/booking/booking-flows.md)
* added a featured product section to [Atlas API Documentation Updates](/api-document/readme.md)
  {% endupdate %}

{% update date="2026-07-08" %}

## Expanded VOID airline coverage

Updated the VOID documentation to reflect the current supported airline scope.

What changed:

* documented 23 supported VOID airlines across four regions
* added `TS`, `Y4`, `EI`, and `VF` to the supported coverage list
* clarified that `ZG` support is limited to US routes

Updated pages:

* [Void workflow](/api-document/product-guides/post-booking/void.md)
* [Void](/api-document/api-reference/post-booking-apis/void.md)
* [Atlas API Documentation Updates](/api-document/readme.md)
  {% endupdate %}

{% update date="2026-07-06" %}

## Added Fulfilment API and `getOfferPrice.do`

Published the new Fulfilment API booking path for `getOfferPrice.do` and updated key workflow pages with fulfilment-specific timing and request-limit guidance.

What changed:

* added [Get Offer Price](/api-document/product-guides/booking/booking-step-guides/get-offer-price.md) for entry-step positioning, 5-minute timing, retry rules, and recovery guidance
* added [Get Offer vs Fulfilment API](/api-document/product-guides/booking/booking-overview/booking-decisions/get-offer-vs-get-offer-price.md) to distinguish standard Get Offer from the Fulfilment API path
* added [Get Offer Price](/api-document/api-reference/booking-apis/get-offer-price.md) under API Reference
* updated [Booking Overview](/api-document/product-guides/booking/booking-overview.md) to add the new Fulfilment API branch
* updated [Get Offer](/api-document/product-guides/booking/booking-step-guides/get-offer.md) to distinguish `getOffers.do` from `getOfferPrice.do`
* updated [Create Order](/api-document/product-guides/booking/booking-step-guides/create-order.md), [Payment & Ticketing](/api-document/product-guides/booking/booking-step-guides/payment-and-ticketing.md), and [Query Order](/api-document/product-guides/booking/booking-step-guides/query-order.md) for 5-minute Fulfilment API handling
* updated [Orders & Ticketing](/api-document/support-and-reference/troubleshooting-and-support/faqs/atlas-api-order.md) to separate the standard 30-minute hold from the Fulfilment API path
* updated [API Request Limits](/api-document/product-guides/booking/booking-overview/api-request-limits.md) to document the separate `getOfferPrice.do` QPM policy
  {% endupdate %}

{% update date="2026-07-05" %}

## Added identifier, flow-choice, and throttling guidance

Published fifteen new support pages for common booking-flow integration questions.

What changed:

* added [Identifiers](/api-document/product-guides/booking/booking-overview/identifiers.md) for `routingIdentifier`, `sessionId`, `OfferId`, `orderNo`, and refresh rules
* added [Search vs Get Offer](/api-document/product-guides/booking/booking-overview/booking-decisions/search-vs-offer.md) to clarify when to use `search.do` and when to use `getOffers.do`
* added [429 vs 110](/api-document/support-and-reference/troubleshooting-and-support/errors-handing/429-vs-110.md) to explain request-limit governance versus search concurrency pressure
* added [202 vs 301 vs 308](/api-document/support-and-reference/troubleshooting-and-support/errors-handing/202-vs-301-vs-308.md) to explain which earlier step must be refreshed
* added [Verify vs Create Order](/api-document/product-guides/booking/booking-overview/booking-decisions/verify-vs-order.md) to clarify the validation boundary before order creation
* added [Polling and Ticketing Timing](/api-document/product-guides/booking/booking-step-guides/query-order/post-payment-polling.md) to explain post-payment follow-up and safe polling behavior
* added [402 vs 404 vs 406 vs 615](/api-document/support-and-reference/troubleshooting-and-support/errors-handing/402-vs-404-vs-406-vs-615.md) to clarify payment-state recovery and duplicate-payment risk
* added [Baggage and seat productCode freshness](/api-document/product-guides/booking/optional-ancillaries/baggage-and-seat-productcode-freshness.md) to explain when ancillary selections are stale
* added [Restart from Search vs Verify vs Get Offer](/api-document/product-guides/booking/booking-overview/booking-decisions/restart-point.md) to explain which booking step must be rerun after stale context or price drift
* added [307 vs 327 vs 410](/api-document/support-and-reference/troubleshooting-and-support/errors-handing/307-vs-327-vs-410.md) to clarify passenger, document, and contact input errors at order creation
* added [309 vs 409](/api-document/support-and-reference/troubleshooting-and-support/errors-handing/309-vs-409.md) to clarify stale ancillary codes versus baggage segment-mapping errors
* added [Seat fallback modes](/api-document/product-guides/booking/optional-ancillaries/seats-and-baggage/seat-fallback-modes.md) to explain `STOP_TICKET`, `STOP_SEAT`, and `SIMILAR_SEAT`
* added [401 vs 402 vs 404](/api-document/support-and-reference/troubleshooting-and-support/errors-handing/401-vs-402-vs-404.md) to clarify payment deadline expiration versus non-payable or already-paid orders
* added [205 vs 299 vs 304](/api-document/support-and-reference/troubleshooting-and-support/errors-handing/205-vs-299-vs-304.md) to clarify transient verify and order failures
* added [318 vs 608 duplicate booking](/api-document/support-and-reference/troubleshooting-and-support/errors-handing/318-vs-608-duplicate-booking.md) to clarify duplicate-booking handling before another retry

Updated pages:

* [Atlas API Documentation Updates](/api-document/readme.md)
* [Booking Overview](/api-document/product-guides/booking/booking-overview.md)
* [Error Codes](/api-document/support-and-reference/troubleshooting-and-support/errors-handing.md)
* [Payment & Ticketing](/api-document/product-guides/booking/booking-step-guides/payment-and-ticketing.md)
  {% endupdate %}

{% update date="2026-07-03" %}

## Added QPS and QPM request-limit guidance

Updated booking, troubleshooting, and FAQ pages to document request-limit governance for selected pre-booking APIs.

What changed:

* added Atlas error code `429` guidance with `retryAfter`
* documented default limits for Search, Fulfilment, and Ancillary resource pools
* clarified that `verify.do` and `getOffers.do` share one fulfilment pool
* clarified that `seatAvailability.do` and `getLuggage.do` share one ancillary pool
* confirmed that `order.do` and `pay.do` are not part of this request-limit policy

Updated pages:

* [Booking Overview](/api-document/product-guides/booking/booking-overview.md)
* [Search](/api-document/product-guides/booking/booking-step-guides/search.md)
* [Get Offer](/api-document/product-guides/booking/booking-step-guides/get-offer.md)
* [Verify](/api-document/product-guides/booking/booking-step-guides/verify.md)
* [Seats](/api-document/product-guides/booking/optional-ancillaries/seats-and-baggage.md)
* [Baggage](/api-document/product-guides/booking/optional-ancillaries/baggage.md)
* [Error Codes](/api-document/support-and-reference/troubleshooting-and-support/errors-handing.md)
* [Search Errors](/api-document/support-and-reference/troubleshooting-and-support/errors-handing/search-errors.md)
* [Verify, Order & Ticketing Errors](/api-document/support-and-reference/troubleshooting-and-support/errors-handing/verify-order-and-ticketing-errors.md)
* [Search & Booking](/api-document/support-and-reference/troubleshooting-and-support/faqs/atlas-api-search-and-book.md)
  {% endupdate %}

{% update date="2026-06-30" %}

## Added multi-channel notification setup guidance

Published [Multi-channel Notifications](/api-document/product-guides/extensions-and-integrations/multi-channel-notifications.md) for ATRIP delivery across webhook, email, DingTalk, WeCom, Slack, and Teams.

What changed:

* added a new guide for channel selection, ATRIP setup, and test notifications
* clarified in [Webhook Overview](/api-document/product-guides/extensions-and-integrations/webhook-overview.md) that webhook is one delivery option in the broader notification model
* updated [Airline Status Update Notification](/api-document/product-guides/extensions-and-integrations/webhook-overview/airline-status-update-notification.md) to position airline status as the first live multi-channel scenario

Updated pages:

* [Multi-channel Notifications](/api-document/product-guides/extensions-and-integrations/multi-channel-notifications.md)
* [Webhook Overview](/api-document/product-guides/extensions-and-integrations/webhook-overview.md)
* [Airline Status Update Notification](/api-document/product-guides/extensions-and-integrations/webhook-overview/airline-status-update-notification.md)
  {% endupdate %}

{% update date="2026-06-29" %}

## Removed `Accept: application/json` from standard headers

Updated the sandbox access guidance to keep the standard request headers aligned with current usage.

What changed:

* removed `Accept: application/json` from the standard headers list
* kept the remaining standard header guidance unchanged

Updated pages:

* [Sandbox Access](/api-document/readme-1/making-requests.md)
  {% endupdate %}

{% update date="2026-06-29" %}

## Updated UAT Validation for ATRIP UAT Testing

Updated the UAT guidance to reflect the latest ATRIP flow.

What changed:

* UAT now starts from **UAT Testing**
* partners choose the target function scope before continuing
* **flight booking** is now documented as the required core function
* **Confirm and Continue** and **Submit Verification** are now part of the documented flow
* failed cases now point users to the ATRIP failure reason directly

Updated pages:

* [UAT Validation](/api-document/readme-1/uat-submission-guide.md)
* [Quick Start](/api-document/readme-1/quick-start.md)
* [Getting Started](/api-document/support-and-reference/troubleshooting-and-support/faqs/atlas-api-general-information.md)
  {% endupdate %}

{% update date="2026-06-10" %}

## Expanded Void workflow and webhook guidance

Updated the void documentation to reflect the current post-booking flow.

What changed:

* clarified the standard `voidQuotation.do` → `void.do` → `queryVoidOrders.do` sequence
* added guidance for `voidOfferId`, `voidCode`, and strict void-window handling
* expanded `order.void` webhook trigger rules, status values, and retry-failure behavior

Updated pages:

* [Void workflow](/api-document/product-guides/post-booking/void.md)
* [Void](/api-document/api-reference/post-booking-apis/void.md)
* [Void Notification](/api-document/product-guides/extensions-and-integrations/webhook-overview/void-notification.md)
  {% endupdate %}

{% update date="2026-06-09" %}

## Updated SeatAvailability call rules

Updated seat-selection documentation to reflect the latest `seatAvailability.do` requirements.

What changed:

* independent mode is no longer available
* use `sessionId` from `verify.do` or `OfferId` from `getOffers.do`
* flight-only seat quote requests are not supported

Updated pages:

* [Inflow Seat & Baggage](/api-document/api-reference/booking-apis/inflow-seat-and-baggage.md)
* [Seats & Baggage](/api-document/product-guides/booking/optional-ancillaries/seats-and-baggage.md)
* [Verify](/api-document/product-guides/booking/booking-step-guides/verify.md)
* [Get Offer](/api-document/product-guides/booking/booking-step-guides/get-offer.md)
* [Booking Overview](/api-document/product-guides/booking/booking-overview.md)
* [Search & Booking](/api-document/support-and-reference/troubleshooting-and-support/faqs/atlas-api-search-and-book.md)
  {% endupdate %}

{% update date="2026-04-15" %}

## Added MCP-Assisted Development

Published [MCP-Assisted Development](/api-document/readme-1/integration-tools/mcp-assisted-development.md) for teams using GitBook MCP during Atlas API integration.

Use it when you need to:

* find the correct workflow before coding
* understand which identifier or API comes next
* jump from development questions to the right reference or troubleshooting page

The guide also includes prompt patterns and usage boundaries for production-safe development.
{% endupdate %}

{% update date="2026-04-09" %}

## Added Sandbox Validation Test Kit

Published [Sandbox Validation Test Kit](/api-document/readme-1/sandbox-development/sandbox-validation-test-kit.md) for a no-code sandbox validation run.

Use it when you need to:

* confirm credentials and network access before development
* run the core sandbox happy path with Newman
* verify `Search`, `Verify`, `Order`, and `Pay` in one pass
* quickly check sandbox readiness after environment changes

The page also explains the expected final retrieve timeout during ticketing polling.
{% endupdate %}

{% update date="2026-04-08" %}

## Improved Error Codes landing page

Updated [Error Codes](/api-document/support-and-reference/troubleshooting-and-support/errors-handing.md) with:

* retry policy guidance
* a quick decision table for high-frequency codes
* high-risk mistakes to avoid during retry
* pattern-based checks for common integration issues

This makes the page more useful as the main troubleshooting entry point.
{% endupdate %}

{% update date="2026-04-03" %}

## Added Hybrid Payment Guide

Published [Hybrid Payment Guide](/api-document/product-guides/booking/booking-step-guides/payment-and-ticketing/hybrid-payment-guide.md) under **Payment & Ticketing**.

Use it when you need to:

* switch from VCC pass-through to deposit
* decide whether to reuse or regenerate an order
* handle hybrid payment fallback in ATRIP and API flows
  {% endupdate %}
  {% endupdates %}