We are opening the Application Marketplace, and we want you to build on it. If you have ever wanted to plug into a customer’s charging data, layer new functionality on top of Road.io, or ship an integration your users have been asking for, this is your way in.

Built on standards you already know

Road.io is now an OpenID Connect provider. There is no bespoke protocol to learn and no shared API keys to pass around. It is OAuth 2.1 and OpenID Connect, Authorisation Code flow with PKCE, discovery documents, JWKS, the works. If you already have an OIDC library, you are most of the way to a working integration.

That is the whole point: getting connected should be the boring part, so you can spend your time on the app itself. The authentication guide walks through the flow end to end.

A growing set of scopes

Access is scoped and consent-driven. There is already a documented set of scopes covering identity, account details, charging stations, and charging sessions, and that set grows steadily as we open up more of the platform.

Trust is the feature

The protocol matters, but the consent model matters more. Customers stay in control, and not just over which scopes an app is granted. They also decide exactly which pieces of their data are shared, down to individual locations and chargers, and they can change or revoke that at any time.

Access reflects what a customer actually owns and shares, continuously, not a snapshot frozen at sign-up. For you as a developer that means integrations customers can trust by design, which is the difference between an app people install and an app people keep.

Start building

Everything you need to register an app, authorise a customer, and make your first call is in the documentation.

This is the best time to get involved and shape where it goes. Build something, and tell us what you are making.