Chargers
Back offices
Your platforms
Two ProVolt Time
Eve Single ProAlfen
Pulsar MaxWallbox
345 more brands
Plugchoice
E-Flux
GreenFlux
Monta
315 more
Web portal
App
Your productREST API
OCPP 1.6J
OCPP 1.6J
JSON
One API for every charger.
Whatever the charger brand, whichever back office it already reports to, your product gets one normalised API. That back office can stay connected, so nothing you run today has to change.
Plugchoice
One API
Your product
How a charger reaches your product
Examples of what you can build
The full reference is on developer.plugchoice.com.
POSTactions/charge-limit
{ "connector_id": 1, "limit": 10 }
Limit10 A
Latest meter value
{
"measurand": "Power.Active.Import",
"phase": "L1",
"value": "2468", "unit": "W"
}
PUTconnectors/{connector_id}
phase_rotationRST
max_amperage16
OCPP logs
10:04BootNotificationAccepted
10:05AuthorizeAccepted, E-Flux
10:05StartTransactionid 1725528
10:09AuthorizeRejected, E-Flux
Charger actions, bulk
✓Two Pro Parking
✓Dock One Business
✓Depot West
Apply to 12 chargers
Bring Plugchoice into your own app
Everything the Plugchoice app does, the API does too. Build the parts you need into your own app, and your customer gives it access with OAuth 2.0. Every framed element is one call.
- REST APIEvery call documented on developer.plugchoice.com
- SDKPlugchoice features for your own app, on top of the API
- Normalised charger dataChargers, connectors, sessions and meter values in the same fields, whatever the maker
Your user adds a charger without leaving your app
Our SDK opens Link, the hosted onboarding, inside your app. Your user follows a few steps on their phone and Auto Connect does the technical work, so nobody types a websocket URL or chargepoint ID.
1Your user taps Connect charger
In your app or on your website. You already know who they are and where the charger is, so Link starts from there.
2They agree to share their charger with you
The consent screen carries your name, logo and colour, and lists what you may see and control.
3They pick their charger
12 brands have a setup made for them. Any other OCPP charger is added by hand, in the same flow.
4Auto Connect sets it up
Link reaches the charger over Wi-Fi, Bluetooth or the brand's cloud, points it at Plugchoice and shows each step as it goes.
5The current operator stays
When the charger already reports to a back office, it stays connected next to Plugchoice.
What Link takes care of
- Its charging history, imported once when the charger is added, for the brands with a dot
- Its charging cards, put on the whitelist, where the brand allows it
- The back office it already used, kept through our OCPP proxy
- New brands arrive in the hosted flow, without a new release of your app
12 brands with Auto Connect
Each brand has a setup of its own. A charger that is not on the list goes through the same flow and is set up by hand.
- Alfen
- Easee
- Enovates
- go-e
- Peblar
- Ratio
- SolarEdge
- Teltonika
- Volt Time
- Wallbox
- Webasto
- Zaptec
Link imports the charging history
Users who already have the Plugchoice app connect your product there with OAuth 2.0. The SDK is in beta until version 1.0.
Questions partners ask
What if a charger cannot be connected automatically?
Your user stays in the same flow. They type the charger's chargepoint ID. Link shows what to set in the charger's own settings or app, and waits until the charger connects.
Do we get the charging history?
Yes, for the brands marked with a dot above. Link imports it once, when the charger is added. Reconnecting a charger later imports nothing again.
Does my customer see the Plugchoice app?
No. With the SDK your customer stays in your app. Link carries your name, logo and colour, with Plugchoice named next to it.
The charger already runs on another platform. What happens to it?
It stays connected. The charger connects to Plugchoice, and our OCPP proxy passes its traffic on to the back office it already had.
What do we need to build?
An endpoint on your server that asks Plugchoice for a client secret, a button that opens Link, and a check when Link closes. Without any code, a start link or a QR code works too.
Can we try it before we go live?
Yes. You get test credentials first, and test mode works with real chargers, so you can try everything with your own.
Which platforms does the SDK support?
iOS 16 and later, Android 10 and later, React Native with Expo, and the web. The code is open source on GitHub.
Who decides what my product may do?
Your user. They agree to what you may see and control, and can disconnect your product at any time in Plugchoice. Hosting and subprocessors are on our security page.
Get listed where owners add a back office
Owners and installers choose from 300+ back offices when they connect a charger. Once your integration is live, your platform is in that list too.
- In the app and the web portalOwners add you in a few taps and choose your role: Billing, or Data and control.
- A page in our integrations directoryInstallers and charge point operators find you on plugchoice.com when they choose what to connect.
- Switching needs no site visitThe charger stays connected to Plugchoice, so moving to your platform needs no new settings on the charger.
What it runs on
A charger connects once. Plugchoice passes its OCPP traffic on to the back offices and serves the same data to the app, the web portal and your product.
Chargers348 brands
Two ProEve Single ProPulsar MaxPlugchoice
OCPP proxyREST APIWeb portalAppBack offices300+
Energy, booking and automation45
Energy management23Credit aggregators10Automation12Your productREST API
- Uptime and incidentson a public status page
- DIN ISO/IEC 27001:2022certified data centres in the EU, audited every year
- Automated backupsThe platform database is backed up automatically.
- Messages loggedexportable while we hold them, with the back office that answered
- Buffered when a back office dropsheld and replayed when it reconnects
- Service levelsunder a separate agreement
Start in the web portal
Create a free account, point a charger at wss://ocpp.plugchoice.com and it appears in the portal.
Charging at home? Get the app.