What is Fleet API?

Fleet API is a RESTful data and command service providing access to Tesla vehicles, energy, and other types of devices. Partners can interact with their own devices, or devices for which they have been granted access by a customer.

Follow the onboarding process below to register and get an API key to interact with Tesla's API endpoints. Applications can request vehicle owners for permission to view account information, get vehicle status or even issue remote commands. Vehicle owners maintain control over which application they grant access to, and can change these settings at any time.

Create a Tesla account and ensure it has a verified email and multi-factor authentication enabled.

Click the 'Request Access' button below to request app access. Provide legal business details, application name, description, and purpose of usage. Tesla will review the request and email with status updates.

While requesting access, select the scopes to used by the application. Reference the authentication overview page for a list of available scopes.

Note: account creation requests can be automatically rejected if the application name already exists.

A public key must be hosted on the application's domain before making calls to Fleet API.

The key is used to validate ownership of the domain and provide additional security when using Vehicle Commands and Fleet Telemetry.

To create an EC public key using the secp256r1 curve (prime256v1), run:

openssl ecparam -name prime256v1 -genkey -noout -out private-key.pem

Then, generate the associated public key.

openssl ec -in private-key.pem -pubout -out public-key.pem

This public key should be available at:

https://developer-domain.com/.well-known/appspecific/com.tesla.3p.public-key.pem

Note: private-key.pem needs to be kept secret and should not be hosted on your domain.

Next, call the register endpoint to finish registration with Fleet API.

This request must be made with a partner authentication token.

To call the endpoint, view the endpoint's official documentation.

Now that the register endpoint has been called, Fleet API is configured and ready to receive requests.

Next steps to take:

• Selecting the proper authentication token type and generating tokens. Authentication overview.
• Pairing a public key to a vehicle. This is required to send Vehicle Commands and setup Fleet Telemetry.
• Configuring Fleet Telemetry which streams data directly to a server.