Roaming and integrations
One roaming connection. Your systems in the loop.
Your eMSP connects to Getz Hub once over OCPI, instead of building an integration per operator. Operators that agree terms with you appear to your drivers. Your own systems hear about charging through signed webhooks.
White-label EMP architecture
Your brand’s app and back office run on the shared EMP platform. Charging networks come through Getz Hub; payments through your merchant accounts; your systems through signed webhooks.
The Getz EMP platform (Getz runs it)
Getz runs and updates the platform. On it, your own eMSP organisation: drivers, pricing, wallets and data kept separate from every other brand on the platform. One or more trading brands per organisation.
Use Tab to reach the diagram, then the arrow keys to move between parts.
Roaming through Getz Hub
What travels over the connection
OCPI 2.3.0 and 2.2.1
OCPI 2.3.0 is the main version; 2.2.1 is still accepted, so operators on either can reach your drivers.
Locations, tariffs, sessions in
Operators’ data arrives as read-only copies; the platform never edits it.
Tokens and requests out
Driver tokens and the driver’s start and stop requests, tracked until the operator answers; the operator’s charger carries them out.
Real-time authorisation
Every start is checked by your EMP on the spot: driver status, token and payment method.
Site access respected
The operator decides who may charge at its sites. Private sites stay out of your app, and a start the operator has not authorised is refused.
Onboarding
How your organisation joins Hub
Connecting to Hub does not by itself open every network: each operator agrees terms with you, and a start is tested on each network you intend to offer.
Step 1: Register
Enter Hub’s versions address and your registration token under Roaming → Hub connection; credentials are exchanged over OCPI.
Step 2: Agree terms
Roaming agreements are made on Hub. Only operators with an agreement appear to your drivers.
Step 3: Test a start on each network
With your team, a session is started and billed on each network you intend to offer, during testing.
Step 4: Watch freshness
The back office shows how fresh each partner’s data is and resyncs when needed.
Partner webhooks
Your systems hear about charging as it happens
Signed events into your fleet, telematics, CRM or finance systems, per event type.
Per event type
Subscribe to the events you need, optionally for one fleet only.
Signed, retried, logged
Signed deliveries, retries with backoff and a delivery log with a test event.
Finance export
Every charge, payment and refund in a period as a CSV.
Integration details
How webhook deliveries behave
What your engineers need before building a receiver.
| Capability | How it works |
|---|---|
| Signature | An X-Getz-Signature header: an HMAC-SHA256 of the timestamp and the raw body, signed with your endpoint’s secret. Reject signatures older than five minutes. |
| Event identity | Every event has an id (also sent as X-Getz-Event-Id) that stays the same on every retry and redelivery, so your receiver can drop duplicates. |
| Event types | Sessions started and completed, charges rated, paid and failed, refunds, token changes and low driver wallets |
| Retries | Only a 2xx answer counts as delivered. Up to eight attempts, waiting 30 seconds and doubling each time (capped at six hours), with a 10-second timeout per attempt. |
| Failing endpoints | After 20 failed attempts in a row the endpoint is switched off and its pending deliveries are cancelled; any success resets the count. |
| Recovery and reconciliation | A delivery log with every attempt, its status and response; redeliver any delivery once your endpoint is fixed, and send a test event from the back office. |
Be precise
Real-time authorisation needs the platform to be reachable
Because every start is checked live, a driver on your tokens cannot start while the EMP or Hub is unreachable. That protects you from unpaid sessions and lost cards being used. Starting when the platform is unreachable is coming soon.
We do not publish an API catalogue or an SDK for partners: integration starts with the events and systems you need.
- Every start authorised in real time
The support console: a driver’s tickets, sessions and payments in one place.
- What you see: tickets and one search for any record
- Why it matters: faster answers for drivers
Questions about roaming and integrations
Which charging networks will our drivers see?
Those connected to Getz Hub that agree terms with you. Operators join one by one, so we do not publish a coverage figure or name networks that are not connected.
Do Getz’s own products get better treatment on Hub?
Hub is run as a separate, neutral business with the same rules for every partner. Its built controls and the governance still being set up are described on the Getz Hub website.
Is there a public API?
Not as a published product. Your app uses the platform’s driver API, charging networks connect over OCPI through Hub, and your systems receive webhooks.
Map out your integrations
Tell us where your drivers charge and which systems need charging data.