OCPP API · BrandX, with your own app
Your app. Our charging engine.
Get the full BrandX suite in your brand: CMS, Fleet Charge, WhatsApp Charge and UPI Charge. Then build your own driver app on our backend APIs. Your drivers never leave your app.
01 · How it fits together
BrandX behind the scenes. Your app in front.
OCPP API is BrandX with one difference: instead of our white-labelled driver app, you build your own on our APIs. Your chargers connect only to your white-labelled platform, and everything else stays in your brand.
White-labelled by us
Your BrandX suite
Your network runs here, in your brand. Chargers connect here.
CMS · Fleet Charge · WhatsApp Charge · UPI Charge · Master Dashboard · Customer Support Portal
Built by you
Your own driver app, on our APIs
Charging lives inside the app you already have.
Find chargers · start and stop · live session · payments your way
02 · BrandX or BrandX + OCPP API
Same platform. You choose who builds the app.
| BrandX | BrandX + OCPP API | |
|---|---|---|
| CMS | White-labelled | White-labelled |
| Fleet Charge | White-labelled | White-labelled |
| WhatsApp and UPI Charge | White-labelled | White-labelled |
| Driver app | Ours, in your brand | Yours, built on our APIs |
| Chargers connect to | Your white-labelled platform | Your white-labelled platform |
Want us to build the app too? See BrandX →
03 · Who builds on it
For teams that want their own charging platform.
04 · What you can do
Full charging control, from your own code.
Start and stop sessions
Remotely, on any connector.
Live charger status
Availability, faults and connector state.
Session and energy data
kWh, duration and meter values for every session.
Configuration and resets
Change charger settings and reset remotely.
Firmware updates
Over the air.
Webhooks
Real-time events for sessions, status changes and faults.
05 · You build, we run
You own the experience. We handle the protocol.
You build
– Your driver app
– Your payment flow and pricing
– Your brand and user experience
– Or anything else you have in mind
We run
– Your white-labelled CMS, Fleet, WhatsApp and UPI Charge
– OCPP connectivity for every charger
– Uptime, scaling and protocol updates
06 · How it works
Live in three steps.
STEP 01
Set up your BrandX suite
CMS, Fleet, WhatsApp and UPI Charge, white-labelled in your brand.
STEP 02
Connect your chargers
Point them at your white-labelled platform's OCPP endpoint.
STEP 03
Build charging into your app
Call our APIs from your backend platform.
07 · For developers
Everything you need to start building.
API documentation
Endpoints, events and examples.
Sandbox
Test against a simulated charger.
Developer support
Help from the team that runs the platform.
08 · FAQ
Questions developers ask.
Is OCPP API part of BrandX?
Yes. It's BrandX for brands that want to build their own driver app. You still get the white-labelled CMS, Fleet Charge, WhatsApp Charge and UPI Charge.
Which OCPP versions are supported?
OCPP 1.6J and 2.0.1.
Do I need Plugzmart chargers?
No. Any OCPP-compliant charger works.
Is there a sandbox to test in?
Yes. Test against a simulated charger before you go live.