Skip to navigation
ProxyCommands

Send an OCPP command to a charger

Queues one OCPP CALL for the charger through the OCPP gateway. Poll GET /proxy/ocpp/commands/{tracking_id} for the charger’s answer. Organization is taken from the Bearer JWT.

Authentication

AuthorizationBearer

Bearer authentication of the form Bearer <token>, where token is your auth token.

Path parameters

commandstringRequiredformat: "^[A-Za-z0-9]+$"1-64 characters

OCPP action, e.g. RemoteStartTransaction or Reset.

Headers

X-Request-Idstring or nullOptionalformat: "^[\x21-\x7e]+$"<=64 characters
X-Correlation-Idstring or nullOptionalformat: "^[\x21-\x7e]+$"<=128 characters

Request

This endpoint expects an object.
charge_point_idstringRequired1-255 characters
Charger that receives the OCPP CALL.
ocpp_versionenum or nullOptional

v16 → OCPP 1.6, v201 → 2.0.1, v21 → 2.1. Omit to use the charger’s registered version (1.6 if it has none).

Allowed values:
payloadmap from strings to anyOptional
OCPP action payload, sent as the CALL body.
idempotency_keystring or nullOptional>=1 character
Replays return the first dispatch instead of sending again.

Response

Successful Response
charge_point_idstring
Charger the CALL was sent to.
ocpp_versionstring
OCPP version the CALL was sent in.
commandslist of objects
The CALLs queued for the charger.

Errors

400
Bad Request Error
401
Unauthorized Error
404
Not Found Error
409
Conflict Error
422
Unprocessable Entity Error
429
Too Many Requests Error
502
Bad Gateway Error
504
Gateway Timeout Error