Tesla Fleet API

First obtain a Tesla developer app client_id and client_secret from Tesla Developer after approval via Getting Started. Then mint a partner token by POSTing grant_type=client_credentials, your client_id, client_secret, an API audience equal to the regional Fleet API base URL, and desired scopes to partner token docs.

First obtain a Tesla developer app client_id and client_secret from Tesla Developer after approval via Getting Started. Then send users through the authorization-code flow described in Third-Party Tokens: redirect them to https://auth.tesla.com/oauth2/v3/authorize, receive the callback code, and exchange it at POST https://fleet-auth.prd.vn.cloud.tesla.com/oauth2/v3/token. Save the refresh_token if you request offline_access.

First obtain a Tesla developer app client_id and client_secret from Tesla Developer and a business consent auth_code via Tesla for Business Consent Management as documented in Third-Party Business Tokens. Then mint the token by POSTing grant_type=client_credentials, client_id, client_secret, auth_code, scope, and regional Fleet API audience to https://fleet-auth.prd.vn.cloud.tesla.com/oauth2/v3/token.