> For the complete documentation index, see [llms.txt](https://docs.enapi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.enapi.com/getting-started/testing-your-connection.md).

# Testing your connection

After the handshake, your platform is connected to the ENAPI integrations environment and your initial data is in. From here you work through a staging test that mirrors a real production integration end-to-end, and the ENAPI integrations team signs off before you move to production.

The pages below cover each part of that:

* [Overview](https://docs.enapi.com/getting-started/testing-your-connection/overview.md) — what testing proves and what you need in place
* [After the handshake](https://docs.enapi.com/getting-started/testing-your-connection/after-the-handshake.md) — what ENAPI sets up for you automatically
* [For CPOs](https://docs.enapi.com/getting-started/testing-your-connection/for-cpos.md) — where your data lands, what gets tested
* [For eMSPs](https://docs.enapi.com/getting-started/testing-your-connection/for-emsps.md) — where partner data lands, what gets tested
* [Starting and stopping sessions in staging](https://docs.enapi.com/getting-started/testing-your-connection/starting-and-stopping-sessions-in-staging.md) — drive a session from the portal
* [Success criteria](https://docs.enapi.com/getting-started/testing-your-connection/success-criteria.md) — what passing looks like
* [Testing modalities](https://docs.enapi.com/getting-started/testing-your-connection/testing-modalities.md) — sync vs async, pick one


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.enapi.com/getting-started/testing-your-connection.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
