> 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.md). # Getting Started ### What ENAPI does ENAPI is the open platform that commoditizes connectivity across the EV charging ecosystem. Connect once via OCPI and reach all of our connected partners: Charge Point Operators (CPOs), e-Mobility Service Providers (eMSPs), data aggregators, and payment terminal providers (PTPs). Discover partners, sign agreements in clicks, let data sync automatically, and clear finances without spreadsheets. We handle the complexity of deal making, technical connectivity, and financial clearing so you can focus on growing your business. ### The platform at a glance ENAPI is organized around the lifecycle of a roaming partnership: * [Roaming](/roaming.md). Find roaming partners, sign legal contracts, and configure the commercial offer. This is where new roaming connections start. * [Technical Documentation](/technical-documentation.md). Live visibility into locations, sessions, and data quality across your connected network — so issues get caught before drivers feel them. * [Data Quality](/data-quality.md). Live visibility into locations, sessions, tokens, and tariffs across your connected network — so issues get caught before drivers feel them. * [CDR Clearing](/cdr-clearing.md). The pipeline that turns raw charging records into billable, disputable line items, with full end-to-end visibility. Plus reference sections you'll come back to as you grow: * [Pricing & Tariffs](/pricing-and-tariffs.md). How tariffs flow on ENAPI, plus partner-specific and ENAPI-managed pricing models. * [Advanced Features](/advanced-features.md). Routing, version interoperability, Plug & Charge, and tracing. * [Security, Compliance & SLAs](/security-compliance-and-slas.md). Uptime commitments, incident handling, data residency (see also [Regions](/getting-started/onboarding-to-enapi.md)), and certifications. ### How it works ENAPI is built on OCPI (Open Charge Point Interface), the industry standard for exchanging roaming data between charging networks. OCPI defines how location data, tariffs, tokens, charging sessions, and billing records flow between parties. You connect to ENAPI through [Set up your OCPI Handshake with ENAPI](/getting-started/set-up-your-ocpi-handshake-with-enapi.md) — a one-time technical setup. After that, data flows automatically. Your locations and tariffs sync to the hub, partner data becomes available to you, and when a roaming agreement is signed, transactions start flowing immediately. No additional integration work required. ENAPI supports [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). If your partner is on a different version than you, [OCPI Version Interoperability](/advanced-features/ocpi-version-interoperability.md) handles the conversion automatically. You don't need to be on the same version to roam together — that's the kind of friction we're here to remove. ### Start here Use this section in order: * [Onboarding to ENAPI](/getting-started/onboarding-to-enapi.md) — create your account and pick the right onboarding path. * [Set up your OCPI Handshake with ENAPI](/getting-started/set-up-your-ocpi-handshake-with-enapi.md) — connect your platform to ENAPI. * [Testing your OCPI Handshake with ENAPI](/getting-started/testing-your-ocpi-handshake-with-enapi.md) — validate your setup before go-live. * [The ENAPI Portal](/getting-started/the-enapi-portal.md) — learn where each workflow lives. * [Settings and Configuration](/getting-started/settings-and-configuration.md) — configure your users, organization, and products. --- # 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 dynamically 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.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 `build a script that syncs our docs to a CMS` 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.