Atlas API FAQs
Common Atlas API integration questions for setup, booking, payment, ticketing, post-booking, and finance topics.
Use this section for common Atlas API integration questions and edge cases.
New to Atlas API? Read What is Atlas API? for product capabilities and starting points.
Start here when you need to:
find the right FAQ by implementation stage
answer a common onboarding or booking question fast
route payment, ticketing, or post-booking questions to the right page
Start with the right FAQ section
Before kickoff or onboarding
Use these pages first:
Sandbox, setup, and first implementation
Use:
Search, booking, and ticketing
Use:
Payment, refund, and finance
Use:
Post-booking operations
Use:
FAQ categories
FAQ
What is Atlas API?
Atlas API supports flight shopping, booking, payment, ticketing, and post-booking operations.
Use Atlas API concepts for definitions of booking flows, identifiers, orders, and webhooks.
Where should a new Atlas API partner start?
Start with Before Integration for high-priority planning questions.
Then use Kickoff Checklist to align flow choice, payment design, ticketing handling, and launch scope.
Where can I find booking and ticketing questions?
Use Search & Booking for search, verify, pricing, and booking flow questions.
Use Orders & Ticketing for order status, ticketing, PNR, and follow-up questions.
Use Fulfilment API FAQ when the main question is whether Fulfilment API fits your model or how it works alongside existing Atlas interfaces.
Where can I find payment or refund questions?
Use Payments for deposit, VCC, card handling, and payment limits.
Use Fulfilment API FAQ when the payment question is tied to Fulfilment API fit, dual payment paths, or failure alert timing.
Use Post-booking and Finance for refunds, follow-up, top-ups, and reconciliation questions.
Last updated
Was this helpful?

