📣Atlas API Documentation Updates

Latest Atlas API documentation updates, new integration guides, and recommended next reads.

💬 Need help? If you're stuck, ask Eva on ATRIP for instant diagnostics.

Ask Eva

Use this page to track the latest Atlas API documentation updates.

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.dovoid.doqueryVoidOrders.do

  • added stronger guidance for voidOfferId, voidCode, and void-window checks

  • expanded order.void webhook coverage, status values, and retry-failure behavior

Read next:

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:

MCP-Assisted Development

Read MCP-Assisted Development 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:

Sandbox Validation Test Kit

Read Sandbox Validation Test Kit 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:

Error Codes improvements

Error Codes 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:

Start here by use case

New Atlas API integration

Start with:

Sandbox validation

Start with:

Booking and payment flow

Start with:

Troubleshooting and support

Start with:

FAQ

What changed in the Atlas API docs recently?

Recent updates expanded the Void workflow, Void, and Void Notification pages, changed seatAvailability.do call rules, added MCP-Assisted Development, published Sandbox Validation Test Kit, and improved Error Codes as a troubleshooting entry point.

Which guide should I read first for sandbox integration?

Start with Quick Start. Then use Sandbox Validation Test Kit to confirm readiness before coding.

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

Use Booking Overview for the main flow, Payment & Ticketing for payment and polling, and Error Codes for failure handling.

Full change log

Expanded Void workflow and webhook guidance

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

What changed:

  • clarified the standard voidQuotation.dovoid.doqueryVoidOrders.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:

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:

Added MCP-Assisted Development

Published MCP-Assisted Development 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.

Added Sandbox Validation Test Kit

Published Sandbox Validation Test Kit 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.

Improved Error Codes landing page

Updated Error Codes 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.

Added Hybrid Payment Guide

Published Hybrid Payment Guide 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

Last updated

Was this helpful?