# A REST vehicle command now requires the Tesla Vehicle Command protocol on except fleet accounts and pre-2021 Model S/X

Calls to POST /api/1/vehicles/{}/command/* on Tesla Fleet API stopped working on January 1, 2024.

On January 1, 2024, vehicle command endpoints changed to require the Tesla Vehicle Command protocol. Calls to POST /api/1/vehicles/{}/command/* fail after this date. This change affects all requests except fleet accounts and pre-2021 Model S/X.

## What to use instead

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.

- 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
- Calls it hits: `POST /api/1/vehicles/{}/command/*`
- Who it affects: except fleet accounts and pre-2021 Model S/X
- Source: [Announcement](https://developer.tesla.com/docs/fleet-api/announcements)
- Verified: October 26, 2026, against Tesla Fleet API's own pages
- Page: https://www.okapi.bot/providers/tesla-fleet-api/breaking-changes/a-rest-vehicle-command-now-requires-the-tesla-vehicle-command-protocol-on/

## Tesla Fleet API's words

> All vehicles* will require Tesla Vehicle Command protocol. The REST API will be fully deprecated

Okapi finds the calls this change hits in your repo and opens the pull request with the fix: https://github.com/apps/okapi-agent