DeveloperSkip to main content

  1. Fleet API
  2. Charging

Partner Endpoints

Endpoints

fleet_telemetry_errors

GET /api/1/partner_accounts/fleet_telemetry_errors

Returns recent fleet telemetry errors reported by vehicles after receiving the config.

This endpoint requires a partner authentication token.

public_key

GET /api/1/partner_accounts/public_key

Returns the public key associated with a domain. It can be used to ensure the registration was successful.

This endpoint requires a partner authentication token.

register

POST /api/1/partner_accounts

Registers an existing account before it can be used for general API access. Each application from developer.tesla.com must complete this step.

  • The domain for this endpoint must match the root domain from the allowed_origins on developer.tesla.com. Ex.: 123.abc.com can be used for an allowed_origin of www.abc.com.
  • The Bearer token for this request must be a partner authentication token.
  • A PEM-encoded EC public key using the secp256r1 curve (prime256v1) must be and remain hosted at https://<app domain>/.well-known/appspecific/com.tesla.3p.public-key.pem. This public key will be registered on devices and used to validate commands that are generated by the vehicle-command proxy.
  • The domain will be displayed to users as part of the mobile-app-based vehicle key-pairing process.

This endpoint requires a partner authentication token.