Plugsurfing's APIs
Plugsurfing offers two separate integration products. Customers typically choose either Drive API or Roam OCPI, not both.
About Plugsurfing
Plugsurfing is a leading eMobility Service Provider (eMSP or EMP) in Europe, offering electric vehicle (EV) drivers access to an extensive network of public charging points across European countries. Through its app and charging card, Plugsurfing enables users to locate charging stations, and then initiate and pay for charging sessions seamlessly.
Choose your integration path
Plugsurfing offers two separate integration products: Drive API and Roam OCPI.
A customer normally chooses one integration path, not both.
Do not mix Drive API endpoints, AI tooling, user flows, payment flows, or charging-key management with the Roam OCPI module documentation.
| Product | Choose it when | Not the right fit when | Source of truth |
|---|---|---|---|
| Drive API | You want Plugsurfing's proprietary integration for charging data, users, payments, charging keys, and remote sessions. | You want a standards-based OCPI 2.2.1 roaming integration. | Drive API guides, API Reference, and MCP for AI Agents |
| Roam OCPI | You want managed roaming through an OCPI 2.2.1 integration path. | You need Drive API-specific user, payment, subscription, or charging-key order flows. | Roam OCPI guides and the OCPI 2.2.1 specification |
Use Drive API when you want the broader Plugsurfing product surface.
Use Roam OCPI when you want the OCPI-based roaming product.
Updated about 9 hours ago