The API-First Infrastructure For EV Charging
Designed for engineers, eMabler's APIs connect charging to the systems you already run, giving your team the freedom, speed, and control to build only what you need and when you need it.
GET /v1/charging-sessions/sess_8f21
{
"id": "sess_8f21",
"status": "completed",
"energy_kwh": 42.6,
"charge_point": "cp_a1b2c3",
"success": true
}
Built for integration from day one
eMabler provides two open APIs that work together: a REST API for the calls you make, and a Push API for the events we stream to you. Both are fully documented, versioned, and proven in production across millions of charging sessions, so you can build charging into your own product fast and trust it to stay stable as you scale.
Read, write, configure
REST gives you full programmatic access to the whole platform: chargers and sites, sessions, tariffs and pricing, RFIDs and users, energy management, and data export. Start or stop a session, reconfigure a connector, or pull a month of history in one call, then automate the workflows your operation runs on. The contract is versioned and backward-compatible, so what you ship today keeps working tomorrow.
- Read, write, and configure across the platform
- Build custom workflows and automate operations
- Versioned and stable as the platform evolves
GET /v1/charge-points/cp_a1b2c3
{
"status": "available",
"connector": "Type 2",
"firmware": "3.4.1",
"online": true
}Real-time event streaming
Subscribe once and eMabler streams charging events to your endpoint the moment they happen, over webhooks, Kafka, Azure Service Bus, or AWS SNS. Your systems react in real time and never have to poll, so live status, transactions, and meter values reach your stack as fast as they change.
- Transactions, charger status, meter values, and entity changes
- Real-time streaming with no polling
- Feeds your CRM, billing, and energy systems
POST /webhooks/emabler
{
"event": "session.completed",
"session_id": "sess_8f21",
"energy_kwh": 42.6,
"success": true
}eMabler's APIs are well designed and clearly documented, which made the integration straightforward for our team.”
300+ integrations you don't have to build
Payments, billing, energy management, roaming, fleet, CRM and ERP: the connectors are already built. Pick what you need, plug it into the systems you already use, and go live without months of custom work.
Every integration runs on documented, stable APIs already in production. We own the architecture, the delivery, and the maintenance, so connections don't break as you scale. Don't see what you need? Get in touch. We build custom integrations too.
PaymentsIncluding: Apple Pay, Google Pay, Vipps, MobilePay, Credit cards
Including: Apple Pay, Google Pay, Vipps, MobilePay, Credit cards
Take ad hoc payments right at the charger with cards, mobile wallets, and payment terminals, so any driver can charge and pay without an app or an account.
RoamingIncluding: Hubject, Gireve, Plugsurfing, Enapi
Including: Hubject, Gireve, Plugsurfing, Enapi
Open your network to roaming partners and give your drivers access to hundreds of thousands of charge points across Europe, with sessions and CDRs exchanged over OCPI.
Energy managementIncluding: Octopus Energy, Emulate, Enico
Including: Octopus Energy, Emulate, Enico
Shift charging to cheaper, greener hours with spot-price and virtual-power-plant integrations, and balance load across a site with dynamic load management.
Business systemsIncluding: Salesforce, Hansen, Utility Cloud
Including: Salesforce, Hansen, Utility Cloud
Push live sessions, charger status, and invoices into the CRM, ERP, and billing systems you already run, so charging data shows up where your teams work.
Fleet & leasingIncluding: Ayvens, NF Fleet, TandemDrive
Including: Ayvens, NF Fleet, TandemDrive
Send charging sessions to fleet and leasing platforms for automated home-charging reimbursement, cost control, and per-driver reporting.
Custom APIBuild exactly what you need
Build exactly what you need
Not in the library yet? Build it yourself on the documented REST and Push APIs, or we build the connector with you.
Charging built into the app your customers already use
Your customers already have an app for fuel, parking, loyalty, or energy. eMabler's APIs let you add EV charging right into it: start and stop sessions, show live status, take payment and issue receipts, without sending anyone to a separate app.
Everything runs under your brand and your UX. You own the experience end to end, the data flows straight into your systems, and drivers never leave the product they already trust.
- Your brand and UX: Your colors, your flows, your design system, not ours.
- Native in your existing app: Ship charging as a feature, not a second app to download.
- Drivers never leave your product: One login, one wallet, one place for every service you offer.
eMabler allows us to keep charging as part of the Neste experience. We manage the customer relationship through our own app, retain ownership of customer data, and have the flexibility to expand our charging services as our needs evolve.”
What you can build
Expand your charging offer and launch new services on infrastructure you control, while keeping full ownership of your data, sessions, and customers. Use only the endpoints you need, connect them to your existing ERP, CRM, fleet, and go live in weeks.
Build on top of the platform
Add the workflows and logic your business needs on top of eMabler, beyond any prebuilt module.
Integrate with your stack
Move charging data both ways between eMabler and the ERP, CRM, fleet, and identity systems you already run.
Own your data
Keep full control of your charging data, sessions, users, transactions, and vehicles, and export it anywhere.
Automate your operations
Run bulk changes, scheduled jobs, and event-driven workflows through code, with no manual dashboard work.
Build on open standards
Speak OCPP and OCPI so charging fits the same protocols as the rest of your infrastructure.
Scale on one API
Grow from a pilot to thousands of charge points on the same endpoints and data model.
The eMabler developer hub
Comprehensive API documentation, guides, and references: everything your team needs to integrate with confidence, stay productive, and shorten time to market.
Everything you need to run and scale EV charging
The API is one part of a complete platform. Every module is production-proven at network scale and reachable through the same open API. When you would rather not run it yourself, our managed services team runs it for you.
Keep your network reliable and cost-efficient, from one charger to thousands.
Flexible pricing that adapts rates to capture more value.
Real-time dashboards across your entire charging operation.
AI-powered monitoring that fixes common issues automatically.
Load balancing and price adaptation that turn energy into revenue.
One-time payments so anyone can charge without an account.
Make your chargers visible across roaming hubs and partner platforms.
We run your charging network so you can run your business.
Common questions about the eMabler API
What kind of API does eMabler offer?
eMabler offers two open APIs that work together: a REST API and a Push API. The REST API handles on-demand requests such as charge points, sessions, tariffs, and billing, and the Push API streams events the moment they happen, over webhooks, Kafka, Azure Service Bus, or AWS SNS. Use one or both to build EV charging into your own product.
Is the API stable as the platform evolves?
Yes. eMabler's REST API is versioned and backward-compatible, so it stays stable as the platform changes underneath it. An integration you ship today keeps working tomorrow.
Can I build charging into my own app?
Yes. You can embed EV charging directly in your own app or portal as a white-label experience, so drivers start sessions, check live status, and pay without ever leaving your product. Everything the platform does is available through the API.
Does eMabler work with my existing chargers and systems?
Yes. eMabler is hardware-agnostic and works with any OCPP-compliant charger, on OCPP 1.6 and 2.0.1. Through the open API and 300+ ready integrations, you can connect charging to the CRM, ERP, billing, and energy systems you already run, and exchange sessions with roaming networks over OCPI.
How long does an eMabler integration take?
Most integrations go live in 2 to 4 weeks. Pre-built connectors cover the major CRM, ERP, and billing systems, and self-service API keys with a test environment let you start building in a few days.
Where do I find eMabler's API documentation?
Full documentation for the REST and Push APIs lives at docs.emabler.com, with OpenAPI references, guides, and an interactive try-it-out. Start with the getting-started guide, or open the eMabler developer hub for everything in one place.