// GET /v1/tires · stable
The whole fitment, one call.
- 235/60R18
- front_size and rear_size on the reference CR-V.
- 33 / 30 psi
- recommended front and rear pressures.
- 103 H
- load index and speed rating.
- 400 CCA
- battery cold-cranking amps.
The whole fitment, one call.
Sizes, pressures, load index and speed rating come back together, with the battery's CCA, for the exact config.
curl 'https://vinspeclookup.com/api/v1/tires?vin=5J6RW2H82KL000007' \ -H 'Authorization: Bearer otp_live_…'{
"object": "tires",
"config": {
"config_key": "2019_honda_cr_v_ex_l15be",
"year": 2019,
"make": "Honda",
"model": "CR-V",
"trim": "EX",
"engine": "1.5L L15BE 4cyl",
"drivetrain": "4WD"
},
"tires": {
"battery_cca": 400,
"front_size": null,
"is_run_flat": null,
"is_staggered": false,
"options": [
{
"aspect_ratio": 60,
"is_oem_standard": true,
"load_index": 103,
"pressure_front_psi": 33,
"pressure_rear_psi": 30,
"rim_diameter_in": 18,
"size_front": "235/60R18",
"speed_rating": "H",
"wheel_spec": "7.5Jx18 ET45",
"width_mm": 235
},
{
"aspect_ratio": 65,
"is_oem_standard": false,
"load_index": 104,
"pressure_front_psi": 32,
"pressure_rear_psi": 30,
"rim_diameter_in": 17,
"size_front": "235/65R17",
"speed_rating": "H",
"wheel_spec": "7.5Jx17 ET45",
"width_mm": 235
}
],
"pressure_front_psi": 32,
"pressure_rear_psi": 30,
"rear_size": null,
"source": "https://www.wheel-size.com/size/honda/cr-v/2019/"
},
"meta": {
"generated_at": 1792323140145
}
}Pressures, load, speed, flags.
The console's structured view of the same response: the flags as chips, the figures as cells, the factory options as rows.
2019 Honda CR-V EX
complete92% filledSquare, staggered, run-flat.
Three booleans drive three chips. The legend below is the render's own chip set with the field that sets each one.
The flags exist so a screen never has to parse a size string to know what to do. A rotation pattern, a replacement rule and a spare-tire prompt each read one boolean. The sizes, pressures, load index and speed rating stay as separate fields for the same reason: a tire shop's order form wants them one per box, and a listing page wants them in one line, and both come from the same response.
// IN USE
Where the fields land.
Three places this response ends up, drawn the way the homepage draws its data groups. Every value in the pictures is from the sample above.
A tire shop order
front_size, rear_size, pressures, load index and speed rating fill the order form one field per box.
The fitment line on a listing
The size buyers ask about first, printed under the trim without anyone typing it.
A fitment quote
Four of the right size, the pressures to set, and the battery CCA for the test, from one call.
// QUESTIONS
Details.
- Does it cover optional wheel packages?
- options[] lists every factory fitment for the config with is_oem_standard marking the default. Aftermarket sizes are out of scope.
- What does is_staggered mean?
- Different sizes front and rear. is_run_flat marks run-flat fitment. Both are booleans so a UI can show a chip without parsing sizes.
- Why is the battery here?
- Because a tire shop is usually also the place a battery gets tested. battery_cca sits in the tires group and in the spec sheet.
- Can I get the fitment by year/make/model?
- Yes, and if the model has more than one fitment across its configs the API answers 409 with the candidate config_keys instead of guessing. Pass a trim, or pick a config_key, and the call returns the fitment for that exact car.
// TRY IT
Run this response yourself.
Every window on this page is the sandbox's answer for the reference vehicle. Open the console, pick /v1/tires, and run it with no key. Ready for live data across any vehicle? Request access.