Skip to main content
Getz Hub

Data feeds and integrations

The public charging catalogue, in the format you use

Choose how to receive the public charging catalogue: OCPI push or pull, GeoJSON, or signed webhooks. Hub sends what changed since your last acknowledgement, withdraws locations that stop being public, and sends a full snapshot every day.

Every feed delivery is logged: snapshot or changes, what was sent and withdrawn, and whether the receiver accepted it. Synthetic demo data.

  1. Delivery status and latency per feed
  2. Each delivery: mode, items changed and withdrawn, status and attempts

The challenge

Polling is not a data strategy

In-car and map systems need current data in their own format, without hammering an API.

  • Format conversion

    Every consumer wants a different shape of the same data.

  • Missed withdrawals

    Sites that close or go private linger in downstream maps.

  • Drift

    Without periodic full snapshots, small errors accumulate.

How it works

How feeds work

  1. Step 1: Choose a channel

    OCPI push to your Locations and Tariffs receiver, OCPI pull, GeoJSON (RFC 7946) or Standard Webhooks events.

  2. Step 2: Receive deltas

    Hub sends what changed since your last acknowledgement, and withdraws a location that stops being public.

  3. Step 3: Daily snapshot

    A full snapshot every 24 hours keeps your copy aligned.

  4. Step 4: Retries and signing

    Requests are signed with HMAC-SHA256 and retried with back-off; a permanent rejection stops the feed for review.

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": "ZW*DCZ:e19e492e-a4d2-440f-a1f1-5d367e67a659",
      "geometry": {
        "type": "Point",
        "coordinates": [
          31.096,
          -17.7581
        ]
      },
      "properties": {
        "kind": "location",
        "id": "e19e492e-a4d2-440f-a1f1-5d367e67a659",
        "operator": "ZW*DCZ",
        "name": "Demo Centre – Borrowdale",
        "address": "8 Demo Road, Borrowdale",
        "city": "Harare",
        "country": "ZWE",
        "timeZone": "Africa/Harare",
        "evses": [
          {
            "uid": "DEMO-BRW-AC01-E1",
            "evseId": "DEMO-BRW-AC01-E1",
            "status": "UNKNOWN",
            "lastUpdated": "2026-11-18T15:47:04.379Z",
            "connectors": [
              {
                "id": "1",
                "standard": "IEC_62196_T2",
                "format": "SOCKET",
                "powerType": "AC_3_PHASE",
                "maxPowerW": 22000,
                "tariffIds": [
                  "f3c44ea1-4699-4b3d-8176-45e5e7e9d492"
                ]
              }
            ]
          }
        ],
        "lastUpdated": "2026-11-18T15:47:05.538Z"
      }
    }
  ],
  "tariffs": [
    {
      "id": "f3c44ea1-4699-4b3d-8176-45e5e7e9d492",
      "operator": "ZW*DCZ",
      "currency": "USD",
      "elements": [
        {
          "price_components": [
            {
              "vat": 15.5,
              "type": "ENERGY",
              "price": 0.39,
              "step_size": 1
            }
          ]
        }
      ],
      "lastUpdated": "2026-11-17T20:14:40.793Z"
    }
  ],
  "removed": [],
  "removed_tariffs": []
}
Synthetic demo data. The EVSE status is UNKNOWN because the demo charger was offline when the snapshot ran. A delta has the same shape with mode “delta”, and lists withdrawn location and tariff ids in removed and removed_tariffs. Each request is signed (webhook-id, webhook-timestamp and webhook-signature headers).

Capabilities

Feed channels

  • OCPI push

    To your OCPI 2.1.1, 2.2.1 or 2.3.0 Locations and Tariffs receiver.

  • OCPI pull

    An OCPI sender interface you query for public locations and tariffs.

  • GeoJSON

    Snapshot and delta feeds in standard GeoJSON for map systems.

  • Signed webhooks

    Events following the Standard Webhooks convention, signed per request.

Questions

Data feeds and integrations: questions

Feed or API: which do we need?

Use the read API to query on demand, for example when a driver opens a map. Use a feed when your system keeps its own copy of the catalogue and needs every change, including withdrawals, plus a daily snapshot to stay aligned.

Can we see what a feed delivers before we commit?

The sample on this page is an excerpt of a real GeoJSON snapshot made with demo data. For the OCPI or webhook channels, tell us which one you would use in your enquiry and we will go through an example with your team. Feeds carry only public locations, their availability and their tariffs.

Can a map provider pass the data on to others?

Onward distribution is set in your data agreement. Tell us who would receive the data when you enquire.

Can a feed include private locations?

No. Feeds carry only locations published as public, and a location that stops being public is withdrawn from every feed.

How are credentials for our endpoint handled?

Credentials for your receiving endpoint are held as deployment secrets referenced by the feed configuration, never stored in the database. Until they are set, the feed stays blocked rather than sending unauthenticated.

Get charging data in your format

Tell us which channel and format you need, and how you will use the data.