> 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/starting-and-stopping-sessions-in-staging.md).

# Starting and stopping sessions in staging

Drive a session end-to-end from the portal to verify the full flow. Works on any EVSE you can see — your own if you're a CPO, partner EVSEs if you're an eMSP.

## Start a session

1. Open the location, find the EVSE row, click the **⋯** menu and pick **Start a charge**.

   ![EVSE row with the Start a charge menu item](https://303450155-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FheBP0sH0U1Rrp1jIot9S%2Fuploads%2FEaOzZJOjUuDhcxl7nN0r%2F01-evse-menu-start-a-charge.png?alt=media\&token=72c93341-85b5-4b4d-946b-56a402f93405)
2. The **Start a charge** dialog opens. Pick the mode that matches your role, then click **Start charging**.

   **CPO — Remote start.** Select one of the eMSP simulator's tokens from the dropdown. Our test eMSP sends a remote-start command to us, forwarded to your platform using that token.

   ![Start a charge dialog, Remote start tab with token dropdown](https://303450155-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FheBP0sH0U1Rrp1jIot9S%2Fuploads%2Fv2krOQ53oV2pl3mTyzst%2F02-start-charge-dialog-remote-start-cpo.png?alt=media\&token=2972a435-f81a-481c-a6e9-6b15ea46fb45)

   **eMSP — RFID swipe.** Enter one of your own token UIDs. ENAPI simulates an RFID swipe on the EVSE using that token.

   ![Start a charge dialog, RFID swipe tab with token UID field](https://303450155-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FheBP0sH0U1Rrp1jIot9S%2Fuploads%2FKsJAAA2Yy7SSpIvIdkGM%2F03-start-charge-dialog-rfid-swipe-emsp.png?alt=media\&token=5911bbca-582c-49f8-982f-f71e4a1c2f54)
3. The session appears in **Sessions** with status **Active**.

   ![Sessions list with the active session visible](https://303450155-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FheBP0sH0U1Rrp1jIot9S%2Fuploads%2FNzWIi5b1mVoAegV6gvD2%2F04-session-active-in-sessions-list.png?alt=media\&token=66a0b31a-f403-4643-9256-edd2522a4270)

## Stop a session

1. Open the session from the **Sessions** list.
2. Click **Stop charge** at the top of the session detail.

   ![Session detail view with the Stop charge button](https://303450155-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FheBP0sH0U1Rrp1jIot9S%2Fuploads%2FfPwHfYA7rNIP9uEKagct%2F05-session-detail-stop-charge.png?alt=media\&token=0229cd28-c602-4d4e-8a3d-2a4aeca45802)

A CDR is generated and routed by the simulator shortly after. Where it lands is covered in [For CPOs](https://docs.enapi.com/getting-started/testing-your-connection/for-cpos.md) and [For eMSPs](https://docs.enapi.com/getting-started/testing-your-connection/for-emsps.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/starting-and-stopping-sessions-in-staging.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.
