EV Charging API and Webhooks
The EV charging software API for building your own apps and connecting your business systems to YoCharge.
YoCharge runs charging networks for 100+ CPO partners in 25+ countries. The same platform is open to your developers: a REST API for custom integrations and webhooks that notify your systems when something happens. Use it to put charging inside your own app, sync your ERP and billing tools, or build products we haven’t thought of.
- REST API
- Webhooks
- Developer mode
- OCPI 2.2.1 roaming
What the YoCharge API is for
The platform already handles chargers, sessions, drivers, tariffs and payments. The API lets your own software work with it, so you don’t rebuild what’s already running.
Your own driver app: add charging to the mobile app you already have, instead of sending drivers to a second app.
ERP integration and billing: connect YoCharge to your ERP, billing and loyalty systems, so charging data reaches the tools your finance and operations teams use.
Custom applications: build internal tools, partner portals or new services on top of the platform.
Webhooks: instead of polling, your systems are notified when events happen on the platform, and act on them straight away.
What do you want to build?
Pick the route that matches your project:
Charging inside my existing app the Charging API, with developer mode on the White-label Business plan.
My own branded charging apps, without coding them the white-label Android and iOS apps.
Charging on other operators’ networks for my drivers our eMSP product, white-label or API-based.
Data flowing into my ERP, billing or loyalty tools the REST API and webhooks.
The platform on my own servers White-label Enterprise.
Developer mode on the White-label plans
Developer mode is how white-label customers build their own applications on YoCharge.
| White-label plan | What you get |
|---|---|
| White-label Starter | White-label platform and web app for walk-in charging; OCPI integration for charging on third-party networks |
| White-label Business | Everything in Starter, plus your own white-label Android and iOS apps, or developer mode for building custom applications |
| White-label Enterprise | Everything in Business, plus custom deployment on your own servers |
Plans are quoted per region and scope. See plans and pricing
One platform, three ways to connect
Each part of a charging business talks to YoCharge over the interface built for it:
Chargers, over OCPP: OCPP 1.6J and 2.0.1 supported, and 2.1-ready, with 60+ charger brands running on the platform.
Other networks, over OCPI: OCPI 2.2.1 roaming, with OCPI integration in 3–7 business days.
Your own systems, over the REST API and webhooks: apps, ERP, billing and anything else you run.
Payments, invoices and tariffs set up on YoCharge stay in one place, whichever route the data takes. EV charging payments and billing
What’s in the API
One developer page for everything you connect to YoCharge. Here is what the API covers today:
REST API resources: stations and connectors, charging sessions, RFID and ID tags (create and disable), driver favourites and support tickets.
Signed webhooks: charging session started, session summary, meter value updates and charger status. Each call is signed with HMAC-SHA256, so you can check it came from YoCharge, and every delivery is logged.
API keys you control: your admin creates and revokes keys, and each request authenticates with its key.
Fair-use rate limits: limits apply per key, and every response carries rate-limit headers, so your code can pace itself.
An API reference: an OpenAPI reference for your account, shared on request or when your account is created.
How to get access
Book a demo: tell us what you want to build and which systems it has to connect to.
Get the API documentation: documentation is shared on request, or when your account is created.
Build: your developers work against the API under your plan.
Go live: your app or integration runs on the same platform as the rest of your network.
The platform runs on AWS, Google Cloud and Azure, across 6+ data centers, with 99%+ uptime.
Why an API strategy matters for a charging business: 3 key API strategies to expand an EV charging business
CPO partners
countries
charger brands
charging sessions
EV charging API: questions developers ask
What is an EV charging API?
An application programming interface that lets your own software work with a charging platform: reading charging data, starting actions and reacting to events. YoCharge offers a REST API with webhooks for custom integrations and ERP connections.
Does YoCharge have webhooks?
Yes. Webhooks notify your systems when events happen on the platform, so they don’t have to keep asking. The event list is in the API documentation.
Where is the API documentation?
It’s shared on request, or when your account is created. Book a demo or email sales@yocharge.com, and tell us what you plan to build.
Which plans include developer mode?
Developer mode comes with the White-label Business plan, as an alternative to the white-label apps, and with White-label Enterprise, which includes everything in Business.
Can I add charging to my existing mobile app?
Yes. That’s what the Charging API is for: integration with the app you already have, instead of a second app for your drivers.
Can I connect YoCharge to my ERP or billing system?
Yes. The REST API is built for custom integrations and ERP connections, and the platform also integrates third-party tools such as billing systems and loyalty programmes.
Is there an API for eMSPs?
Yes. Our eMSP product comes white-label or API-based, with OCPI 2.2.1 roaming and earlier OCPI versions.
Can I run the platform on my own servers?
Yes, on the White-label Enterprise plan, which adds custom deployment on your own servers.
Tell us what you want to build
Show us your app, your systems and your plans. We’ll walk you through the API and share the documentation.
Book a demoOr email sales@yocharge.com