Skip to main content
Vehicle commands are used to remotely control and configure vehicles through the c.technology platform. They include actions such as locking/unlocking doors, reconfigurations of transmission intervals, etc.

​
Command structure

Commands are structured as follows: 
{
    "vehicle_id": "veh_01jnk61e5pf6zs5ag6483xqe43",  // The vehicle the command is targeted at.
    "timestamp_created": "2025-09-17T12:21:49.566Z",  // Time the command was created.
    "timestamp_planned_execution": "2025-09-17T12:25:00.000Z",  // Optional time the command should be executed.
    "priority": "HIGH",  // Priority of the command: LOW (delivery when possible), HIGH (immediate delivery).
    "command": "DOUT1:ON",  // The command to be executed, format depends on the command type.
    "timestamp_execution": null,  // Time the command was executed, null if not yet executed.
    "response": null,  // Response from the vehicle after execution, null if not yet executed.
}
Commonly, IoT devices in vehicles only communicate at certain intervals to save power and data costs. Thus, most commands are sent with LOW priority, and queued and delivered when the vehicle next connects to the platform. Commands with HIGH priority are delivered immediately when the vehicle connects, interrupting regular data transmission if necessary.
It may not be possible for you to send HIGH priority commands depending on your vehicles, IoT devices, and subscription plan.
⌘I