Tire API v1.3.0 Changelog: Full Size Catalog & Reverse Lookup Quota
Tire API v1.3.0 ships a new endpoint for Business customers who want the entire tire-size catalog in one shot, plus a fairer, more sustainable quota model on reverse lookup. Here's everything that changed.
New Endpoint: GET /search_allsizes (Business)
Overview
Returns every distinct tire size in the database in a single cached call — no more drilling down through /search_allwidth and /by_size one dimension at a time. This is built for clients who want to ingest the full size list to power their own sizing engine or catalog.
Endpoint Details
- HTTP Method: GET
- Base URL: https://tire.vdim.app/api/v1
- Full Path: /api/v1/search_allsizes
- Authentication: x-api-key header
- Access: Business plan only — other tiers receive a
403 Business subscription required
What's In the Response
The payload is size strings only — there's no vehicle or fitment linkage attached, so it doesn't expose any of the proprietary size-to-vehicle mapping. It's purely the distinct list of tire sizes.
Caching
Responses are served with Cache-Control: public, max-age=3600 (1 hour); repeat calls within that window can return a 304.
Request Example
curl -H "x-api-key: your-business-key" "https://tire.vdim.app/api/v1/search_allsizes"
Quota
Usage is metered by its own monthly size-catalog quota — 500 calls/month on Business — surfaced via X-AllSizes-Quota-* response headers and in GET /api/v1/usage. Each call also counts against your regular daily request limit.
Reverse Lookup Gets a Monthly Quota
GET /api/v1/reverse_lookup (tire size → matching vehicles) is the direction of our API that exposes the proprietary fitment mapping, so as of v1.3.0 it carries a per-tier monthly quota in addition to the existing daily limit.
To be clear about intent: these are generous, competitive ceilings — benchmarked against the market's established size-first fitment tools — not tight caps. A legitimate fitment app doing size-first lookups shouldn't come close to hitting them.
| Plan | Monthly Reverse-Lookup Quota | Trial Bonus (New Signups) |
|---|---|---|
| Free | 100 | 50 (one-time, consumed first) |
| Starter | 5,000 | — |
| Pro | 20,000 | — |
| Business | 60,000 | — |
What's Not Affected
GET /by_vehicle/tiresize (vehicle → tire sizes) — the core, everyday lookup direction most consumer-facing tools use — is untouched. It stays on the daily request limit only, with no monthly cap.
Quota Headers
Every reverse_lookup response now includes:
X-RevLookup-Quota-LimitX-RevLookup-Quota-RemainingX-RevLookup-Quota-Reset
When the quota is exhausted, you'll get a 429 with an upgrade message. Quotas reset on the first of each month, America/Toronto time.
GET /api/v1/usage now returns both a reverseLookupQuota block and an allSizesQuota block, alongside the existing vinQuota block from v1.2.0.
Why We're Doing This
Reverse lookup is the direction that could, in principle, be swept systematically to reconstruct our fitment database. The monthly quota is one small, generous guardrail among several — it's not the primary control. The main protections are our updated Terms of Use, which now include a clause prohibiting bulk extraction and dataset reconstruction, plus internal monitoring for unusual enumeration patterns. If you're building a normal, size-first fitment experience, none of this should be visible to you day to day.
Docs & Spec Updates
- OpenAPI spec bumped to 1.3.0 with full
/search_allsizesdocumentation and the newreverse_lookupquota details (headers and error responses), importable asopenapi.yaml/openapi.jsoninto Postman or Insomnia - The in-app
/api/v1/docsJSON is updated with both endpoints and reflects version 1.3.0 - The README's endpoint list and rate-limit section are updated to match
No Breaking Changes
v1.3.0 is fully backward compatible. If you're a Free, Starter, or Pro customer using by_vehicle lookups, nothing changes for you. If you use reverse_lookup heavily, check your new monthly headroom — but for size-first fitment use cases, the new ceilings are set well above normal usage.
Trying It Out
- API guide: https://tire.vdim.app/api/docs
- Swagger UI: https://tire.vdim.app/api/docs/v1
- Sign up: https://account-tire.vdim.app/signin/signup
Support & Resources
Need help? Contact support at support@vdimtech.com or visit the API portal at https://tire.vdim.app for interactive documentation.
Conclusion
v1.3.0 is about giving Business customers a faster path to the full size catalog while keeping the fitment mapping data fair to access for everyone. Give /search_allsizes a try if you're building a sizing engine, and let us know how the new quotas feel in practice.