Smartcar API
GET /v2.0/compatibility endpoint removal
Stopped workingSubscribe to Smartcar APIShare
On September 15, 2026, the endpoint GET /v2.0/compatibility was removed. Calls to this endpoint fail since that date and return 410 Gone.
Calls it hits
GET /v2.0/compatibility
What to use instead of these calls
To confirm compatibility, connect the vehicle through Smartcar Connect, where the exact signals and commands supported are reported from real platform activity.
In Smartcar API's words
`GET /v2.0/compatibility` (Compatibility by VIN) will be removed on **September 15, 2026**. After that date, requests return `410 Gone`.
Facts
- API
- Smartcar API
api.smartcar.com - Kind
- Endpoint removal
- Takes effect
- September 15, 2026
- Calls after that day
- Fail
- Source
- Changelog
- Last updated
- Verified
- , against Smartcar API's own pages
Questions
When does this change take effect?
Calls to GET /v2.0/compatibility on Smartcar API stopped working on September 15, 2026.
What happens to calls after September 15, 2026?
They have failed since September 15, 2026.
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.
More from Smartcar API 1
-
/v2.0/*Version retirement Stops workingin 25 days
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.