Tesla Fleet API
A REST vehicle command now requires the Tesla Vehicle Command protocol on except fleet accounts and pre-2021 Model S/X
Stopped workingSubscribe to Tesla Fleet APIShare
On January 1, 2024, vehicle command endpoints changed to require the Tesla Vehicle Command protocol. Calls to POST /api/1/vehicles/{id}/command/* fail after this date. This change affects all requests except fleet accounts and pre-2021 Model S/X.
Calls it hits
POST /api/1/vehicles/{id}/command/*
What to use instead of these calls
Send commands through the Tesla Vehicle Command protocol instead. You can sign requests with the vehicle-command SDK or route them through its tesla-http-proxy.
In Tesla Fleet API's words
All vehicles* will require Tesla Vehicle Command protocol. The REST API will be fully deprecated
Facts
- API
- Tesla Fleet API
fleet-api.prd.na.vn.cloud.tesla.com - Kind
- Behaviour change
- Announced
- November 17, 2023
- Takes effect
- January 1, 2024
- Calls after that day
- Fail
- Who it affects
- except fleet accounts and pre-2021 Model S/X
- Source
- Announcement
- Last updated
- Verified
- , against Tesla Fleet API's own pages
Questions
When does this change take effect?
Calls to POST /api/1/vehicles/{id}/command/* on Tesla Fleet API stopped working on January 1, 2024.
What happens to calls after January 1, 2024?
They have failed since January 1, 2024.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.