> 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/onboarding-to-enapi.md). # Onboarding to ENAPI Onboarding to ENAPI starts with creating your account and ends with you live on the platform, exchanging data with roaming counterparties. This page gets you oriented — which path to pick, which environment to start in, and who on your team does what. The actual handshake lives in [Set up your OCPI Handshake with ENAPI](/getting-started/set-up-your-ocpi-handshake-with-enapi.md). ### **Pick your region first** ENAPI runs as independent platforms in Europe and North America. The region you register in decides where your data is stored and processed and which counterparties appear in your roaming directory — there's no cross-region roaming yet, so this is a commercial decision as much as a technical one. In most cases, choose the region where your charge points or your drivers are. Read [Regions](about:blank) before you register, or with the team at if you're unsure or if you expect to operate in both. **Partners in Australia and New Zealand** As we scale we will build out more regions - for now if you are a partner in Australia or New Zealand please select ‘Europe’ as your region. ### Before you start: who you'll need Onboarding touches three roles on your side. They can be the same person at smaller operators, but the work is distinct: * **Commercial owner** — signs the Terms & Conditions with ENAPI, decides which counterparties to roam with, and signs roaming agreements. * **Technical owner** — runs the OCPI handshake, configures endpoints, and validates data flows. Needs admin access to your backend. * **Operations owner** — monitors live sessions and CDRs after go-live, handles disputes, and is the escalation point for support. Often takes over from the technical owner once production is stable. If you're a fast-track partner (see below), the technical owner's role is mostly a verification check rather than a build. ### Testing on staging first, then production Most partners start in staging — a sandbox where you run the handshake, test endpoints, and verify data flows. Concretely, this means you've completed the credentials handshake, successfully exchanged data on every OCPI module in your scope (typically Locations, Sessions, CDRs, Tokens, Commands and Tariffs), and run at least one end-to-end test session that produces a matching CDR on both sides. Once that's signed off, you repeat the same handshake in production with live credentials. {% hint style="info" %} **Fast-track exception:** If you operate on a CPMS we've already integrated with — AMPECO, ChargePoint, Driivz, Evesto, and others — you can skip staging and onboard directly to production. These platforms are pre-validated against ENAPI, so there's no new technical surface to test; we already know the OCPI version, module support, and quirks of each. Ask your account manager if you're not sure which applies to you, or if you're on a custom instance of one of these platforms (forks often need a light staging pass). {% endhint %} ### Which OCPI version do you need? ENAPI's platform translates between [OCPI Version Interoperability](/advanced-features/ocpi-version-interoperability.md), so you don't need to match your counterparty's version — you just need to tell us yours. If you're not sure, your CPMS vendor or technical owner can confirm. Version differences mostly affect which modules and fields are available. **One exception:** if you're connecting as a data aggregator or a payment terminal provider, use 2.2.1 or later — OCPI 2.1.1 can't express your role, so a 2.1.1 connection is registered as an eMSP. Check that your platform sends your actual role rather than defaulting to EMSP, and if you're a PTP, prefer 2.3.0. ### Create your account 1. Go to [app.staging.enapi.com](http://app.staging.enapi.com/) (or, if you're on the fast-track, [app.enapi.com](http://app.enapi.com/) for Europe or [app.us.enapi.com](http://app.us.enapi.com/) for North America) and click **Register here**. 2. Enter your name, business email, and a password. 3. Choose your Region — Europe or North America. This is where your organization and all of its data will live; see [Regions](about:blank). 4. Click the confirmation link we email you. The link expires after 24 hours; request a new one from the login page if it does. 5. Enter your organization's legal name and brand name. Legal name is what appears on contracts and invoices; brand name is what counterparties see in the roaming directory. 6. Review and submit. Your account is active — but roaming isn't live yet. You still need to complete the OCPI handshake and, for production, have signed or accepted the Terms & Conditions on ENAPI. Staging access doesn't require the agreement, so you can start technical work in parallel with commercial paperwork. {% hint style="warning" %} Region can't be changed from the Portal after registration. If you realise you picked the wrong one, contact support before running your handshake — moving an organization between regions is a manual operation. {% endhint %} ### Invite your team Once your account is created, you can invite the rest of your team from the **Settings → Team** section. Add each person by email and they'll receive an invitation link to set up their own login under your organization. We recommend bringing in your technical and operations owners early so they have access during the handshake and validation phases. ### What happens next Your account manager will reach out within one business day to confirm your party ID, region, and the OCPI modules you want enabled. Your **party type** — CPO, eMSP, data aggregator, payment terminal provider, or a combination — is taken from the role you declare during the [OCPI handshake](/getting-started/set-up-your-ocpi-handshake-with-enapi.md); see [Roles and Parties on ENAPI](/getting-started/roles-and-parties-on-enapi.md) if you're not sure which applies to you. From there: * **Run the handshake** → [Set up your OCPI Handshake with ENAPI](/getting-started/set-up-your-ocpi-handshake-with-enapi.md) * **Validate your integration in staging** → [Testing your OCPI Handshake with ENAPI](/getting-started/testing-your-ocpi-handshake-with-enapi.md) * **Book your commercial onboarding meeting** → [Schedule a time with Jakob](https://calendly.com/enapi) * **Send your first roaming offer** → [Roaming](/roaming.md) **Not roaming?** Data aggregators and payment terminal providers send offers the same way — on their own contract. See [Custom Contract Templates](/roaming/custom-contract-templates.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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.enapi.com/getting-started/onboarding-to-enapi.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.