Webhook

Your business has one webhook. Teslemetry posts telemetry from every vehicle your customers share with you to its URL. You set it on the Webhook page, or with the API.

A vehicle sends telemetry only for the fields in its streaming configuration. See Vehicle config.

Settings

• URL - where Teslemetry posts each message. It must be reachable from the internet: localhost, .local names and private or reserved IP addresses are refused. https:// is recommended; http:// is allowed, but delivery is then unencrypted.
• Authorization header - optional. Sent as the Authorization header with every message, for example Bearer <your secret>. Use it to check that a message came from Teslemetry. It is never shown again after you save.
• Format - Teslemetry, Tesla or Splunk HEC. See Webhook payloads.
• Enabled - turn delivery off without deleting the webhook.
• Verify certificate - check the TLS certificate of your URL. Leave it on unless your server uses a self-signed certificate.

Saving replaces the whole webhook, including its Authorization header. To keep a header, enter it again; leave the field empty to remove it.

Only admins can change or delete the webhook.

Last delivery

The Last delivery card shows the outcome of the most recent delivery to the saved webhook: delivered or the failure reason, with the HTTP status when there was one, and when it was sent. It also shows the time of the last success, the number of consecutive failures, and the last error message while deliveries are failing. It says when the webhook is disabled, and shows No deliveries yet. until the first delivery is recorded.

Delivery

Each message is sent once, as an HTTP POST with a JSON body. If your server is down or answers with an error, that message is not sent again. Teslemetry does not disable a business webhook after failed deliveries.

Delivery for a product stops when the customer stops sharing it, or when you remove it.