# UAT Validation

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

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

Use this page when your sandbox integration is ready for go-live validation.

### Goal of this phase

Validate that the sandbox integration is ready for production.

This phase converts a completed sandbox integration into an approved go-live result.

### When to start UAT

Start UAT after:

* sandbox credentials are working
* the core booking flow is integrated
* request headers and authentication are stable
* webhook handling is ready if full integration UAT is required
* your team can execute test cases end to end

{% hint style="info" %}
Before UAT, run the [Sandbox Validation Test Kit](/api-document/readme/quick-start/sandbox-development/sandbox-validation-test-kit.md).

Use it to confirm credentials, network access, and the basic booking path before formal validation starts.
{% endhint %}

### UAT tracks

There are two UAT tracks.

#### 1. Shopping and Ticketing UAT

Use this track when you need to validate the standard search-to-ticket flow.

This usually covers:

* search
* verify
* order
* payment
* ticketing result

#### 2. Full Integration UAT

Use this track when you need to validate the end-to-end integration between Atlas and your booking platform.

This usually covers:

* passenger type combinations
* trip type combinations
* direct and connecting itineraries
* payment methods
* ancillaries
* webhooks
* operational follow-up flows

### What to prepare before submission

Prepare these items before submitting UAT:

* completed UAT template
* test evidence for each scenario
* expected and actual results
* relevant order numbers or request IDs
* webhook evidence when full integration is tested
* the Postman collection used by your team, if needed

### Recommended execution order

{% stepper %}
{% step %}

### Download the correct template

Pick the UAT track that matches your integration scope.
{% endstep %}

{% step %}

### Run all required scenarios

Execute every scenario in sandbox and record the result clearly.
{% endstep %}

{% step %}

### Attach evidence

Include request outcomes, screenshots, webhook samples, and order references where relevant.
{% endstep %}

{% step %}

### Submit via ATRIP

Submit the completed UAT result through Eva in ATRIP.
{% endstep %}

{% step %}

### Wait for review feedback

Atlas reviews the submission and may request clarification or retesting.
{% endstep %}
{% endstepper %}

### Download resources

#### Shopping and Ticketing UAT template

{% file src="/files/oFWdQtXQkvNu73lemrpz" %}

#### Shopping and Ticketing Postman collection

{% file src="/files/a9O0GV4nXQZ6OUIJ0b58" %}

#### Full Integration UAT template

{% file src="/files/KUBubQopcIiPauYwn4mI" %}

#### Full Integration Postman collection

{% file src="/files/zOebd5XZw1e7NNRr57UN" %}

### Submission path

After you complete the relevant template, submit the results through Eva in ATRIP.

![](/files/Mbeuge0jojBZI5ouG3SV) <mark style="color:$info;">**==>**</mark> ![](/files/PhftninIhVnIxyzWGgQI)

### Common reasons a submission is sent back

* missing scenarios
* incomplete expected or actual results
* no supporting evidence
* unclear passenger or trip type coverage
* webhook flow not demonstrated for full integration UAT

### Complete this phase when

You have all of these:

* submitted the correct UAT track
* attached the required evidence
* resolved any review feedback
* received UAT approval

### Output of this phase

* approved UAT result
* confirmed go-live readiness

### Next step

After UAT passes:

* ask your customer manager to switch the account to `LIVE`
* generate production credentials
* set up the production IP whitelist
* replace sandbox endpoints
* run a controlled smoke test
* monitor the first live orders and webhook events

### Related pages

* [Sandbox Development](/api-document/readme/quick-start/sandbox-development.md)
* [Sandbox Validation Test Kit](/api-document/readme/quick-start/sandbox-development/sandbox-validation-test-kit.md)
* [Quick Start](/api-document/readme/quick-start.md)
* [Production Go-Live](/api-document/readme/quick-start/production-go-live.md)
* [Webhook Overview](/api-document/readme/webhook-overview.md)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://resources.atriptech.com/api-document/readme/quick-start/uat-submission-guide.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.