> 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/testing-modalities.md).

# Testing modalities

You can run the staging tests on your own time, or on a live call with the ENAPI integrations team. The simulators and the checks are the same either way — only the pace and the level of support differ.

## Asynchronous

Your technical team runs the handshake, drives the tests, and shares results. The integrations team validates asynchronously once you're ready. Pick this when you want to spread the work across your team, iterate on your side between steps, or simply have the time.

1. Register on [staging](https://app.staging.enapi.com/register).
2. Invite the relevant team members on the [team](https://app.staging.enapi.com/company/team) page.
3. Run the [handshake](https://app.staging.enapi.com/handshakes) and work through the tests.
4. [Contact](https://calendly.com/integrations-enapi) the ENAPI integrations team to validate your results.
5. Once you're green in staging, register on [production](https://app.enapi.com/register) and run the production [handshake](https://app.enapi.com/handshakes).

## Synchronous

Run everything on a live call with the integrations team. 50 minutes end-to-end — handshake, data checks, sessions, sign-off. Pick this when you want to move quickly, or have a question that's faster to resolve live.

1. Register on [staging](https://app.staging.enapi.com/register).
2. Invite the relevant team members on the [team](https://app.staging.enapi.com/company/team) page.
3. Book a 50-minute slot with your technical team and the integrations team on [Calendly](https://calendly.com/integrations-enapi/50min).
4. Handshake and tests are run live on the call.


---

# 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/testing-modalities.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.
