Suspend token
Moves an ACTIVE token to SUSPENDED, so it stops authorizing charging until it is reactivated. An optional reason is recorded on the history event.
Requires the emsp:tokens:write scope.
Authorizations
The access token received from the authorization server in the OAuth 2.0 flow.
Headers
Client-generated unique key per operation intent (UUID). Same key + identical body replays the original response; same key + different body returns 409.
Path Parameters
The token id
Body
Free-text reason, recorded on the history event of each token the action changes
500"Card reported lost"
Response
The suspended token
Canonical schema version
v1 Stable internal token id, commonly a UUIDv7
64Owning tenant, set by the platform
RFID, APP_USER, AD_HOC_USER, EMAID, OTHER Primary credential identifier, unique within the tenant
50Contract or credential identity, e.g. an eMAID
50Issuer name associated with the credential
100OCPI whitelist policy
ALWAYS, ALLOWED, ALLOWED_OFFLINE, NEVER PROVISIONED, ACTIVE, SUSPENDED, EXPIRED, REVOKED Whether the token has been distributed to whitelist-capable CPO networks
When the token was created in the platform registry
Canonical publication timestamp propagated to roaming partners
2364Preferred language of the token owner
OCPI token group id used in roaming payloads. Unrelated to Spirii EMSP token groups
50Primary Spirii EMSP token group, set at provision time. A convenience only: membership is many-to-many and is managed through POST /emsp/v1/token-groups/{groupId}/tokens
50Name/value pairs validated against the tenant's active TOKEN metadata schema