Skip to main content
The enable_ignition and disable_ignition commands depend on mobile network signal coverage to communicate with the vehicle. It is essential to ensure that the vehicle is reachable and connected before sending either command. If one of these commands is executed and the vehicle moves out of coverage, physical intervention may be required.
For security reasons, enable_ignition and disable_ignition require two-step confirmation. On the first call (without the code field), the command is not executed: the response returns status: "Confirmation", a 6-digit code, and a message to display to the user. To execute the command, resend the same request including the received code. See POST vehicle-command for details.Example of the first-step response (confirmation):
Usage requirements and responsibilities (ignition disablement)Remote ignition disablement is a sensitive feature. By using it, your company is responsible for ensuring that:
  • Access to ignition commands is restricted to authorized users and is not available to all users.
  • The command is initiated only by your company, not by third parties.
  • The vehicle is owned by your company, rented, or legally under your fleet.
  • The vehicle’s end user has provided consent.
  • Use is limited to situations where the vehicle is missing, there is reasonable suspicion of theft or robbery, or the vehicle is being used without authorization.
  • Your internal procedures have been completed before submission, including, when applicable, attempting to locate the vehicle through the available APIs, in accordance with applicable law.
  • An attempt was made to notify the end user before submission.
  • Reasonable efforts were made to confirm that the disablement can be completed safely.
After disabling the ignition, re-enable it (enable_ignition) as soon as it is no longer safe or necessary to keep the vehicle disabled.

​
enable_ignition

Enable ignition
  • Description: enables the ignition when the vehicle’s safety preconditions are met (see below).
  • Preconditions:
    • The vehicle must be turned off.
    • The vehicle ignition must have been previously disabled by remote command.
  • Example:

​
disable_ignition

Disable ignition
  • Description: disables the ignition when the vehicle’s safety preconditions are met (see below). A warning will be shown on the vehicle dashboard.
  • Preconditions:
    • The vehicle must be turned off.
  • Example:

​
start

Remote start
  • Description: starts the vehicle remotely when the vehicle’s safety preconditions are met (see below).
  • Preconditions:
    • The engine hood must be closed.
    • The fuel tank must not be in reserve.
    • The battery voltage must be at adequate levels.
    • The hazard lights must not be on.
    • The transmission must be in Park (P).
    • There must be no malfunction indicator lights on the vehicle dashboard.
The vehicle must not have completed more than two consecutive successful remote starts. For the next remote start to succeed, the customer must start the vehicle physically before trying again.
  • Example:

​
cancel_start

Cancel remote start
  • Description: cancels a previously sent remote start command or turns off the vehicle if it was started by remote command and the ignition was not turned on manually.
  • Preconditions:
    • The vehicle must have been previously started by remote command.
  • Example: