Skip to main content
Getz Hub

For EV charging and fleet apps

Connect once, then agree roaming with each operator

Connect to Hub once as an eMSP, then propose roaming agreements to participating operators. Each operator approves its own agreement. Tokens, sessions, commands and charge records then travel through that one OCPI connection.

Roaming agreements: which partners roam together, for which OCPI modules, from when. Synthetic demo data.

  1. An agreement routes only once both sides accept the same revision

What connecting means for an app

One connection
then an agreement with each participating operator you roam with
Start · stop · results
remote commands routed and results relayed back
Checked records
mismatches held before they reach you
Same terms
as Getz’s own driver app

Coverage

Find operators, propose agreements, start roaming

Find the operators connected to Hub in the partner directory and propose an agreement for the modules you need. Once the operator accepts, its locations, tariffs and live availability reach your app, translated to your OCPI version, and every message between you is routed and recorded, as in the routing history shown here.

An illustration: a driver planning Johannesburg to Cape Town finds, in your app, the chargers of the operators you roam with. Which South African operators you can reach depends on who is connected and agrees; ask us before you plan a launch.

  • Agreements per operator and module, with start and end dates
  • Push your tokens, or let operators authorise in real time

Every message the Hub routed, with where it came from, where it went and why. Synthetic demo data.

  1. What you see: routing decisions for one demo partner, by module and outcome
  2. Why it matters: any delivery can be traced back to the decision behind it

A roamed session

A roaming transaction, end to end

Follow one roamed charging session through Hub, message by message.

Illustration

One roamed charging session, end to end

A driver of one app charges at another operator’s charger. Follow the OCPI messages through Hub.

The CPO publishes its location and tariff

The CPO pushes locations and tariffs once. Hub delivers them to each app it has a roaming agreement with, if the CPO’s visibility rules allow that app to see the location.

Illustration of the OCPI message flow through Hub. It shows how Hub routes messages; it is not a live simulation and does not show the app’s own driver pricing, which happens after Hub.

When a charge does not go to plan

A good start, a failed start and a held record

What your driver sees, what your app receives and can do, and when to involve the Hub team. Based on how Hub routes commands and checks charge records today.

  • The charge starts

    START_SESSION → ACCEPTED → result ACCEPTED

    What the driver sees
    The session appears in your app and updates while the car charges.
    What your app receives and can do
    Hub relays the operator’s acknowledgement, then its result to your response_url. Session updates arrive for your driver only; the charge record follows once it passes the tariff check.
    When to contact Hub
    Nothing to do.
  • The start fails or times out

    REJECTED · result FAILED (e.g. EVSE_OCCUPIED) · TIMEOUT after 30 s

    What the driver sees
    Whatever your app shows: for example, that the charger did not start and which connector to try instead.
    What your app receives and can do
    Read the reason. A refusal by Hub says “Not routed” with the check that failed (no agreement in force, location not visible to you, operator offline). An operator’s failure comes back as its own result, unchanged. With no result within 30 seconds, Hub sends TIMEOUT to your response_url with your correlation ID; the charger may still have acted, so check your sessions feed before retrying. Hub never repeats a start for you, and tells you the result once.
    When to contact Hub
    Find the command in your partner portal by its correlation ID: it shows the reason in words, the operator’s own answer, the location, EVSE and session, and what to do next. If Hub refused a route you believe is agreed, e-mail support@getzcharging.com with that correlation ID; Hub support finds the command by it.
  • The charge record is held

    CDR re-priced → mismatch → held

    What the driver sees
    The session has ended in your app; the final amount waits until the record is decided.
    What your app receives and can do
    Your partner portal lists the charge records for your drivers that Hub held, released or rejected, with the session ID, operator, verdict and the difference. Do not bill the driver until the record is released: a released record reaches you as normal; a rejected one never does, and the operator sends a correction under a new record id. Only Hub finance staff release or reject, with a reason. If your platform offers the optional Getz assurance module, each decision also reaches you as an OCPI notice.
    When to contact Hub
    If a record stays held past your settlement window, or a completed session shows no record at all, e-mail support@getzcharging.com with the session ID and correlation ID.

What your product team gets

Built for the app side of roaming

  • Your own pricing

    You set the driver price. Hub passes the operator’s tariff and never touches your markup.

  • Autocharge vehicle IDs

    A car’s vehicle ID roams as an ordinary token. If two apps claim the same ID, Hub refuses to guess.

  • Self-service operations

    See your deliveries and connection health, and retry failures yourself.

Your path

From enquiry to your first roamed session

  1. Step 1: Enquiry

    Tell us about your app, its OCPI version and your markets.

  2. Step 2: Onboarding

    Register your eMSP party and complete the credentials handshake from your back office.

  3. Step 3: Agreements

    Propose agreements to operators in the partner directory.

  4. Step 4: Live roaming

    Your drivers charge on partner networks while both sides watch deliveries and assurance results.

Questions apps ask

Before you connect

Who pays the per-session fee?

The party that starts the roamed session pays it, usually the app, above a free monthly allowance. Getz’s own apps are quoted under the same model; one published price list is coming soon. Your quote states which sessions count, including failed starts, retries and test traffic. Request a quote.

How do we investigate a failed charge?

A refused start carries its reason in the OCPI response, an operator’s failure comes back as its own result and a missing result becomes TIMEOUT after 30 seconds. Your partner portal finds each command by its correlation ID, with the reason in words, the operator’s own answer and what to do next; deliveries show their correlation ID too. If Hub is involved, send that ID to support@getzcharging.com. See the three outcomes.

What if Hub cannot be reached when a driver wants to charge?

Starting a roamed session uses real-time authorisation through your app and Hub, which protects you from unpaid sessions. Charging that starts when either is unreachable is coming soon.

We are building on Getz EMP. Do we get better terms?

No. Apps built on Getz EMP connect on the same terms as any other app. There are no forced bundles and no preferential routing.

Who approves a roaming agreement?

You propose an agreement to an operator for the modules you need; the operator accepts or counters. Nothing flows until both sides accept the same revision, and either side can end it. Roaming agreements.

What does our engineering team need to prepare?

Your eMSP party (country code and party ID), a public HTTPS versions URL and the modules you plan to use. The technical integration page lists the prerequisites and the module table by OCPI version.

We only need charger locations for a map. Is this the right page?

Probably not. If you do not start sessions, the read-only charging data API or a data feed serves public locations, availability and tariffs without a roaming connection.

We are building for a car brand. Which route fits?

Compare the owner-app, in-car data and dealer options on the automotive page.

Enquiry

Discuss roaming integration

What happens next

Tell us about your app and the markets you serve. We reply by e-mail.

Driver apps, fleet tools, employer schemes and white-label apps all connect the same way, as eMSPs.

Fields marked with an asterisk are required.

Hub translates between versions, so any of these can connect.

Optional. Helps us route your enquiry to the right person.