Announcements and Changelog

Ability to generate a token on behalf of a business is now live. See here for more information.

The charging and preconditioning schedule commands are now supported via Fleet API. These should be preferred over the scheduled charging and departure commands.

Vehicles must be running firmware version 2024.26 or later.

Fleet Telemetry onboarding no longer requires submitting a CSR to Tesla. Vehicles running firmware version 2024.26.4 or later can receive configurations through the vehicle-command HTTP proxy. Full setup details are available on the Fleet Telemetry page.

Applications with CSRs submitted but not processed should migrate to using the new vehicle-command approach.

Applications configured using a CSR will continue to work, but are encouraged to migrate to the new process.

Developers can now create open-source applications through https://developer.tesla.com, which enables application use without publishing secrets. Open-source applications are limited to the discovery tier and do not use a client secret for token creation.

Application scopes can now be updated on developer.tesla.com by clicking the API & Scopes Manage link in the Credentials & API section of an application. As described in #5 of the third-party token, users can update scopes and revoke access to applications using the update/revocation auth.tesla.com page. Note: Application scope changes may take up to 10 minutes to become active.

Fleet API is Tesla's official 3rd party API and the only supported API for vehicle interactions. The list of available endpoints can be found at Endpoints and Regional Requirements. Starting April 2024, any vehicle APIs not part of this list will be phased out. Per the Fleet API policies, continued usage of unsupported APIs will result in the revocation of Fleet API access privileges.

With the release of Tesla mobile app 4.30.0, vehicle pairing will require the application public key to remain hosted at the /.well-known/ path on the domain used for application registration. This is a security improvement that includes partner domains in the chain of trust for vehicle interactions. See the check_csr script for an example testing the presence of the registerd public key on the application domain.

As part of a security improvement, the acquisition of a new Refresh token will now render the user’s previous Refresh token and its associated Access tokens invalid.

Registering vehicles for fleet-telemetry is now live. See here for more information.

Calls directly to the /command endpoint without the use of the Tesla Vehicle Commands protocol SDK will be deprecated. For command continuity, migrate to the Tesla Vehicle Commands protocol as soon as possible:

When calling the /command endpoint for a vehicle that requires the Tesla Vehicle Command protocol, Fleet API will return an error.

Vehicles running firmware versions 2023.38+ will not return location information by default in vehicle data. Developers who need that information will need to add "location_data" parameter to the query, see here. This will result in a location sharing icon to show on the vehicle UI.

Important: Fetching vehicle data periodically is not recommended, see Fleet Telemetry for streaming needs.

Following the release of Tesla Vehicle Command SDK support for REST API vehicle command endpoints is now reaching end of life. Starting 2024 most vehicles will require sending commands via Tesla Vehicle Command SDK.

The use of Tesla http proxy is recommended for ease of development and to accelerate the transition to Tesla Vehicle Command (via SDK). When applicable, the proxy will transform Rest API HTTP commands into the Tesla Vehicle Command Protocol. Once configured, developers can simply point their application to the proxy without making any code changes to their application.

Tesla Vehicle Command SDK provides end-to-end authentication for sending commands to vehicles. This is the recommended way of sending commands to vehicles.

Security experts are encouraged to dive more into the protocol and give feedback on Github. To report a security issue, follow the directions on https://www.tesla.com/legal/security.