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

# Overview

The [handshake](https://docs.enapi.com/getting-started/set-up-your-ocpi-handshake-with-enapi.md) exchanges credentials and endpoints. Testing is the next step: proving that OCPI data flows both ways, that sessions complete end-to-end, and that CDRs land where they should.

The ENAPI integrations team validates every connection before it goes to production, typically on a call.

## Prerequisites

* A functioning OCPI implementation in 2.1.1, 2.2.1, or 2.3
* A staging account on [app.staging.enapi.com](https://app.staging.enapi.com/register)
* Your technical team invited to the account via the [team](https://app.staging.enapi.com/company/team) page

## How it fits together

1. [After the handshake](https://docs.enapi.com/getting-started/testing-your-connection/after-the-handshake.md) — ENAPI pairs you with the opposite-role simulator and pulls your initial data.
2. [For CPOs](https://docs.enapi.com/getting-started/testing-your-connection/for-cpos.md) or [For eMSPs](https://docs.enapi.com/getting-started/testing-your-connection/for-emsps.md) — role-specific view of where your data lives and what gets exercised.
3. [Starting and stopping sessions in staging](https://docs.enapi.com/getting-started/testing-your-connection/starting-and-stopping-sessions-in-staging.md) — drive sessions yourself to cover the full flow.
4. [Success criteria](https://docs.enapi.com/getting-started/testing-your-connection/success-criteria.md) — the bar for sign-off and the move to production.
5. [Testing modalities](https://docs.enapi.com/getting-started/testing-your-connection/testing-modalities.md) — async or sync; pick the pace that fits.


---

# 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/overview.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.
