Autonomous Fleet Charging, Through One API
Your platform keeps routing and dispatch. We give it the charging network: find chargers across CPOs and regions, reserve a connector ahead of arrival if you choose, start the session without a driver, and settle with every CPO in one place. That’s charging orchestration for fleets that have no one behind the wheel.
REST API, available on request Global coverage through regional hubs
A driverless vehicle can’t hunt for a charger
Public charging was built around a person. Someone opens an app, drives around looking for a free connector, taps a card and pays. Take the driver away and every one of those steps has to happen in software, before the vehicle leaves its last job.
That’s the real problem in autonomous vehicle charging. Whether it’s a robotaxi, an autonomous delivery van or a driverless fleet shuttle, the fleet’s platform needs to know:
which chargers exist across networks, and which are free right now;
what each one costs;
whether a connector can be held until the vehicle gets there;
how the session will start with no one to tap a card;
how charges from many CPOs turn into one settlement.
Connecting to each CPO separately, in every region you operate, doesn’t scale. YoMobility, powered by YoHub, gives your platform all of it through one integration.
How it works: reserve, then charge
Two steps. The first is optional.
Step 1: Reserve a charger ahead of arrival (optional)
Your platform picks the charger and asks for a connector to be held for that vehicle. At supported charge points on YoHub, the connector is reserved for the vehicle’s token until it’s used, cancelled or expires. Your router adds the charging detour to the route. If the plan changes, update or cancel the reservation.
A reservation is an authorisation hold: the charger won’t start a session for anyone else’s token. It doesn’t physically keep the bay clear, so your platform should always have a fallback.
Step 2: Charge
When the vehicle arrives and is connected, the session starts without a driver. It’s authenticated by the reservation token, by a start command sent through the hub, or by the vehicle’s own identity where the charger supports it. Your platform follows the session until it ends. Every session then settles across CPOs in one place.
Or just charge
Reservation is optional. If your platform would rather send a vehicle straight to an available charger, skip step 1 and start the session on arrival.
You decide where to charge. We orchestrate the charge.
Your platform owns the allocation intelligence, routing and dispatch: which vehicle charges, when, and where, given its range, its next job and its route. We don’t second-guess it. YoMobility and YoHub give it the charging network, carry out its decisions at the charger, and report back.
What the EV charging API covers
One REST API, available on request, sits between your fleet platform and the charging networks. It covers five jobs:
Charger discovery
Charge point locations across connected CPOs and regions, with connector types, and which charge points accept reservations.
Availability and pricing
Current status and tariffs, so your platform can choose a charger before it commits the detour.
Reservation (optional)
Hold a connector ahead of arrival, then update or cancel the hold, at supported charge points on YoHub.
Session start and status
Start the session and follow it from start to finish.
Usage and settlement
A record of every session, settled across CPOs in one place, so each charge can be traced back to the vehicle.
When a charger says no. A charger can reject a reservation, be occupied or offline, or cancel a hold it accepted. A reserved bay can also be blocked. In each case the API tells your platform what happened, so it can pick another charger and re-plan the route.
Global coverage through regional hubs
YoHub runs six regional hubs: India (IN), Southeast Asia (SEA), the Middle East & North Africa (MENA), Australia & New Zealand (ANZ), Europe (EU) and North America (NA). Your platform integrates once and charges across networks in every region where you operate.
- IN hubIndia, Nepal, Bhutan, Sri Lanka, Maldives
- SEA hubIndonesia, Singapore, Malaysia, Thailand, Vietnam, Philippines
- MENA hubUAE, Saudi Arabia, Qatar, Oman, Egypt, Morocco
- ANZ hubAustralia, New Zealand, Fiji, Samoa
- EU hubIreland, UK, Netherlands, Germany, France, Spain, Italy
- NA hubUSA, Canada, Mexico, Colombia, Brazil, Chile
Where reservations work
Reservations are live at supported charge points on YoHub. On other networks, reservation availability depends on the partner hub or CPO. Where a charger can’t be reserved, your vehicles can still just charge.
Built on open standards
YoHub connects CPOs and hubs over OCPI 2.2.1, the open roaming protocol, so charge points from different networks look the same to your platform.
Works with your existing fleet stack
You don’t replace anything. The API sits beside the dispatch and routing systems you already run, and takes its instructions from them.
Many operators also run driver-led EVs. YoMobility’s EV fleet management software runs those vehicles, drivers and payments on one platform. Its charging management module lets a control room start, monitor and control sessions remotely across networks. Autonomous and driver-led vehicles can share the same charging layer.
Autonomous fleet charging: questions buyers ask
What is autonomous fleet charging orchestration?
It’s the layer between an autonomous fleet’s own platform and the charging networks. Your platform decides where and when each vehicle charges. YoMobility, powered by YoHub, finds the chargers, holds a connector if you want one, starts the session and settles with every CPO.
How do autonomous vehicles charge without a driver?
Every step a driver used to do happens in software. The session is authenticated by a reservation token, a start command sent through the hub, or the vehicle’s own identity where the charger supports it, so no one needs to tap a card or open an app.
Can it integrate with our routing and dispatch system?
Yes. Your platform integrates once through our REST API, which is available on request. It keeps allocation, routing and dispatch. We carry out the charging part of its decisions.
Do we have to reserve a charger?
No. Reservation is optional. You can reserve a connector ahead of arrival at supported charge points, or send the vehicle to charge without one.
Does a reservation keep the bay free?
It’s an authorisation hold, not a physical barrier: the charger won’t start for anyone else’s token. If a bay is blocked or a charger fails, your platform hears about it and can re-plan to another charger.
Where can we reserve a charger?
At supported charge points on YoHub. On other networks, reservations depend on the partner hub or CPO. You can always just charge.
Which regions do you cover?
Coverage is global, through six regional hubs: India (IN), Southeast Asia (SEA), the Middle East & North Africa (MENA), Australia & New Zealand (ANZ), Europe (EU) and North America (NA).
How is charging paid for across different CPOs?
Every session is recorded and settled across CPOs in one place, so you don’t reconcile a separate bill from each network.
Plan charging for your autonomous fleet
Tell us where your fleet runs and how your platform dispatches it. We’ll show you how it would discover, reserve and charge across networks, with one settlement.