For charging data and API access
Public charging data, with clear permission to use it
Navigation apps, in-car systems, insurers, fuel apps and fleet tools read public locations, live availability and tariffs through a scoped key or a feed in the format they use.
Every feed delivery is logged: snapshot or changes, what was sent and withdrawn, and whether the receiver accepted it. Synthetic demo data.
- Delivery status and latency per feed
- Each delivery: mode, items changed and withdrawn, status and attempts
Data scope
What you can read, and what is never shared
Only what operators publish as public. Each scope is a separate permission on your key.
| Capability | Read API and feeds | Notes |
|---|---|---|
| Charging locations and connectors | Yes | Locations published as public only |
| Live availability | Yes | Separate scope |
| Tariffs | Yes | Separate scope |
| Private, fleet and home locations | No | Never served |
| Sessions, charge records and driver tokens | No | Never part of data products |
| Reliability or uptime history | No | Not offered today |
Delivery
In the format your system already reads
Read API
Scoped, rate-limited, read-only keys, shown once when issued.
OCPI feed
For systems that already speak OCPI.
GeoJSON
For maps and GIS tools.
Signed webhooks
Deltas pushed as they happen, plus a daily full snapshot.
Sample delivery
What a GeoJSON feed delivers
An excerpt of a real snapshot from Hub’s GeoJSON feed, captured with the fictional demo dataset: one public location with one of its EVSEs, and the tariff it references.
{
"type": "FeatureCollection",
"mode": "snapshot",
"generated_at": "2026-11-21T17:50:08.745Z",
"features": [
{
"type": "Feature",
"id": "ZA*DMO:df97940b-3c79-4d0e-86ac-a5fce4443325",
"geometry": {
"type": "Point",
"coordinates": [
28.0416,
-26.1457
]
},
"properties": {
"kind": "location",
"id": "df97940b-3c79-4d0e-86ac-a5fce4443325",
"operator": "ZA*DMO",
"name": "Demo Mall – Rosebank",
"address": "50 Demo Avenue, Rosebank",
"city": "Johannesburg",
"country": "ZAF",
"timeZone": "Africa/Johannesburg",
"evses": [
{
"uid": "DEMO-RSB-AC01-E1",
"evseId": "DEMO-RSB-AC01-E1",
"status": "UNKNOWN",
"lastUpdated": "2026-11-18T15:47:02.119Z",
"connectors": [
{
"id": "1",
"standard": "IEC_62196_T2",
"format": "SOCKET",
"powerType": "AC_3_PHASE",
"maxPowerW": 22000,
"tariffIds": [
"550c0a72-4013-45bb-b108-fe092eff67ae"
]
}
]
}
],
"lastUpdated": "2026-11-18T15:47:06.580Z"
}
}
],
"tariffs": [
{
"id": "550c0a72-4013-45bb-b108-fe092eff67ae",
"operator": "ZA*DMO",
"currency": "ZAR",
"elements": [
{
"price_components": [
{
"vat": 15,
"type": "ENERGY",
"price": 5.65,
"step_size": 1
},
{
"vat": 15,
"type": "PARKING_TIME",
"price": 30,
"step_size": 60
}
]
}
],
"lastUpdated": "2026-11-15T13:43:30.982Z"
}
],
"removed": [],
"removed_tariffs": []
}Keys and metering
Usage you and we can both see
Each key carries its own scopes and rate limit. Requests are metered per key and hour, so any conversation about usage starts from the same numbers. Data plans are priced by scope and rate limit, on request.
Scoped, rate-limited keys for the read-only public API. Synthetic demo data: limits shown are examples, not a standard plan.
- Scopes: locations, tariffs, availability
- The key is shown once; only its hash is stored
Questions
For data teams
How many chargers does the data cover?
Only those of operators connected to Hub that publish them as public. We do not quote coverage figures before they exist; ask us for the current picture.
Is there reliability or uptime data?
Not through Hub today. Hub serves locations, live availability and tariffs.
How do we get the API reference?
Every data customer receives the interface reference with its key. To evaluate first, the sample on this page shows a real GeoJSON feed excerpt made with demo data; if you need more example fields, say so in your enquiry.
What may we do with the data?
Permitted use, attribution and how long you may keep copies are set in your data agreement; no standard terms are published yet. Ask for the data terms with your intended use, before you integrate.
What happens when an operator withdraws a site?
A location that stops being public is no longer served by the read API, and every feed receives a withdrawal for it. Your agreement sets how quickly your own copies must follow. Data feeds.
How current is the data?
Live availability comes from the status updates connected operators send. Feeds carry each change since your last acknowledgement plus a full snapshot every 24 hours. Ask us about the update frequency your use case needs.
Do we need a roaming agreement to use the data?
No. A data key covers public locations only, under your data plan. Roaming agreements are for partners that exchange sessions and charge records over OCPI. If you need to start charging sessions, see EV charging apps.
Enquiry
Explore API access
What happens next
Tell us which data you need and how you will use it. We reply by e-mail.
Every key is scoped and rate-limited, and only locations operators publish as public are served.