FAQ

Frequently Asked Questions

Everything you need to know before getting started with the Tire Size API.
300+
Free requests/day
99.9%
Uptime target
4
Pricing plans
24h
Support response
General
Overview of the Tire Size API and who it's built for.
  • Provides accurate, up-to-date tire fitment data for vehicles across a wide range of makes, models, years, and trims
  • A single request returns the exact OEM tire specifications for any supported vehicle — including tire size, load index, and speed rating
  • Built for tire retailers, automotive platforms, fleet management systems, and e-commerce stores that need reliable fitment data without building their own database
  • Tire retailers — power your "find tires by vehicle" search widget
  • E-commerce platforms — filter and recommend tires for any vehicle
  • Fleet managers — automate tire spec lookups across a mixed fleet
  • Automotive apps — add fitment data without a database of your own
  • Developers — integrate tire data into any product via a simple REST API
  • Yes — visit our live API demo to run real searches by vehicle or tire size without creating an account
  • The Free tier gives you 300 requests per day at no cost — no credit card required
  • All responses are in JSON format over HTTPS — standard REST conventions
  • Full OpenAPI 3.0 spec available in both YAML and JSON — import directly into Postman, Insomnia, or any code generator
  • We target 99.9% uptime — check real-time status at /api/health
  • Enterprise customers can request a custom SLA — contact us to discuss
  • Help Center — step-by-step guides and troubleshooting for common issues
  • Contact form — we respond within 24 hours
  • /api/health — check if there is an ongoing incident
Tip: Check the Help Center first — most authentication and 404 issues are solved there in under a minute.
Pricing & Plans
Everything about plans, billing, limits, and cancellation.
Free
$0 / month
300 req/day
Growth
Paid
5,000 req/day
Premium
Paid
200K req/day
Enterprise
Custom
50K+ req/day
  • Completely free — no credit card required
  • 300 requests per day, resetting at midnight UTC
  • Designed for development, testing, and small projects
  • Upgrade any time from your dashboard when you need more volume
Note: The Free plan is also rate-limited per IP. For production use, upgrade to Growth or higher.
  • You'll receive a 429 Too Many Requests response for any requests over your limit
  • Quota resets at midnight UTC automatically — no action needed
  • Monitor usage from your dashboard or upgrade to avoid interruptions in production
  • Billed monthly on the date you first subscribed
  • Receipt sent by email after each charge
  • View full billing history in your account dashboard
  • Cancel anytime from your dashboard under Plans → Cancel Subscription
  • Keep your current plan access until the end of the billing period — no immediate cutoff
  • Account reverts to the Free tier automatically after the period ends
  • Go to your dashboard and click Plans
  • Upgrades take effect immediately
  • Downgrades apply at the start of the next billing cycle — you keep current limits until then
  • Refund requests are evaluated case by case
  • If you were charged in error or experienced significant downtime on our side, contact us and we'll make it right
  • We consider discount requests on a case-by-case basis
  • Reach out with a brief description of your project and we'll see what we can do
Technical
Authentication, integration, caching, and developer tools.
  • Pass your API key as a request header: x-api-key: YOUR_API_KEY
  • Do not include it as a URL query parameter — it will be rejected
  • Get your key from your account dashboard under the API Key tab
  • Works with any language that can make HTTP requests — it's a standard REST API
  • Our API docs include ready-to-use examples for JavaScript, Python, and cURL
  • The OpenAPI spec can auto-generate client code for Go, PHP, Ruby, Java, C#, and more via OpenAPI Generator
  • Technically yes, but strongly not recommended
  • Client-side calls expose your API key in the page source — it can be scraped and abused
Best practice: Proxy requests through your own backend. Your backend holds the key, the browser never sees it. This also lets you add your own caching layer.
  • CORS is enabled for registered domains
  • Need a specific domain added? Contact us with your domain and we'll add it to the allowlist
  • Direct client-side API calls are not recommended for security reasons (see above)
  • Tire fitment data changes rarely — caching is highly recommended
  • Lookup lists (all makes, years, widths) — cache for 24 hours or longer
  • Vehicle fitment data — cache for 7 days safely
  • Caching reduces daily request usage, speeds up your app, and prevents hitting rate limits during traffic spikes
  • OpenAPI YAML — import into Postman, Insomnia, etc.
  • OpenAPI JSON — for automated pipelines and code generators
  • Explore and test all endpoints interactively in our Swagger UI directly in the browser
  • Production: https://tire.vdim.app/api/v1
  • Documentation: https://tire.vdim.app/api/docs
  • Health check: https://tire.vdim.app/api/health
  • All endpoints require HTTPS — HTTP requests are not accepted
  • All error responses use a consistent JSON structure: { "error": "...", "status": 401, "timestamp": "..." }
  • 401 — invalid or missing API key
  • 404 — no data found for that vehicle
  • 429 — daily rate limit exceeded; wait until midnight UTC or use exponential backoff
  • 500 — server error; retry after a short delay — these are transient
Data & Coverage
What's in the database, how accurate it is, and how to handle gaps.
  • Covers passenger vehicles, SUVs, and light trucks for the North American market
  • Use /search_allmake to get the full list of supported makes
  • Use /year_range?make=Toyota to check year coverage for a specific make
  • Reflects OEM (Original Equipment Manufacturer) specifications — the sizes vehicles ship with from the factory
  • Data is sourced and verified from manufacturer documentation
  • Found a discrepancy? Report it and we'll investigate and correct it
  • Updated as new model year data becomes available — typically annually for new model years
  • Ongoing corrections and additions throughout the year
  • Follow our blog for update announcements and new endpoint releases
  • No — the API covers OEM fitment data only (what the vehicle came with from the factory)
  • Does not include aftermarket wheel sizes, lifted fitments, plus-sizing recommendations, or winter tire packages
  • This scope keeps the data reliable and unambiguous
  • Use /search_allmake to confirm the exact make spelling — spelling and spacing matter (e.g. Land Rover not Land-Rover)
  • Try omitting the trim parameter to get all trims for that model
  • If the vehicle is genuinely missing, contact us with the year, make, model, and trim — we'll prioritize adding it
  • Different trim levels often ship with different wheel and tire sizes
  • Example: a base LE trim may use 17" wheels while the XSE uses 18"
  • The API returns all trims — always filter by trim for accurate fitment data
  • 235 — section width in millimeters (how wide the tire is)
  • 45 — aspect ratio (sidewall height as % of width)
  • R — radial construction
  • 18 — wheel diameter in inches
  • The API returns separate fields (width, aspectRatio, diameter) as well as the combined tireSize string

Ready to get started?

Sign up free — no credit card required. 300 requests per day on us.

Create Free Account Visit Help Center