Skip to main content

EV Charging Protocols

Rollyy integrates with EV charging networks and vehicle manufacturers using industry-standard protocols.

OCPI 2.2.1 — Charging Network Roaming​

Status: ✅ Live

OCPI (Open Charge Point Interface) is the primary protocol Rollyy uses to connect to charging networks. It enables the autonomous robot to start and stop charging sessions at any OCPI-compliant CPO across Europe.

Rollyy operates as an eMSP (e-Mobility Service Provider). Supported modules:

ModuleRole
CredentialsHandshake & token exchange
LocationsReceive charger locations from CPOs
SessionsReceive live session updates
CommandsSend START/STOP to CPOs
TariffsReceive pricing from CPOs
TokensExpose driver tokens for CPO validation
Charging ProfilesSend smart charging schedules

Connected networks: Any OCPI 2.2.1 compliant CPO, including roaming hubs (Hubject, Gireve)

→ Full OCPI documentation

Vehicle Manufacturer APIs​

Direct integration with vehicle OEM APIs for battery status, charge port control, and remote charging.

Tesla Fleet API​

OAuth 2.0 integration for Tesla vehicles.

Features:

  • Battery SoC and range
  • Charge port lock/unlock
  • Start/stop charging
  • Vehicle location

Base URL: https://api.rollyy.com/v1/tesla

Mercedes-Benz API​

Mercedes me API for Mercedes-Benz and smart EQ vehicles.

Features:

  • Battery status and range
  • Charging port lock/unlock
  • Start/stop charging
  • Vehicle location

Base URL: https://api.rollyy.com/v1/mercedes

BMW ConnectedDrive​

BMW and MINI electric vehicle integration.

Features:

  • Battery SoC and charging status
  • Charging flap control
  • Remote charging control
  • Vehicle location

Base URL: https://api.rollyy.com/v1/bmw

VW Group API​

We Connect (VW), myAudi (Audi), and Porsche Connect.

Features:

  • Battery status for VW ID., Audi e-tron, Porsche Taycan
  • Charging port control
  • Charge limit configuration

Base URL: https://api.rollyy.com/v1/vwgroup

Quick Start​

Start a charging session via OCPI​

curl -X POST https://api.rollyy.com/ocpi/2.2.1/commands/START_SESSION \
  -H "X-API-Key: your_api_key" \
  -H "Content-Type: application/json" \
  -d '{
    "evse_uid": "FI-VRT-E12345",
    "location_id": "FI-VRT-L001",
    "robot_job_id": "550e8400-e29b-41d4-a716-446655440000"
  }'

Response:

{
  "session_id": "770e8400-e29b-41d4-a716-446655440002",
  "cpo_result": "ACCEPTED",
  "status": "pending"
}

Get Tesla battery status​

curl -X POST https://api.rollyy.com/v1/tesla/battery-status \
  -H "X-API-Key: your_api_key" \
  -H "Content-Type: application/json" \
  -d '{"vehicle_id": "veh_001"}'

Authentication​

All API requests require an API key:

X-API-Key: your_api_key

OCPI endpoints additionally use token-based auth exchanged during the CPO handshake. See OCPI documentation for details.

Next Steps​