> 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/atlas-api-documentation-updates.md).
# Atlas API Documentation Updates
{% hint style="info" %}
💬 **Need help?** If you're stuck, ask Eva on ATRIP for instant diagnostics.
Ask Eva
{% endhint %}
Use this page to track the latest Atlas API documentation updates.
{% hint style="success" %}
Latest update: Void workflow, API reference, and webhook guidance are now expanded.
{% 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
### Latest Atlas API documentation updates
#### 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/readme/post-booking-overview/post-booking-operations/void.md)
* [Void](/api-document/api-reference/post-booking-apis/void.md)
* [Void Notification](/api-document/readme/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:
* [Inflow Seat & Baggage](/api-document/api-reference/booking-apis/inflow-seat-and-baggage.md)
* [Seats & Baggage](/api-document/readme/booking-overview/seats-and-baggage.md)
* [Verify](/api-document/readme/booking-overview/verify.md)
#### MCP-Assisted Development
Read [MCP-Assisted Development](/api-document/readme/quick-start/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/quick-start.md)
* [API Reference](/api-document/api-reference.md)
#### Sandbox Validation Test Kit
Read [Sandbox Validation Test Kit](/api-document/readme/quick-start/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/quick-start/sandbox-development.md)
* [UAT Validation](/api-document/readme/quick-start/uat-submission-guide.md)
#### Error Codes improvements
[Error Codes](/api-document/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/troubleshooting-and-support/errors-handing/common-and-access-errors.md)
* [Verify, Order & Ticketing Errors](/api-document/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/quick-start.md)
* [MCP-Assisted Development](/api-document/readme/quick-start/mcp-assisted-development.md)
* [Booking Overview](/api-document/readme/booking-overview.md)
#### Sandbox validation
Start with:
* [Sandbox Access](/api-document/readme/quick-start/making-requests.md)
* [Sandbox Validation Test Kit](/api-document/readme/quick-start/sandbox-development/sandbox-validation-test-kit.md)
* [Sandbox Development](/api-document/readme/quick-start/sandbox-development.md)
#### Booking and payment flow
Start with:
* [Booking Overview](/api-document/readme/booking-overview.md)
* [Payment & Ticketing](/api-document/readme/booking-overview/payment-and-ticketing.md)
* [Hybrid Payment Guide](/api-document/readme/booking-overview/payment-and-ticketing/hybrid-payment-guide.md)
#### Troubleshooting and support
Start with:
* [Error Codes](/api-document/troubleshooting-and-support/errors-handing.md)
* [FAQs](/api-document/troubleshooting-and-support/faqs.md)
* [Webhook Overview](/api-document/readme/webhook-overview.md)
### FAQ
#### What changed in the Atlas API docs recently?
Recent updates expanded the [Void workflow](/api-document/readme/post-booking-overview/post-booking-operations/void.md), [Void](/api-document/api-reference/post-booking-apis/void.md), and [Void Notification](/api-document/readme/webhook-overview/void-notification.md) pages, changed `seatAvailability.do` call rules, added [MCP-Assisted Development](/api-document/readme/quick-start/mcp-assisted-development.md), published [Sandbox Validation Test Kit](/api-document/readme/quick-start/sandbox-development/sandbox-validation-test-kit.md), and improved [Error Codes](/api-document/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/quick-start.md). Then use [Sandbox Validation Test Kit](/api-document/readme/quick-start/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/readme/booking-overview.md) for the main flow, [Payment & Ticketing](/api-document/readme/booking-overview/payment-and-ticketing.md) for payment and polling, and [Error Codes](/api-document/troubleshooting-and-support/errors-handing.md) for failure handling.
### Full change log
{% updates format="full" %}
{% 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/readme/post-booking-overview/post-booking-operations/void.md)
* [Void](/api-document/api-reference/post-booking-apis/void.md)
* [Void Notification](/api-document/readme/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/readme/booking-overview/seats-and-baggage.md)
* [Verify](/api-document/readme/booking-overview/verify.md)
* [Get Offer](/api-document/readme/booking-overview/get-offer.md)
* [Booking Overview](/api-document/readme/booking-overview.md)
* [Search & Booking](/api-document/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/quick-start/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/quick-start/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/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/readme/booking-overview/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 %}
---
# 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/atlas-api-documentation-updates.md?ask=&goal=
```
`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.