Skip to main content
Roaming puts your chargers in front of drivers from other networks, and gets your own drivers charging on networks you don’t operate.

​
Overview

Spirii supports roaming on both sides of your business, and what it does for you depends on the role you’re in:

As a CPO

Publish and price your chargers for roaming. Spirii exposes them to drivers on other networks, and you see the resulting sessions and revenue — without building a driver base of your own.

As an eMSP

Connect your drivers to other networks’ chargers. Your charge keys and branded app reach roaming chargers across the ecosystem, so your drivers always have somewhere to charge.

​
How it works

Spirii connects to the roaming ecosystem on your behalf, in two ways:
  • Roaming hubs — marketplaces like Hubject, Gireve, and e-clearing.net that aggregate many CPOs and eMSPs. Spirii’s network is connected to the major hubs, so once you enable roaming, your chargers reach the drivers on them and your drivers reach their chargers.
  • Direct integrations — one-to-one connections to specific networks, built over the OCPI protocol and maintained by Spirii. You reach these without negotiating an agreement of your own.
Spirii manages the connection, the data exchange, and settlement for both.

​
Pricing

As a CPO, you set a roaming tariff per location in Spirii Connect: a flat rate per kWh, and the price you’re paid. You enter it gross, so it’s comparable with your standard tariff, but eMSPs are billed the net amount, which is what you receive. Account for the platform fees that apply to roaming sessions so your margin holds. Roaming pricing covers how the tariff is chosen and when a change takes effect. What a driver ultimately pays can differ. When a driver from another network charges on your chargers, their own eMSP decides their final price. As an eMSP, your drivers pay the host CPO’s price for a roaming charge, passed through to your branded app.

​
When to use it

Publishing your chargers across roaming brings in drivers who would never install your app, lifting usage on every location you expose.
Roaming brings third-party drivers from day one, before you’ve built up loyal local drivers of your own.
Roaming gives your drivers access to charge points across other networks, so there’s always somewhere to charge.

​
Set up

What you do depends on your side.

​
As a CPO

Publish and price your chargers. Each location you want on roaming must be:
  • Set to public, with roaming enabled and a roaming tariff set
  • Given a latitude and longitude
  • Using connector IDs in the eMI3 format — the EVSE ID plus the connector number, asterisk-separated, such as DE*SPI*E00012345*1. Invalid IDs keep a charger off roaming.
That format derives from your CPO operator ID, or prefix, such as DE*SPI. Spirii helps set the prefix up once you’ve registered it with your local national registry and the roaming hubs have approved it. Set up a public charging hub covers this alongside the rest of a public site.

​
As an eMSP

Connect your charge keys and app. Each charge key your drivers use must be:
  • Active and roaming-enabled
  • Labelled following the recommended format DK.SPI.C{customerPrefix} to avoid interoperability issues — Spirii converts the label to the formats hubs and OCPI require behind the scenes
Drivers reach roaming chargers through your branded app or Spirii Go, where they appear alongside your own network’s. Fleet quickstart covers issuing the keys and getting drivers on the road.

​
Dependencies & limitations

  • Roaming depends on more parties. A roaming session involves the CPO, the eMSP, and often a hub, so more can interrupt a charge than on a session within your own network.
  • Data formatting is strict. Location, EVSE, and charge key data must follow the required formats (see Set up); incorrect data is the most common reason a charger doesn’t appear or a session fails.
  • The eMSP controls the final price and its own data. You can’t set what a driver pays on your chargers over roaming, and a change you make — price or status — appears in the eMSP’s app only as fast as they refresh it.

Roaming settlement

How the money moves in both directions once sessions are exchanged.

Network coverage

See and filter the chargers your drivers can reach over roaming.

Locations

Enable roaming and set the roaming tariff per location.

Charge keys

How an eMSP’s drivers authenticate across networks.

EVSEs and connectors

Where the connector IDs roaming requires come from.

Sessions and CDRs

The records exchanged over roaming and used to settle each charge.