Reach drivers beyond
your own network.
Use OCPI 2.2.1 to connect with roaming partners. Make your chargers available through other services, give your app users access to partner networks and share charger data with national access points.
Roaming as a CPO
Roaming as an eMSP
National access points
Roaming as a CPO
Roaming as an eMSP
National access points
Put charging data to work
beyond the dashboard.
Connect EOSVOLT with the reporting, fleet and customer systems you already use. Our Public API gives your applications access to charging resources and documented actions.
Charging data and resources
Your business systems
Custom integrations
Charging data and resources
Your business systems
Custom integrations
See what connected
charging makes possible.
EOSVOLT integrations already connect charging with parking, fleet operations and local billing, making charging part of a wider customer service.
Parking and charging
Link charging sessions with a parking system so customers receive the parking discounts associated with their charging activity.
Fleet operations
Bring live charging activity and energy data into a fleet company’s own dashboard, alongside the information it uses to run its vehicles.
Local payments and billing
Bring local payment services, utility reporting and automated tax invoicing into a charging operation built for its market.
Start building with
the Public API.
Give your development team a clear starting point, with API authentication, endpoints, request parameters and example responses documented in one reference. Test your integration in staging before connecting it to production.
Charging connected
to a wider
fleet ecosystem.
WHA Logistics Mobilix uses EOSVOLT for its commercial fleet charging service. Through Voltality VoltNet, its chargers connect with roaming and API services that support WHA’s branded app and access to live charging data.
Frequently asked questions
Can we connect our own payment provider?
We can review your payment provider and the payment methods your business needs. EOSVOLT can work with multiple connected gateways in a deployment, with a default provider selected for the account. Additional integrations can be considered as development work.
Does roaming give us access to every charging network?
Roaming gives you access to networks connected through your OCPI partners. The networks, services and data available depend on the roaming hubs or direct agreements you establish.
Can we keep our existing customer app?
We can review your application’s requirements against the EOSVOLT Public API and available integrations, and help you plan an approach that supports the customer journey you want to offer.
Are all integrations included by default?
Your integration setup depends on the services your business uses, the modules selected for your account and any necessary agreements with third-party providers.
Can our developers test before going live?
Yes. The Public API has separate staging and production environments, with documented versioned routes to help you develop and test integrations.
Who connects the payment terminal to EOSVOLT?
The EOSVOLT team adds and links the payment terminal to your account. Share the terminal and the charging locations or chargers where it will be used, and we’ll handle the platform setup.
Explore the platform
behind the connections.
Pricing and payments
Configure charging prices, collect payments, and follow the records behind every transaction. Support different customer groups and billing arrangements across your operation.
Supported hardware
Connect supported AC and DC chargers over OCPP, and manage monitoring, remote commands, and firmware for every model.
White label platform
Launch a branded EV charging experience with EOSVOLT behind it. Configure the app, payment setup, and connected services around your customers and the way your business operates.