Connect to YoHub over OCPI 2.2.1
Everything your engineering team needs to plan the integration: roles, modules, the handshake and how we test before you go live.
Roles
YoHub connects to your platform in the role you play:
- As a CPO, you connect to YoHub’s eMSP-facing interface and push your locations, tariffs, sessions and CDRs.
- As an eMSP, you connect to YoHub’s CPO-facing interface and receive locations and tariffs, send tokens and commands, and receive sessions and CDRs.
- A company that is both can connect in both roles.
Supported modules
| Module | CPO role | eMSP role |
|---|---|---|
| Versions | ✓ | ✓ |
| Credentials | ✓ | ✓ |
| Locations | ✓ | ✓ |
| Tariffs | ✓ | ✓ |
| Tokens | ✓ | ✓ |
| Sessions | ✓ | ✓ |
| CDRs | ✓ | ✓ |
| Commands | ✓ | ✓ |
| Charging Profiles | — | — |
Charging Profiles (smart charging) is not offered today.
Onboarding steps
- 01
Book a call. We review your OCPI implementation and your role.
- 02
Receive your token. We issue the token for the credentials handshake.
- 03
Run the handshake. Your platform registers with YoHub through the OCPI 2.2.1 credentials module and exchanges version and endpoint details.
- 04
Test. We exchange test locations, a token and a session end to end, and check the CDR.
- 05
Go live. Your connection is switched to production and your data starts flowing to partners.
OCPI 2.2.1 integration notes
HTTPS, JSON, token-based authorisation per OCPI 2.2.1.
List endpoints follow OCPI 2.2.1 pagination.
Technical questions go to the integration team, via sales@yocharge.com until a dedicated address exists.
Connect once. Reach every network.
Book a 45-minute call with the team that runs the platform. We’ll map your integration and show you the network live.