Skip to main content
Commands are available to authorized accounts and can affect physical devices. Validate command syntax and device configuration with Graviton before sending operational commands.

Queue a command

POST /objects/{imei}/commands accepts: Use the returned cmd_id with GET /objects/{imei}/commands/{commandId}. A 201 response confirms queueing. It does not confirm that the tracker received or executed the command. Inspect the returned status and response fields and verify the vehicle outcome through your normal operations process.

Engine control

The /immobilize and /remobilize operations require the stop_engine permission for subaccounts. They can use a matching account command template or a supported protocol command. When neither is available, the API returns ENGINE_COMMAND_REQUIRED and requires a device-specific cmd, type, and gateway. Confirm safe operating conditions before engine control. Do not copy a command from a different tracker model. Avoid blind retries after timeouts because a queued command may still execute.