> 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/technical-documentation/ocpi-version-support-2.1.1-2.2.1-and-2.3.0.md).

# OCPI Version Support 2.1.1, 2.2.1, and 2.3.0

ENAPI supports three OCPI versions. Our translation engine handles the differences automatically, so partners on different versions can still roam with each other.

<table><thead><tr><th width="101.55859375">Version</th><th width="156.81640625">Status</th><th>Notes</th></tr></thead><tbody><tr><td><strong>2.1.1</strong></td><td>Fully supported</td><td>Widely adopted. Lacks native hub support.</td></tr><tr><td><strong>2.2.1</strong></td><td>Fully supported</td><td>Most commonly used. Adds hub support, richer tariffs, role-based endpoints.</td></tr><tr><td><strong>2.3.0</strong></td><td>Recommended</td><td>Latest. Improved credential management and session handling. Native HGV and PnC support. </td></tr></tbody></table>

{% hint style="info" %}
**Note:** OCPI 2.2 (without the .1 patch) is not supported.
{% endhint %}

### Which version should I use?

If you're starting fresh, we recommend **2.2.1 or higher**.

If you already have a working 2.1.1 implementation, you don't need to upgrade. Our translation engine handles version differences between you and your partners — you can connect on 2.1.1 and roam with a partner on 2.3.0 without either side doing anything special. Find out more about [OCPI Version Interoperability](https://docs.enapi.com/advanced-features/ocpi-version-interoperability.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/technical-documentation/ocpi-version-support-2.1.1-2.2.1-and-2.3.0.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.
