> 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/api-reference.md).

# API Reference

{% 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 %}

{% hint style="warning" %}
All API Reference endpoint examples on this site show **sandbox** base URLs.

For production traffic, use the production API base URLs shown in ATRIP under `My Profile` → `Company Information`.

Production uses **two** API base URLs:

* one for `search` traffic
* one for all other transaction APIs

Do not send live traffic to sandbox endpoints.
{% endhint %}

Use this section for exact endpoint schemas, fields, and samples.

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

Start here when you need to:

* confirm exact request and response fields
* find the endpoint reference for a workflow
* validate field-level implementation details after reading the guides

### FAQ

#### When should I use API Reference?

Use API Reference when you need exact endpoint-level details such as request fields, response fields, schemas, and samples.

Use [Product Guides](/api-document/product-guides.md) first when you need flow choice, sequence guidance, or business decisions.

Use [Integration Guides](/api-document/readme-1.md) when you need onboarding, sandbox, UAT, or go-live steps.

#### Which page should I open first in API Reference?

Start with the workflow group that matches the task.

Then open the exact endpoint page for the API you are implementing.

### Browse by workflow

* [Booking APIs](/api-document/api-reference/booking-apis.md)
* [Post-booking APIs](/api-document/api-reference/post-booking-apis.md)
* [Webhook & Incident APIs](/api-document/api-reference/webhook-and-incident-apis.md)
* [Utility APIs](/api-document/api-reference/utility-apis.md)

### Common starting points

* [Search](/api-document/api-reference/booking-apis/search.md)
* [Verify](/api-document/api-reference/booking-apis/verify.md)
* [Create Order](/api-document/api-reference/booking-apis/create-order.md)
* [Payment & Ticketing](/api-document/api-reference/booking-apis/payment-and-ticketing.md)
* [Refunds](/api-document/api-reference/post-booking-apis/refunds.md)
* [Webhook Registration & Incidents](/api-document/api-reference/webhook-and-incident-apis/webhook-registration-and-incidents.md)
* [Balance](/api-document/api-reference/utility-apis/balance.md)
* [ATRIP Token](/api-document/api-reference/utility-apis/atrip-token.md)

### Recommended usage

1. Start with [Product Guides](/api-document/product-guides.md) for workflow choice.
2. Use [Integration Guides](/api-document/readme-1.md) for sandbox, UAT, and production rollout.
3. Use this section for request and response details.
4. Use [Support & Reference](/api-document/support-and-reference.md) for troubleshooting, shared reference data, and updates.

### Faster implementation with MCP

Use [MCP-Assisted Development](/api-document/readme-1/integration-tools/mcp-assisted-development.md) when you need help finding the right workflow, comparing related APIs, or narrowing down the next integration step.

Use this section as the field-level source of truth after the workflow is clear.

### What comes next?

After you confirm the endpoint schema, return to the matching workflow or integration page to continue implementation.