> 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.md). # Technical Documentation Technical reference for the teams implementing against ENAPI. [Getting Started](/getting-started.md) and [Roaming](/roaming.md) got you connected and roaming. This section is what your engineers will come back to. ### **Implement OCPI once** Every OCPI implementation in production is slightly different — different versions, different module coverage, different interpretations of optional fields. Without a clearing layer, you absorb that variance into your code for every new partner. ENAPI handles it. Your team implements OCPI once, against ENAPI. We translate between versions, normalize field interpretations, and shield you from partner-specific quirks. This section documents what we support and how we behave. ### In this section Start with the page that matches your question: * [OCPI Version Support 2.1.1, 2.2.1, and 2.3.0](/technical-documentation/ocpi-version-support-2.1.1-2.2.1-and-2.3.0.md) — check which OCPI versions ENAPI supports. * [Supported OCPI Modules and Capabilities](/technical-documentation/supported-ocpi-modules-and-capabilities.md) — see which modules ENAPI supports today. * [How ENAPI Syncs OCPI Data](/technical-documentation/how-enapi-syncs-ocpi-data.md) — understand initial sync, deltas, and full syncs. --- # 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.md?ask=&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.