> 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/readme-1.md).

# Integration Guides

{% hint style="info" %}
💬 **Need help?** If you're stuck, ask Eva in the Help Center for instant diagnostics.

<a href="https://www.atriptech.com/" class="button primary" data-icon="comments">Ask Eva</a>
{% endhint %}

Use this section for Atlas onboarding and the full implementation lifecycle from sandbox to go-live.

New to the product? Read [What is Atlas API?](/api-document/what-is-atlas-api.md) for an overview of supported workflows.

Start here when you need to:

* get access and credentials
* build the integration in the right order
* prepare UAT evidence
* complete production cutover safely

### What belongs in Integration Guides

Use this section for:

* onboarding and access setup
* sandbox implementation
* validation and go-live preparation
* integration-stage setup tasks

Use [Product Guides](/api-document/product-guides.md) when you need to choose the right booking flow or product capability.

Use [API Reference](/api-document/api-reference.md) when you need exact endpoint fields and schemas.

### Recommended reading order

1. [Quick Start](/api-document/readme-1/quick-start.md)
2. [Sandbox Access](/api-document/readme-1/making-requests.md)
3. [Sandbox Development](/api-document/readme-1/sandbox-development.md)
4. [UAT Validation](/api-document/readme-1/uat-submission-guide.md)
5. [Production Go-Live](/api-document/readme-1/production-go-live.md)

Use [Integration Tools](/api-document/readme-1/integration-tools.md) when you want optional implementation accelerators such as [Atlas AI Assistant Skill](/api-document/readme-1/integration-tools/atlas-ai-assistant-skill.md) or [MCP-Assisted Development](/api-document/readme-1/integration-tools/mcp-assisted-development.md).

### Common starting points

#### New Atlas API integration

Start with [Quick Start](/api-document/readme-1/quick-start.md).

Then move to [Sandbox Access](/api-document/readme-1/making-requests.md) and [Sandbox Development](/api-document/readme-1/sandbox-development.md).

#### UAT and launch preparation

Use [UAT Validation](/api-document/readme-1/uat-submission-guide.md) and [Production Go-Live](/api-document/readme-1/production-go-live.md).

#### Notification setup during integration

Use [Webhook Overview](/api-document/product-guides/extensions-and-integrations/webhook-overview.md) for webhook event coverage and handling guidance.

Use [Multi-channel Notifications](/api-document/product-guides/extensions-and-integrations/multi-channel-notifications.md) for channel setup across webhook, email, DingTalk, WeCom, Slack, and Teams.

#### Need to choose a booking flow?

Use [Product Guides](/api-document/product-guides.md).

Start with [Booking Overview](/api-document/product-guides/booking/booking-overview.md) when you are deciding between the three main booking paths.

### Typical implementation lifecycle

{% stepper %}
{% step %}

### Access and kickoff

Collect sandbox credentials and confirm required request headers.
{% endstep %}

{% step %}

### Sandbox development

Build the integration in sandbox and validate the main implementation path.
{% endstep %}

{% step %}

### UAT validation

Run the required UAT track and submit the evidence package.
{% endstep %}

{% step %}

### Production go-live

Switch to production credentials and endpoints after UAT approval and account activation.
{% endstep %}
{% endstepper %}

### Related sections

* [Product Guides](/api-document/product-guides.md)
* [API Reference](/api-document/api-reference.md)
* [Support & Reference](/api-document/support-and-reference.md)