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

# For eMSPs

## Where partner data lands

* **Locations → Partner data** — the simulator's locations exposed to you, as they would appear from a real CPO partner.
* **Tariffs** — tariffs ENAPI received from the simulator.

## What gets tested

### Inbound — ENAPI pulls from you

* **Tokens** — format, authentication data, state management. If you only use Commands, this step is skipped.

### Outbound — you pull from the CPO simulator

* **Locations** — completeness, filtering.
* **Tariffs** — pricing accuracy, update mechanism.

### Session flow

1. **Start** — sessions are started using your tokens, either from ENAPI or through your interface. Authorization and routing are verified.
2. **Updates** — ENAPI session updates are routed to you.
3. **Stop and CDR** — termination executed; CDR generated and routed to you.
4. **RFID authentication** — tested manually with the ENAPI onboarding team.

To drive a session yourself from the portal, see [Starting and stopping sessions in staging](https://docs.enapi.com/getting-started/testing-your-connection/starting-and-stopping-sessions-in-staging.md).


---

# 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/for-emsps.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.
