Skip to main content
Getz Hub

Charging data API

Public charging data through one read-only API

Navigation apps, in-car systems, fleet tools and insurers can read public charging locations, live availability and tariffs through scoped, rate-limited keys. Only locations that operators publish as public are ever served.

Scoped, rate-limited keys for the read-only public API. Synthetic demo data: limits shown are examples, not a standard plan.

  1. Scopes: locations, tariffs, availability
  2. The key is shown once; only its hash is stored

The challenge

Charging data is scattered

Anyone who needs a complete picture of public charging has to scrape apps or sign separate data deals with each operator.

  • One deal per operator

    Each network has its own format, terms and update frequency.

  • Stale availability

    Static lists say nothing about whether a charger is free or working.

  • Unclear permission

    Data copied from apps comes with no clear right to use it.

How it works

How access works

  1. Step 1: Agree a plan

    Scope (locations, availability, tariffs) and rate limit are agreed with you. Pricing on request.

  2. Step 2: Receive a key

    Hub staff issue a key with your scopes and limit. It is shown once and stored only as a hash.

  3. Step 3: Read public data

    Query public locations, live availability and tariffs. Locations a CPO does not publish as public are never served.

  4. Step 4: Usage is metered

    Requests are metered per key and hour, by channel, and can be exported.

Sample response

What the read API returns

Excerpts of real responses from Hub’s read API, captured with the fictional demo dataset: one public location (trimmed to one EVSE), its live status and the tariff it references, with currency and VAT.

{
  "location": {
    "id": "df97940b-3c79-4d0e-86ac-a5fce4443325",
    "operator": "ZA*DMO",
    "name": "Demo Mall – Rosebank",
    "address": "50 Demo Avenue, Rosebank",
    "city": "Johannesburg",
    "country": "ZAF",
    "coordinates": {
      "latitude": "-26.145700",
      "longitude": "28.041600"
    },
    "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"
  },
  "availability": {
    "locationId": "df97940b-3c79-4d0e-86ac-a5fce4443325",
    "operator": "ZA*DMO",
    "lastUpdated": "2026-11-18T15:47:06.580Z",
    "evses": [
      {
        "uid": "DEMO-RSB-AC01-E1",
        "evseId": "DEMO-RSB-AC01-E1",
        "status": "UNKNOWN",
        "lastUpdated": "2026-11-18T15:47:02.119Z"
      }
    ]
  },
  "tariff": {
    "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"
  }
}
Synthetic demo data. Each key returns only the scopes it holds (locations, availability, tariffs). The EVSE status is UNKNOWN because the demo charger was offline. Coordinates and timestamps are as the operator published them; the full interface reference comes with your key.

Capabilities

What the API offers

Read-only access to the public charging data operators publish through Hub.

  • Scoped keys

    Each key carries its own scopes and rate limit and can be edited or revoked.

  • Live availability

    EVSE status from connected operators, for locations they publish as public.

  • Tariffs

    The tariffs referenced by public locations.

  • Usage metering

    Hourly usage per key, split by channel and exportable.

In the product

Usage metering per key

Requests by hour and by endpoint, for every key. Figures shown are demo values, not a service measure. Captured with synthetic demonstration data.

Coming soon

Public charging data on your own website.

  • Coming soon

    A hosted "chargers near you" map widget for partner websites

    Drop in a map of public chargers, with no map hosting of your own.

Questions

Charging data API: questions

How do we get the API reference?

Each data customer receives the interface reference with its key, and our engineers walk your team through it. The sample on this page shows what responses look like.

Is there an example of the data?

Yes: the sample on this page shows real read-API responses made with demo data (a location, its live status and its tariff, with currency and VAT). The data feeds page shows the GeoJSON feed equivalent. The full interface reference comes with your key.

What may we do with the data?

Permitted use, attribution and how long you may keep copies are set in your data agreement. Tell us your intended use when you enquire.

How does an operator keep a site out of the API?

By not publishing it as public: the API serves only locations operators publish as public, and an unpublished location stops being served. Visibility and privacy controls.

We need to start and stop sessions. Is this the right API?

No. The data API is read-only. Starting sessions, sessions and charge records go through an OCPI roaming connection: see technical integration and EV charging apps.

Do you include charger reliability scores?

Not through Hub today. Hub serves the locations, availability and tariffs operators publish as public.

What does API access cost?

Data plans are priced by scope and rate limit. Pricing on request. See the pricing model.

Explore API access

Tell us what data you need and how you will use it. We reply by e-mail.