Commands
Commands in OCPI 2.2.1
The Commands module asks a CPO to perform an action, such as starting or stopping a charging session. The immediate ACCEPTED response means the CPO accepted the command request. It does not prove that charging started. The request supplies response_url, and the later POST reports the Charge Point result; this example has ACCEPTED followed by REJECTED. The immediate CommandResponse supplies timeout for this command. The callback uses CommandResult. The illustrative 30 seconds is this response value, not a universal deadline.
Sources (6)
Example payload · start-session-request
{
"response_url": "https://sender.example.invalid/results/example-command",
"token": {
"uid": "EXAMPLE-TOKEN",
"type": "RFID",
"issuer": "Example Provider",
"valid": true,
"whitelist": "NEVER",
"last_updated": "2026-01-01T00:00:00Z",
"country_code": "NL",
"party_id": "EXB",
"contract_id": "EXAMPLE-CONTRACT"
},
"location_id": "EXAMPLE-LOCATION"
}Example payload · immediate-response
{
"result": "ACCEPTED",
"timeout": 30
}Example payload · eventual-callback
{
"result": "REJECTED"
}Which endpoints does this module define?
These paths illustrate the requests. Use the URLs advertised by your partner, replace the placeholders and choose the matching interface. A listed method does not establish that this site's simulator implements it.
CPO · receiver interface
Send a command to the CPO, requesting the CPO to send the command to the Charge Point
POST/ocpi/ 2.2.1/ commands/ START_SESSION Send a command to the CPO, requesting the CPO to send the command to the Charge Point
POST/ocpi/ 2.2.1/ commands/ STOP_SESSION Send a command to the CPO, requesting the CPO to send the command to the Charge Point
POST/ocpi/ 2.2.1/ commands/ RESERVE_NOW
Source
eMSP · sender interface
Receive the asynchronous response from the Charge Point.
POST{response_url}
Source
Try an endpoint
Send a request to this site's OCPI endpoints and read the answer. It never reaches your own system.