Ctrlk
💬 Need Help? Click Me
For the complete documentation index, see llms.txt. This page is also available as Markdown.
RSS feed

📣Atlas API Documentation Updates

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

💬 Need help? If you're stuck, ask Eva in the Help Center for instant diagnostics.

Ask Eva

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.

🆕 Featured new product: 🆕 Fulfilment API is now available for partners using getOfferPrice.do and immediate payment after order creation.

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 when you need the new getOfferPrice.do booking path.

Then use:

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.

Then use Integration Guides, Booking Overview, and Error Codes.

Which pages should I check for request-limit guidance?

Start with Booking Overview, Search, Search & Booking, and Error Codes.

Popular starting points

New integration

Start with Quick Start and Integration Guides.

Booking flow

Start with 🆕 Fulfilment API, Booking Overview, and Search & Booking.

Use Identifiers when you need the right token for the next step.

Use Verify vs Order when the booking boundary is the main question.

Use Restart from Search vs Verify vs Get Offer when the main question is where to restart.

Use Seat fallback modes when paid seat failure behavior must be defined before booking.

Troubleshooting

Start with Error Codes and FAQs.

Use 429 vs 110 when request frequency or search concurrency is the main issue.

Use 202 vs 301 vs 308 when you need to know which earlier step must be refreshed.

Use 402 vs 404 vs 406 vs 615 when the main risk is duplicate or unnecessary payment retry.

Use 307 vs 327 vs 410 and 309 vs 409 when order input or ancillary mapping is the main failure area.

Use 401 vs 402 vs 404 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:

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:

Read next:

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 to distinguish expired payment windows from non-payable or already-paid order states

  • added 205 vs 299 vs 304 to clarify when to retry once, restart from search, or escalate transient verify and order failures

  • added 318 vs 608 duplicate booking to clarify how to confirm existing booking state before retrying

Read next:

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 to distinguish generic order-field issues, booking-requirement mismatches, and contact phone formatting errors

  • added 309 vs 409 to distinguish stale ancillary codes from baggage segment-mapping errors

  • added Seat fallback modes to explain STOP_TICKET, STOP_SEAT, and SIMILAR_SEAT

Read next:

Payment-state and ancillary freshness clarification pack

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

What changed:

Read next:

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 to explain when to refresh search, refresh verify, or rebuild the booking context

  • added Verify vs Order to clarify the validation boundary before booking creation

  • added Post-payment polling to explain why payment success does not always mean final ticketing

Read next:

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 for routingIdentifier, sessionId, OfferId, orderNo, and fresh-identifier rules

  • added Search vs Get Offer to clarify when to use search.do versus getOffers.do

  • added 429 vs 110 to distinguish request-limit governance from search concurrency pressure

Read next:

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:

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:

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:

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:

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:

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 added Identifiers, Search vs Get Offer, 429 vs 110, 202 vs 301 vs 308, Verify vs Order, Post-payment polling, 402 vs 404 vs 406 vs 615, Baggage and seat productCode freshness, Restart from Search vs Verify vs Get Offer, 307 vs 327 vs 410, 309 vs 409, Seat fallback modes, 401 vs 402 vs 404, 205 vs 299 vs 304, and 318 vs 608 duplicate booking, added QPS and QPM request-limit guidance for selected pre-booking APIs, added Multi-channel Notifications for ATRIP notification setup, added the new ATRIP UAT Testing flow to UAT Validation, clarified that flight booking is required, added automatic verification guidance, expanded the Void workflow, 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

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:

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:

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:

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 identifier, flow-choice, and throttling guidance

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

What changed:

Updated pages:

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:

Added multi-channel notification setup guidance

Published Multi-channel Notifications 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 that webhook is one delivery option in the broader notification model

  • updated Airline Status Update Notification to position airline status as the first live multi-channel scenario

Updated pages:

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:

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:

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:

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

NextIntegration Guides

Last updated

Was this helpful?