Authorize a new connected vehicle

With a pending connected vehicle, the authorization process can be continued. Make sure to follow the provider-specific instructions in the first step before continuing. It's also recommend to create a subscription, as explained in the previous section.


To authorize a new connected vehicle provide the id argument. Each provider requires an options argument. Details can be found below.


After completing the make specific authorization flow initiated by authorization_url, the authorizeConnectedVehicle operation should be executed to validate that the vehicle is successfully authorized. The options argument can be an empty object.

When using Enode it is not possible to have multiple vehicles attached to the same OEM account (eg. Tesla). This scenario will return CONNECT_MULTIPLE_VEHICLES_NOT_ALLOWED and needs to be handled explicitly in your application.


input AuthorizeConnectedVehicleInput

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


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.