Skip to main content
Getz Hub

Resources

Guides on roaming, OCPI and charging data

Practical answers to the questions operators, app teams, car brands and data teams ask us: start with the references below.

Start here

References for your evaluation

Coming soon

Guides we are writing

Each guide will answer a real question from operators, app teams or data teams. Until they are published, the references above cover the same ground.

  • OCPI and interoperability

    What the OCPI versions change, and how hubs translate between them.

    • What changes between OCPI 2.1.1, 2.2.1 and 2.3.0?
    • Do I need a hub or peer-to-peer OCPI?
  • EV roaming

    How roamed sessions, tokens and agreements work end to end.

    • How does a roamed charging session work?
    • What is a roaming agreement in OCPI?
  • CPO integration

    Connecting a back office: onboarding, credentials and visibility.

    • How do I keep private chargers private when roaming?
    • What does the OCPI credentials handshake involve?
  • Charging data

    Public charging data for navigation, in-car and fleet systems.

    • Which charging data is public, and who may use it?
    • API or feed: which delivery suits a map provider?
  • Charge-record assurance

    Checking roamed charge records against agreed tariffs.

    • What does charge-record assurance check, and what not?
    • Why do roamed charge records not match the tariff?
  • Cross-border charging

    Roaming across Southern African borders, currencies and hubs.

    • How does hub peering work for visiting drivers?
    • How are tariffs in different currencies checked?

Have a question we should answer here?

Tell us. Good questions become guides.