Permissions prefixed with read_ allow your application to get data from a vehicle as part of GET requests or event based webhooks.

read_batteryRead an EV’s high voltage battery data
read_chargeRead charging data
read_charge_locationsAccess previous charging locations and their associated charging configurations
read_charge_recordsRead charge records and associated billing information
read_charge_eventsReceive notifications for events associate with charging
read_climateRead the status and settings of the vehicle’s climate control system
read_compassRead the compass direction the vehicle is facing
read_engine_oilRead vehicle engine oil health
read_extended_vehicle_infoRead vehicle configuration information from a vehicle
read_fuelRead fuel tank level
read_locationAccess the vehicles location
read_odometerRetrieve total distance traveled
read_speedometerRead a vehicle’s speed
read_thermometerRead temperatures from inside and outside the vehicle
read_tiresRead a vehicle’s tire status
read_vehicle_infoKnow make, model, and year
read_vinRead VIN


Permissions prefixed with control_ allow your application to issue commands or apply settings to a vehicle as part of POST or PUT requests.

control_chargeControl a vehicle’s charge state
control_climateSet the status and settings of the vehicle’s climate control system
control_securityLock or unlock the vehicle

Required Permissions

The required: prefix allows you to filter out vehicles on the Connect grant screen that do not support it e.g. passing required:read_fuel would lead to a no_compatible_vehicles error in Connect for Tesla as it’s an EV and cannot support fuel endpoints.