The Compatibility API is an Enterprise feature. Please contact us to upgrade your plan.
- The vehicle supports the feature (e.g., a Ford Escape supports /fuel but a Mustang Mach-e does not)
- Smartcar supports the feature for the vehicle’s make
capabilities
for VINs in Canada and Europe.
Request
HeadersThe HTTP Authorization header using the Basic authentication scheme.To construct the Authorization header value:
- Join your
client_id
andclient_secret
with a single colon (:
). - Base64-encode the resulting string:
base64({client_id}:{client_secret})
- Prepend
Basic
(with a trailing space) to the encoded string.
Basic bXktY2xpZW50LWlkOm15LWNsaWVudC1zZWNyZXQ=
The VIN (Vehicle Identification Number) of the vehicle.
A space-separated list of permissions.
An optional country code string according to ISO 3166-1 alpha-2.
Response
true
if the vehicle is likely compatible, false
otherwise.One of the reasons described below if compatible is
false
, null
otherwiseAn array containing capability objects for the set of endpoints that the provided scope value can provide authorization for.
This array will be empty if
compatible
is false
.A vehicle’s compatibility depends on many factors such as its make, model, model year, trim, etc. The API optimizes returning false positives.