Overview

Tessie API endpoints are powered by the Tesla Fleet API but include several enhancements to save you a lot of time and make life a lot easier:

Automatic authorization handling

The Tesla Fleet API uses rotating tokens across multiple APIs requiring you to build a complex OAuth system to maintain. Tessie does it all for you. Generate a Tessie access token and you're done.

Automatic region handling

The Tesla Fleet API requires retrieving, parsing and handling different API regions. Tessie does it for you.

Automatic Vehicle Command Protocol handling

Tesla requires that most vehicles route signed commands through Vehicle Command Protocol. Don't worry — we took care of that for you too.

Doesn't prevent sleep

Making data calls to the Tesla Fleet API will prevent your vehicle from sleeping and drain the battery as a result. Tessie data calls don't affect sleep so your Tesla can sleep and conserve energy.

More data

With the Tessie API, you can also access drives, charges, idles, battery health data and more.

Historical data

The Tesla Fleet API only returns real-time data. Get data for any timeframe with Tessie.

Get data for many vehicles

With the Tessie API, you can access data for many vehicles at once.

More reliable vehicle controls

Tesla Fleet API commands randomly fail for a variety of reasons and requires building complex retry logic. Tessie ensures that commands get executed by handling various network and firmware errors for you.

Get data when the vehicle is sleeping

The Tesla Fleet API doesn't return data if the vehicle is sleeping. Tessie always shows you the most recently seen data so you don't need to wake your Tesla.