Interventions

Interventions represent the actions a user needs to do in order to enable a blocked capability on their device.

Depending on the device model or version, specific capabilities may not be accessible. These cases can be split into two categories:

• Missing capabilities are permanently missing from a device, e.g. a specific vehicle model missing an onboard GPS will never be able to transmit a location.

• Blocked capabilities are inherently supported by a device model but require user action to be unblocked for a user’s specific device, e.g. a vehicle that has an onboard GPS and can start transmitting a location if the user enables the setting in their vehicle’s infotainment system.

Interventions represent the user actions required to unblock a blocked capability. For each connected device, every blocked capability contains one or more interventions that must be resolved to unblock the capability.

Accessing interventions via our API

Interventions are surfaced via the capabilities object returned by fetching a specific device. In most cases, this means there is a two-step process to receive and react to interventions:

1. Fetch a device, e.g. via Get vehicle endpoint. Detect a blocked capability with an intervention ID attached to it.

2. Query the Get intervention endpoint to fetch detailed information about this intervention.