Reference · built on requestConnectorFleet & telematics

Tesla Fleet API

Vehicle state, charging, alerts, and Fleet Telemetry streams for Tesla vehicles, with signed commands through the Vehicle Command Protocol.

Request accessPricing ↗

About

Fleet API is Tesla's data and command service for its vehicles and energy devices. A registered application reads a vehicle's charge_state, drive_state, climate_state, and location_data through vehicle_data, or has the car stream fields such as Soc, Location, Odometer, and DetailedChargeState to a Fleet Telemetry server you host. Commands are signed under the Vehicle Command Protocol with a key the driver pairs to the car as a virtual key. Access is billed per request and per streamed signal, in three regions with their own base URLs.

An operator on Fibric reads the stream across a depot, sees which vans will miss their departure state of charge, and proposes the charge limit, the schedule, or the precondition for a dispatcher to approve, once, with a receipt.

This is a reference listing. It documents what Fibric would read from Tesla Fleet API and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Vehicles on the account through GET /api/1/vehicles, paged 100 at a time, and fleet_status with firmware version, telemetry client version, and key count
  • GET /api/1/vehicles/{vin}/vehicle_data with endpoints charge_state, climate_state, closures_state, drive_state, gui_settings, location_data, vehicle_config, and vehicle_state
  • Fleet Telemetry fields streamed from the car, such as VehicleSpeed, Location, Odometer, Soc, BatteryLevel, ChargeState, DetailedChargeState, ChargeLimitSoc, and TimeToFullCharge
  • Tire, door, and safety fields including TpmsPressureFl through TpmsPressureRr, TpmsSoftWarnings, DoorState, Locked, SentryMode, DriverSeatBelt, and Gear
  • recent_alerts, release_notes, service_data, and nearby_charging_sites per VIN, and drivers on the vehicle
  • Fleet telemetry errors per VIN and per account after a config is applied, through fleet_telemetry_errors and fleet_telemetry_error_vins

Proposed actions

  • Target capability: propose charge_start, charge_stop, set_charge_limit, or set_charging_amps as signed commands under vehicle_charging_cmds
  • Target capability: propose set_scheduled_charging, add_charge_schedule, set_scheduled_departure, or add_precondition_schedule for a depot window
  • Target capability: propose door_lock, door_unlock, flash_lights, honk_horn, or set_sentry_mode under vehicle_cmds
  • Target capability: propose auto_conditioning_start, set_temps, or set_preconditioning_max before a departure
  • Target capability: propose a fleet_telemetry_config for a VIN naming hostname, port, ca, and fields with interval_seconds, or a wake_up before a live read

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Every van at its departure charge

    Stream Soc, ChargeLimitSoc, TimeToFullCharge, and DetailedChargeState from the depot. Where the arithmetic misses the first route, propose set_charge_limit and charge_start for the night shift to approve.

    With Charge Readiness, Depot Charging

  • Shift depot charging off the peak

    Pair ChargeAmps and ACChargingPower with your tariff window. Propose set_scheduled_charging or set_charging_amps per vehicle so the depot stays under its demand cap.

    With Charge Balancing, Tariff Window

  • Catch the tire or alert before the driver calls

    Watch TpmsSoftWarnings, TpmsHardWarnings, and recent_alerts. Propose the service slot and the spare vehicle, with the alert text attached.

    With Vehicle Fault

  • Precondition the cabin for a cold departure

    Read OutsideTemp and InsideTemp with the departure time. Propose auto_conditioning_start or add_precondition_schedule so the car is warm and the range estimate holds.

    With Charge Readiness

Requirements

  • A Tesla account with multi-factor authentication and an approved developer application with the scopes it needs
  • A prime256v1 EC public key hosted at https://<app domain>/.well-known/appspecific/com.tesla.3p.public-key.pem and registered through POST /api/1/partner_accounts
  • A virtual key added by the driver from https://www.tesla.com/_ak/<developer-domain>; most business vehicles and pre-2021 Model S and X do not need it
  • The vehicle-command SDK or its HTTP proxy to sign commands and telemetry configs; an unsigned command is rejected and the vehicle does nothing
  • A Fleet Telemetry server on the public internet and vehicle firmware 2024.26 or later for streaming
  • A payment method and a billing limit above the default of 0; the audience must match the region: na, eu, or cn
Authentication
OAuth 2.0 at https://auth.tesla.com/oauth2/v3/authorize and https://fleet-auth.prd.vn.cloud.tesla.com/oauth2/v3/token: a client_credentials token for an application acting for a business, or an authorization_code token acting for a person, with scopes such as openid, offline_access, user_data, vehicle_device_data, vehicle_cmds, and vehicle_charging_cmds and an audience set to the regional base URL.

Limits

  • Per vehicle and account: 60 realtime data requests, 3 wakes, and 30 device commands a minute; polling vehicle_data regularly is expensive
  • Pay per use with a $10 monthly discount; status codes below 500 are billed; passing the billing limit suspends the API and removes telemetry configs
  • A vehicle streams to at most five third-party applications; pre-2018 Model S and X without the infotainment upgrade cannot stream
  • A refresh token is single use and expires after 3 months; a share invite link is single use and expires after 24 hours

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Tesla Fleet API ↗

Questions and answers

Why do commands have to be signed?
Fleet API uses the Tesla Vehicle Command Protocol. The driver pairs your application's public key to the car as a virtual key; your backend signs each command with the private key, usually through the vehicle-command SDK's HTTP proxy. If a command is not signed, the vehicle rejects it. Most business vehicles and pre-2021 Model S and X are exempt.
What does Fleet Telemetry cost and what does it need?
Telemetry streams from the car to a server you host on the public internet, so you avoid polling vehicle_data. It needs firmware 2024.26 or later and a paired virtual key. Usage is billed per signal; Tesla's sample driving config works out to about $0.006 an hour, and a $10 monthly discount applies.
Which base URL do I use?
North America and Asia-Pacific use https://fleet-api.prd.na.vn.cloud.tesla.com, Europe, the Middle East, and Africa use https://fleet-api.prd.eu.vn.cloud.tesla.com, and China uses https://fleet-api.prd.cn.vn.cloud.tesla.cn. The token's audience parameter must name the same base URL.
Ask about Tesla Fleet API

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Tesla Fleet API through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy