Skip to main content
Product boundary Roam OCPI is a separate product from Drive API. Choose Roam OCPI when you want a managed roaming integration through OCPI 2.2.1. If you need Drive API-specific user, payment, charging-key, or proprietary session flows, use the Drive API docs instead.
Roam OCPI is designed to share the entire Plugsurfing network to businesses who want to expand their own network offering. Roam OCPI offers:
  • Network: Enables EMPs to expand their customer offering with one of the largest European charging networks.
  • Managed roaming: A one-stop shop for EMPs, covering everything from CPO targeting and integrations to invoicing and risk management.
  • Industry standard connection: Provides a hassle-free and structured onboarding and integration process with the industry standard OCPI protocol.
Roam OCPI is built on OCPI version 2.2.1. Download the OCPI 2.2.1 documentation Roam OCPI has some deviations from the standard OCPI protocol due to the massive amount of data and updates that would be required if the standard specification would be followed. The deviations to OCPI 2.2.1 are lined out by module in the Roam OCPI documentation. The main deviations are:
  • Tariffs: Instead of supporting tariff module and sending through all tariff updates that Plugsurfing gets from CPOs, the relevant tariffs are inlined on each connector via the Location module. This way the EMP will be shielded from a large amount of tariff updates every day.
  • Status updates: Plugsurfing will not push status updates due to the large amount of data. Instead, Plugsurfing offers the EMP to do delta pull up to every minute, which will give accurate statuses on connectors without the same amount of unnecessary traffic.

​
Interactions between your EMP, Plugsurfing Roam OCPI, and the CPO

With Roam OCPI you can get the entire Plugsurfing network through one single OCPI integration. Plugsurfing takes care of the agreements, communication and invoices with all CPOs, and you just need to care about one integration and one partner. This product path should not be mixed with Drive API-specific flows and docs.