Custom EV Charging APIs and Integration
If your application needs something out of a charging network, or needs to do something to it, we build that interface and our team integrates it with yours. What it exposes is decided by what you are building, not by what a standard API happened to include.
What operators and product teams usually need, how we design and build it around that, what the integration work looks like with our software delivery centre alongside your team, and how to start.
Talk to Our Integration TeamFor A product team that needs charging inside an application of their own, and does not want to become experts in charging protocols to get there.
What people usually need
The request is almost never for a charging API in the abstract. It is for one specific thing to appear in, or be controlled from, an application that already exists.
- 1
Energy and session information
What was delivered, when, on which unit, at what cost. Into a billing system, a sustainability report, an ERP, a customer portal.
- 2
User and driver information
Who charged, their history, their spend, their entitlement, so an application can recognise its own users at a charger.
- 3
Charger and site state
What is available, what is in use, what is faulted, so it can be shown wherever your users already look.
- 4
Control
Starting and stopping a session, applying a limit, taking a unit out of service, from inside your own product.
- 5
Something none of the above covers
Which happens often, and is the reason we design these rather than publish one and hope it fits.
How we build it
- 1
We start from your requirement
What your application needs to do, who its users are, and where charging has to appear in it. The interface is designed backwards from that.
- 2
We build the interface
Onto the charging platform, shaped for your use, rather than handing you a generic surface and leaving you to work out which parts matter.
- 3
We integrate it with you
Our software delivery centre works alongside your team through the integration, so the work of connecting it is not left on your side of the line.
- 4
We stay through what comes after
Charging hardware in a car park behaves in ways a test environment does not, and the useful support is the kind that is still there in month three.
Working against third-party applications is the normal case rather than the exception. Most of what we integrate with was not built with charging in mind.
Why it is built rather than bought
- 1
A published API is somebody else's guess
It contains what its author expected people to want. The gap between that and what you need is work that lands on your team.
- 2
Your data model is not ours
An interface designed around how your application already thinks is a smaller integration than one that makes you translate on every call.
- 3
Scope is a decision
What is exposed, to whom, and what can be acted on, settled deliberately for your case.
- 4
It can change when you do
The second version of an integration is usually the one that matters, and it is far easier when the interface was built for you in the first place.
Want this applied to your own site?
Talk to Our Integration TeamTechnically reviewed by Deepu Joy, Director of Products and Delivery. Last reviewed 2026-09-10.
Frequently asked questions
Do you have a public API we can read?
Not today. Tell us what you are building instead. We design the interface around your requirement, because a published surface is always another team's guess at what people want and the gap between that and your case becomes work on your side.
Can you integrate with our existing application?
Yes, and that is the normal case. Most of what we connect charging to was not built with charging in mind.
What can it cover?
Energy and session information, driver and user information, charger and site state, and control such as starting or stopping a session or applying a limit. If you need something outside that, say so, because the list is not the boundary.
Who does the integration work?
Our software delivery centre, working alongside your team. The connecting work does not get left on your side of the line.
How do we start?
Tell us what your application does and where charging has to appear in it. That conversation is usually enough to scope the interface.
Need charging inside an application of your own?
Tell us what you are building and what it has to get from the chargers. We will come back with what the interface looks like and what the integration involves.
Talk to Our Integration Team