Comparison of API version 1 and API version 2
|Wheel Size Data|
|The returning wheel fitment data is the same for both versions of the API|
Market - The global automotive market in which the same vehicle has some differences in wheel fitment params.
If you have been unable to find the information on the requested market, try using the car’s details taken from the key markets.
Region - The global automotive region in which the vehicle was officially sold or is currently being sold officially.
Please check this webpage for details
List of regions we cover:
Notes:You can also check what countries are behind the name of region by checking this webpage or using /v2/regions/ API method. All endpoints excluding /v2/search/by_model/ support multiple regions filtering, example: ®ion=eudm®ion=russia®ion=jdm&...
|/upsteps/ API method|
|Get all possible rim and tire combinations based on pre-fitted original
equipment (OE) wheel specs.
Wheel Fitment Calculator is a great demo how you can use it and offer your customers safe replacement options based on factory sizes.
Note All unavailable options on the tire market are filtered out from result.
|TiresVote.com - The world's largest database of tire information: ratings,
professional tire tests, bestseller lists.
Summary of each tire model.
See TiresVote.com OpenAPI
|Meta information in responses|
|Using for SEO|
|See details how you can use Wheel Fitment API for SEO.|
|API methods inheritance||
/v1/search/by_model/, /v1/vehicles/ =>
/v2/regions/ - new
Wheel Fitment API version 1 is deprecated effective November 1, 2021
/v1/of Wheel Fitment's API, and we're focusing on delivering a more consistent experience with this update. With more exciting changes to come, you can expect more thoughtful design and uniformity moving forward.
With that in mind, as of November 1, 2021 the Wheel Fitment version 1 API is deprecated, and in accordance with the our REST API policy, all version 1 APIs will be removed on July 1, 2023.
What will happen if I do nothing?
/v1/APIs were removed, any apps or services still using 1.0 resources will not work. If you rely on a script, integration, or app that makes requests using
/v1/resources, you'll need to update it to use a
/v2/alternative as soon as possible.
We Want Your Feedback