Vehicles
Endpoints for getting an account's vehicles
A logged in user can have multiple vehicles under their account (congrats on being rich!). This resource is primarily responsible for listing the vehicles and the basic details about them.
One potentially confusing part of Tesla's API is the switching use of the
id and vehicle_id of the car. The id field is an identifier for the car on the owner-api endpoint. The vehicle_id field is for identifying the car across different endpoints, such as the streaming or Autopark APIs.For the state and command APIs, you should be using the
id field. If your JSON parser doesn't support large numbers (>32 bit), then you can use the id_s field for a string version of the ID.Retrieve a list of your owned vehicles.
{
"response": [
{
"id": 12345678901234567,
"vehicle_id": 1234567890,
"vin": "5YJSA11111111111",
"display_name": "Nikola 2.0",
"color": null,
"tokens": ["abcdef1234567890", "1234567890abcdef"],
"state": "online",
"in_service": false,
"id_s": "12345678901234567",
"calendar_enabled": true,
"api_version": 7,
"backseat_token": null,
"backseat_token_updated_at": null
}
],
"count": 1
}
These resources are read-only and determine the state of the vehicle's various sub-systems.
Field | Example | Description |
|---|---|---|
id | 12345678901234567 | The id of the car. (Not the vehicle_id!) |
{
"response": {
"id": 12345678901234567,
"vehicle_id": 1234567890,
"vin": "5YJSA11111111111",
"display_name": "Nikola 2.0",
"color": null,
"tokens": ["abcdef1234567890", "1234567890abcdef"],
"state": "online",
"in_service": false,
"id_s": "12345678901234567",
"calendar_enabled": true,
"api_version": 7,
"backseat_token": null,
"backseat_token_updated_at": null
}
}
Last modified 1mo ago