The Tesla API went paid: what actually broke in Teslamate in June 2026

Two pieces of news that merged into one

On 13 June 2026 the chat picked up the news that Tesla was moving third-party access to the car onto a paid Fleet API subscription, around 10$ a month (#460334, #460338, #460340). The reaction matched, down to “so that’s how Elon made his trillion”.

Overnight into 14 June half the owners lost Teslamate (#460818, #460820). A day apart, one subject, an obvious connection. So the connection was drawn (#460405). The post-mortem in the Teslamate repository showed that two different stories had coincided in time.

Symptoms

The container log carried lines of this sort:

[info] GET https://owner-api.teslamotors.com/api/1/vehicles/<id> -> 403 (64 ms)
[warning] TeslaApi.Error / %{"error" => "forbidden, see https://developer.tesla.com/docs/fleet-api", "error_description" => "", "response" => nil}
[error] Error / :unknown

The error text pointed at the Fleet API itself, so the subscription theory looked proven straight from the log. The ticket was opened on 13 June under the title “TeslaApi.Error 403 on v4.0.0” (issue #5399). MQTT connected normally throughout, the car simply disappeared from the interface.

What it turned out to be

The problem sat in authorisation. The maintainers’ working version: Tesla’s token server stopped serving clients that arrive without HTTP/2 and TLS 1.3, and threw 403 on a refresh token renewal. The fix came down to one thing, forcing HTTP/2 with TLS 1.3 on the auth host.

The timeline from the repository:

1. 13 June, 12:17 UTC, release v4.0.0 came out, the one many people updated to while trying to fix themselves.
2. 13 June, 20:32 UTC, issue #5399 filed with the 403.
3. 14 June, 07:43 UTC, issue #5405 “Enforce HTTP/2 and TLS v1.3 for Tesla Auth API” closed.
4. 14 June, 16:33 UTC, PR #5406 “fix: enable HTTP/2 and set TLS to 1.3 for TESLA_AUTH_HOST” closed.
5. 14 June, 17:09 UTC, release v4.0.1 published, with the maintainers stating that it closes the refresh token problem.

Less than a day passed from the first report of the breakage to a stable release, and nobody paid Tesla anything for it.

How people patched around it in the meantime

While there was no release, the chat passed around a CI image built straight from the pull request: ghcr.io/teslamate-org/teslamate:pr-5406 (#460820, #460825). It worked. A day later v4.0.1 came out and it was time to leave the PR image; the Teslamate documentation on testing CI images asks for exactly that in a sentence of its own.

For some owners the car still did not come back after the update. Recreating the tokens helped: /settings, Sign out, enter the tokens again (#460827).

What to do now if you run your own Teslamate

Check the container version. Anything older than v4.0.1 catches the same 403, because the TLS fix is simply not in there.

Check the image tag. If the compose file still says pr-5406, replace it with a normal release tag. By September 2026 the line has moved on considerably: v4.1.0 and v4.1.1 from 14 August, v4.2.0 from 23 August.

If the 403 stays after the update, log out and create the tokens again. It is the first thing to rule out and it takes two minutes.

Read the log rather than the interface. An empty Grafana graph looks the same for any breakage, while the line with the response code in docker logs teslamate separates three different cases at once: a 403 from owner-api means an authorisation problem of exactly this type, a 401 usually means an expired token, and timeouts or no requests at all point to the network or to a sleeping car. Without that line diagnostics turns into guessing at versions, which is what that June day in the chat was spent on.

The paid Fleet API on its own terms

Tesla charges for the Fleet API by request volume, and the conditions sit in the billing and limits section of the developer portal. The “10$ a month” figure from the chat on 13 June comes from participants’ words, nobody attached an official price list to it, and it should not be put into calculations.

What is worth holding in mind: the owner API that self-hosted Teslamate lives on is documented nowhere by Tesla and carries no obligations towards third-party clients. The June story showed that plainly. Any change on Tesla’s side can break it, down to TLS settings on a single host, and there will be no warning.

If you use Teslamate as a data source for checking the battery or the mileage, it helps to know where its numbers end. Battery diagnostics with the car’s own tools is covered in the write-up on Battery Test in Service Mode; on Tesla subscriptions living a life of their own in the region there is the piece on Premium Connectivity.