Introduction

Your apps read your customers' data, and act on it, with the Teslemetry for Business API. It uses the same paths as the Teslemetry API and the Tesla Fleet API, plus a few business endpoints.

Every endpoint, with its request and response schema, is in the API reference. The OpenAPI document is at api.teslemetry.pro/openapi.json.

Base URLs

Use your business's region, shown on the API keys page, or https://api.teslemetry.pro. Each customer's data lives in the region Tesla assigns them, not yours. Teslemetry forwards each request to the right region for you, so you can call any of these with any key.

Each response has an x-region header with the region that answered it.

Authentication

Create an API key in your portal, and send it as a bearer token:

curl --header "Authorization: Bearer {token}" 'https://api.teslemetry.pro/api/business/products'

You can also send it as a token query parameter, but a header keeps it out of logs:

https://api.teslemetry.pro/api/business/products?token={token}

Keys start with api.. Keep them on your servers.

What a key can reach

A key can reach only the vehicles and energy sites your customers have shared with your business, and only while they share them. Each request names one product in its path, by VIN or energy site id.

What a request may do follows the permissions you chose at setup:

• Reading vehicle data needs vehicle access. Reading energy site data needs energy site access.
• Commands need command access for that product type. See Commands.
• Apart from commands, a key changes only streaming config and your business's own webhook and products.

First request

1. List your consented products to find the VINs and energy site ids your customers share.
2. Read a vehicle or an energy site.
3. Set up streaming or a webhook to receive data as it changes.