Back
Tokens
OCPI 2.2.1
Overview
Tokens represent driver identification: RFID cards, app-based auth, or ad-hoc payment. EMSPs push token data to CPOs so drivers can be authorized at any charge point in the roaming network.
Who sends
eMSP (e-mobility service provider)
Who receives
CPO (Charge Point Operator)
Key Fields
| Field | Type | Description |
|---|---|---|
uid | CiString(36) | Unique token identifier (e.g. RFID UID) |
type | TokenType | RFID, APP_USER, or OTHER |
auth_id | CiString(36) | Contract ID for this driver |
valid | boolean | Whether the token is currently valid |
whitelist | WhitelistType | ALWAYS, ALLOWED, ALLOWED_OFFLINE, or NEVER |
Endpoints
GET
/ocpi/2.2.1/tokens/
PUT
/ocpi/2.2.1/tokens/{country_code}/{party_id}/{token_uid}
POST
/ocpi/2.2.1/tokens/{token_uid}/authorize
Live Endpoint Tester
Send requests directly to the local backend and see the response.
GET