Announcements and Changelog

Best practices, cost optimizations, and billing guidance is now available on the Billing and Limits page.

Thank you to the partners who have already completed the program changes described in communication dated 26 November 2024. For those still completing their changes, to prevent disruption to your services, Tesla will also send reminders about the changes starting in March. After the reminder period, access will be blocked.

Since launch, Fleet API has been made available to partners free of charge as part of the discovery period.

Beginning January 1, 2025, Fleet API will begin charging for access. Pricing details are available on the home page.

During the transition period, the application management dashboard will show charges based on application usage. Payment will be waived for charges accumulated prior to January 1, 2025. The estimated charges should be used to understand and optimize application usage.

Starting January 1, 2025, payment for Fleet API applications will take effect. To ensure continued service, applications must take action:

• Configure a billing method in the application management dashboard.
• Set a billing threshold to protect from unexpected charges (recommended). Applications above the specified limit will not be disabled prior to January 1, 2025.
• Optimize application behavior to improve usage.
  • Migrate from polling the vehicle_data endpoint to using Fleet Telemetry.
  • Vehicle wakes should be used sparingly.
  • Before sending a command, confirm the application's fleet key is present on the vehicle and the vehicle is awake. Wake state can be monitored through Fleet Telemetry or the vehicle endpoint.
  • Further suggestions are available on the Best Practices page.

Not all countries support payments at this time. Developers in countries that do not yet support payments will not have a Billing and Usage button in their application management dashboard. Developers in these countries should work to optimize their applications but do not need to take action at this time. Applications created from countries that do not support payment will have limited usage beginning in January 2025.

This scope provides more granular data access control to developers and users. To users it will appear as "Allow access to your vehicle location information, including data such as precise location, and coarse location for approximate location services."

What does this mean for application developers and users?

• Developers: Applications can now request the vehicle_location scope when authorizing users, allowing them to access vehicle location information.
• Users: The vehicle_location scope will now appear on the authorization page for applications that require it.

Migration plan

1. November 2024 - vehicle_location scope is introduced. The /authorize page will show users the vehicle_location scope when loaded with the vehicle_device_data scope. After the migration period, the vehicle_location scope will be need to be explicitly requested.
2. December 2024 - Where required for partner application use cases, partners must start explicitly requesting the vehicle_location scope for new authorizations, and directing existing users to authorize the vehicle_location scope.
3. January 2025 - Authorization grants without the vehicle_location scope will lose access to location related functionality.

Request Only Necessary Scopes: In line with Fleet API Agreement and to enable user trust and safety, it is only permissible to request authorization for scopes that are immediately necessary for the application to function.

Refer the scopes for more information.

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.

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.