Quick Start

Four-phase integration path from sandbox access to production go-live.

Use this guide to move from Atlas sandbox access to live launch.

End-to-end integration flow from sandbox access to go-live

Integration flow

1

Sandbox Access

Generate sandbox credentials and confirm the request basics.

2

Sandbox Development

Build and validate the full integration in sandbox.

3

UAT Validation

Complete the required UAT track after sandbox development is stable.

4

Production Go-Live

After UAT passes and your account is switched to LIVE, generate production credentials and switch to production endpoints for go-live.

How the full flow works

1. Sandbox Access

This is the starting point of the integration.

Generate your sandbox client ID and client secret in ATRIP.

Before moving forward, confirm:

  • standard headers

  • request format

  • identifier handling

  • gzip handling

You are ready for the next phase when sandbox requests can be sent successfully.

Use Sandbox Access for this setup.

2. Sandbox Development

Use sandbox to complete the actual integration work.

This phase usually includes:

  • sandbox environment setup

  • search, verify, order, and payment

  • order query and ticketing follow-up

  • webhook registration and event handling

  • sandbox test data and failure simulation

The goal is not only to call APIs successfully.

The goal is to complete the end-to-end business flow in sandbox.

Use these pages during development:

During this phase, keep these identifiers for later steps:

  • Search: routingIdentifier

  • Verify: sessionId

  • Order: orderNo

Move to UAT only after the sandbox flow is stable and repeatable.

3. UAT Validation

UAT is the validation phase before production.

Use this phase to prove that your integration is ready for go-live.

Prepare:

  • the correct UAT template

  • end-to-end evidence

  • webhook samples when required

  • relevant order numbers or request IDs

The main output of this phase is UAT approval.

Use UAT Validation for the submission steps.

4. Production Go-Live

Start this phase when your sandbox work is complete and you are ready for production.

Then:

  • complete the required UAT work

  • wait for your customer manager to switch the account to LIVE

  • generate production credentials

  • replace sandbox endpoints

  • run a controlled smoke test

  • monitor the first live orders and webhooks

  • go live in production

This completes the move from test integration to live operation.

Use Production Go-Live for the go-live checklist.

What each phase produces

  • Sandbox Access → sandbox client ID and client secret

  • Sandbox Development → stable sandbox booking and webhook flow

  • UAT Validation → approved validation result

  • Production Go-Live → production-ready environment

First end-to-end test resource

Use this Postman collection during sandbox development:

Last updated

Was this helpful?