Sign in / Sign up
Mutate to update a connected vehicle

Remove a connected vehicle

A connected vehicle can be removed by using the removeConnectedVehicle mutation. This operation will first revoke access to the vehicle and then completely remove it. If there is an open subscription an exception will occur.

Removing a connected vehicle requires authentication. This is currently not supported in the developer portal.

Mutation

To remove a connected vehicle provide the id of the vehicle. The mutation will return null or a CONNECTED_VEHICLE_NOT_FOUND exception if the vehicle no longer exists.

Arguments

input • RemoveConnectedVehicleInput

• Required

Other fields

id • ID

Unique ID of the connected vehicle

vehicle_id • ID

Unique ID of the vehicle

status • ConnectedVehicleStatus

Status of the connected vehicle

Show ConnectedVehicleStatus enum values

authorization_url • String

URL to connect the vehicle to the connectivity provider

provider • CarConnectivityProvider

Connectivity provider

Show CarConnectivityProvider enum values

scope • ConnectScope

Scope for accessing the vehicle

Show ConnectScope enum values

label • String

Custom label for a connected vehicle that can be assigned by a user

vin • String

Vehicle identification number, unique identifier for a vehicle

Response

A response can either contain a data or an errors object. The response header will always return 200 as a status code.

Data object

When successful, a data object will be returned with the requested fields. If there are no fields present the data object will return the operation name with the appropriate return type. If the operation was a query, this output will be an object of the schema’s query root type; if the operation was a mutation, this output will be an object of the schema’s mutation root type.

Error object

If unsuccessful, an errors object will be returned with more details in the extensions object. The error object can contain any of the following objects.