Skip to main content
OCPI 2.2.1 roaming for eMSPs and charging networks

Connect EV charging networks through open standards

Savekar is a charge point operator (CPO) platform with an OCPI 2.2.1 interface. eMSPs and roaming partners can show Savekar-managed chargers in their apps, stop sessions remotely, and receive session and charge detail records, through documented endpoints and a structured onboarding. The interface is already in production with our roaming partners.

Read the documentation

What OCPI roaming solves

Reach drivers in partner apps

eMSPs can show Savekar-managed chargers in their own apps, so their drivers can find a charger, see its price and start charging.

One standard instead of custom work

OCPI is the open protocol charging networks use to exchange data. One standard interface replaces a separate custom integration for each partner.

Records both sides can reconcile

Sessions and Charge Detail Records (CDRs) are shared in the standard format, so both partners work from the same record of every charge.

Two protocols, two different jobs

OCPP and OCPI are often confused. Savekar uses both, for different connections.

OCPP 1.6J

Charger ↔ Savekar

How each charger talks to the Savekar charging management system: its status, starting and stopping sessions, and meter readings.

OCPI 2.2.1

Savekar ↔ eMSP or roaming partner

How Savekar, as the CPO, shares locations, tariffs, sessions and CDRs with partner platforms, and receives their commands. This is what this page is about.

Supported OCPI 2.2.1 modules

The modules Savekar implements as a CPO, and what each one is for.

Endpoints and payloads
  • VersionsReceiver

    Version discovery: the public entry point a partner calls first.

  • CredentialsReceiver

    Establishes the connection by exchanging tokens, and supports token rotation.

  • LocationsSender

    Charging locations, EVSEs and connectors, with their status.

  • TariffsSender

    Pricing, so a partner app can show drivers what charging costs.

  • SessionsSender

    Charging sessions and their updates, pushed as they happen.

  • CDRsSender

    Charge Detail Records pushed after each session, for reconciliation.

  • CommandsReceiver

    Operational commands from the partner. STOP_SESSION is supported.

How an integration works

  1. 1

    Review the documentation

    Read the supported modules, endpoints and example payloads in the OCPI documentation.

  2. 2

    Request access

    Tell us about your platform and the flows you need. We confirm the scope with you.

  3. 3

    Exchange credentials

    Connect through the Credentials module: tokens are exchanged to establish the connection.

  4. 4

    Test connectivity

    Test against our development environment. The OCPI simulator lets you try the flows from the eMSP side.

  5. 5

    Validate the flows

    Check locations, tariffs, sessions, CDRs and STOP_SESSION end to end with our team.

  6. 6

    Go live

    We coordinate production onboarding with you once testing is complete.

Good to know

  • Savekar acts as the CPO in OCPI 2.2.1 connections.
  • Each connection is set up per partner through onboarding; networks are not connected automatically.
  • Production access follows a successful test phase.
  • Modules not listed above, such as Tokens, are not currently supported. Tell us if your integration needs one.

Planning an OCPI integration?

Tell us about your platform and the flows you need. We will confirm the scope and set up your test access.

Read the documentation