For international roaming hubs
Peer with Hub for participating South African networks
Getz Hub peers with other roaming hubs as equals, so your partners’ drivers can roam onto participating networks here, and drivers here onto yours. What each side reaches depends on the peering scope and on agreements with each party.
How peering works
Peers are equals
Loop prevention
A message never returns to a party in its path, and Hub never re-publishes to the source.
At most four hub hops
Traffic crosses no more than four hubs between sender and receiver.
Any of three OCPI versions
Peer on 2.1.1, 2.2.1 or 2.3.0; Hub translates for its own partners.
What crosses a peering link
The same rules as any other partner
| Capability | For a peer hub |
|---|---|
| Roaming agreements per party and module | Yes |
| Operators’ visibility rules respected | Yes |
| Connection status through Hub Client Info | Yes |
| Charge records checked against agreed tariffs | Yes |
Peering checklist
What a peer hub prepares and proves
- The OCPI parties your hub speaks for (country code, party ID, role) and the parties you want to reach here
- The modules you will exchange and their direction for each side
- Your OCPI version and a public HTTPS versions URL (Hub follows no redirects)
- The credentials handshake from your platform, then Hub’s connection and module tests against your endpoint
- How your hub forwards OCPI-from, OCPI-to and X-Correlation-ID, so routed messages can be traced end to end
- The X-Getz-Hub-Path header, a documented Getz extension: the hubs a message has already crossed, as comma-separated party codes. Pass it on and add your own hub; without it your hub counts as one hop
- A route count: at most four hubs between sender and receiver, and never back through a hub already in the path
- Roaming agreements with each party you exchange data with: nothing is routed without one
- Who watches deliveries and connection health in the partner portal, and who your engineers contact at Hub
A blocked route, and what to do next
{
"status_code": 4000,
"status_message": "Not routed (HOP_LIMIT_EXCEEDED): hop count 4 >= max 4",
"timestamp": "2026-11-21T09:15:02Z"
}- Hop limit or loop: route through fewer hubs, connect to the receiving party directly, or agree the route with the destination’s own hub; do not re-send the same message through the chain.
- No agreement: propose an agreement for that module to the party, or ask it to accept yours; then send again.
- Not sure why: e-mail support@getzcharging.com with the X-Correlation-ID. Hub staff read the routing decision and its trace for that message.
Questions
For hub operators
Do peer hubs receive connection status?
Yes. Peer hubs hear about every party through OCPI Hub Client Info, as the specification intends for hubs.
What terms apply to peers?
The same as for any other partner. Hub’s published price list, coming soon, applies to peers exactly as to operators and apps.
Which networks would we reach?
Participating networks only: those connected to Hub that agree to roam with your parties. Ask us about the markets and counterparties you need; we do not list partners until they have agreed to be named.
What should our engineers prepare?
Your hub’s OCPI parties (country code and party ID), your OCPI version and the modules you want to exchange. Loop prevention and the hop limit apply from the first message. Technical prerequisites.
We are an operator. Does peering change who sees our sites?
No. Agreements and visibility rules apply to peered traffic exactly as to direct partners. Visibility and privacy controls. Apps should start on the EV charging apps page.
How do we start peering?
Tell us about your hub with the form below. We agree the modules and parties, you complete the OCPI credentials handshake, and both sides watch the first deliveries in the partner portal.
Enquiry
Discuss hub peering
What happens next
Tell us about your hub, the regions you cover and your OCPI version. We reply by e-mail.
Peer hubs connect over standard OCPI 2.1.1, 2.2.1 or 2.3.0, with loop prevention and a 4-hop limit.