Getting Started


Using the Tesla Fleet API

Teslemetry will proxy any Tesla Fleet API requests with a valid access token and subscription to the correct Fleet API regional server for your account. Documentation on the available Fleet API endpoints can be found at

Sending API Requests

API requests use the exact same URI path as the Tesla Fleet API, with one of the Teslemetry load balancers as the domain name.

Teslemetry has three load balancer addresses:

  • - Automatically picks the fastest region.
  • - Only uses North American regions, ideal for the Tesla NA region.
  • - Only uses European regions, ideal for the Tesla EU region.
Curl Example
curl --header "Authorization: Bearer {token}" '{vin}'
Browser Example (less secure){vin}?token={token}
Python Example
import asyncio, aiohttp, tesla_fleet_api
    async def main():
    async with aiohttp.ClientSession() as session:
    api = tesla_fleet_api.Teslemetry(access_token="{token}",session=session)
    print(await api.vehicle.vehicle_data({vin}))
    except tesla_fleet_api.exceptions.TeslaFleetError as e:

PyPi - GitHub

Virtual Key & Command Signing

Newer vehicles require commands to be signed by Teslemetry to increase security. You can see if your vehicle requires command signing by looking at the Command Sign value in the console. The vehicle owner can install the Teslemetry virtual key by clicking the following link using a mobile phone with the Tesla app installed:

You can read more about the Virtual Key and Command Signing topics.