API Authentication and Webhooks

This FAQ covers how to authenticate with the Teslemetry API and configure webhooks for receiving real-time data.

Frequently Asked Questions

How do I authenticate API requests to Teslemetry?

Teslemetry supports two methods for authenticating API requests:

Method 1: Bearer Token (Recommended)

curl --header "Authorization: Bearer {token}" 'https://api.teslemetry.com/api/1/vehicles/{vin}'

Method 2: URL Parameter

https://api.teslemetry.com/api/1/vehicles/{vin}?token={token}

Both methods are equally valid, but the Bearer token method is preferred for production applications as it keeps your token out of server logs.

Where do I get an access token?

Access tokens are created in the Teslemetry console:

Go to teslemetry.com/console
Scroll to the Access Tokens section
Click Add Token to create a new token

You can create up to 10 access tokens and remove them at any time.

What is the API endpoint?

The base API endpoint is:

https://api.teslemetry.com/api/1/

Full API documentation is available at api.teslemetry.com/docs.

Why does my webhook keep getting disabled?

Webhooks are automatically disabled if your server fails to return a 2xx status code for 24 consecutive hours. This prevents Teslemetry from wasting resources sending data to an unresponsive endpoint.

To prevent webhook disabling:

Ensure your server returns HTTP 200-299 for successful deliveries
Implement proper error handling to avoid 5xx responses
Monitor your webhook endpoint's health

What events can I receive via webhooks/streaming?

Event Type	Description
`data`	Telemetry data updates (battery, speed, location, etc.)
`state`	Vehicle state changes (online, asleep, driving)
`vehicle_data`	Full vehicle data responses
`errors`	Error events from the vehicle
`alerts`	Alert notifications (sentry mode, etc.)
`credits`	API credit usage updates

SDKs Available

Python SDK

TypeScript/JavaScript SDK

Updated on: 01/02/2026

Was this article helpful?

Thank you!