API Terms of Usage

These terms apply to every subscription to the Wheel Fitment API and the Wheel Configurator API provided by WHEEL SIZE KZ LLP. Read them carefully — subscribing or using an API key constitutes acceptance.

Wheel Fitment API terms

1. Restriction against competitive use

A subscription to the API cannot be used to build a competing enterprise — websites or applications that replicate Wheel-Size.com's scope or functionality — whether developed directly by the subscriber or through third parties.

2. Data-usage limitations

Extracting or using data from the Wheel-Size.com database via the API to enhance third-party datasets, or for data recompilation and redistribution, is prohibited. See the SEO & data-parsing policy below for the narrow, permitted exception for Cataloging API methods.

3. No resale

The API provided by developer.wheel-size.com cannot be resold under any circumstances.

4. Service-access rights

The provider reserves the right, at its discretion, to suspend or terminate API access in the event of violation of these terms, infrastructure overload beyond the agreed plan limits, or any usage that negatively affects service performance for other subscribers.

5. Confidentiality of access credentials

API keys must be kept confidential. Sharing API keys with any third party is not permitted.

6. Personal licensing

Each license is personal. Affiliates and associated parties must obtain their own subscriptions and API keys.

7. Human-initiated API calls

Important

Search API calls must be initiated by human users — website visitors or application users. Robots, crawlers, spiders and any automated scripts are prohibited from initiating Search calls. See the SEO & data-parsing policy for the list of affected endpoints.

8. Scope of subscription

Each subscription to the Wheel Fitment API covers use across all websites and applications operated by the subscribing company. (Note: this differs from the Wheel Configurator API — see the appendix below.)

Disclaimer

WHEEL SIZE KZ LLP independently operates the Wheel Fitment API and specialises in wheel fitment information. The company is not affiliated with, associated with, authorised by, endorsed by, or officially connected to any of the vehicle manufacturers whose logos may appear on this website or in API responses.

All trademarks, registered trademarks, product names and company names mentioned anywhere in our service belong to their respective holders.

Wheel Configurator API — additional terms

The Wheel Configurator API generates composite images of vehicles fitted with user-supplied rims using imagery licensed from EVOX. The following additional terms apply to every Configurator subscription.

The EVOX logo displayed on every image generated through the Configurator API must remain intact and visible at all times. It cannot be altered, resized beyond its original placement, covered, or obscured.

User-initiated API calls

Calls to the Configurator method ../fit/, which generate vehicle images with specified rims, must be initiated by legitimate end-users. Automated systems — including search robots, crawlers, spiders and parsing scripts — are prohibited from calling this endpoint.

Subscription limitations

Each Configurator subscription permits use on a single website or application. Multiple platforms each require their own subscription — for example, two websites require two subscriptions.

SEO & data-parsing policy

We understand that SEO teams want to generate landing pages from our data (vehicle makes, models, years). API v1 handled this bluntly — keys were automatically disabled when request volume looked like parsing. API v2 makes the policy explicit by splitting methods into two groups.

Cataloging methods — cacheable

The following endpoints can be saved locally for SEO purposes, within your plan's rate limits. Periodic re-fetching is recommended to keep data fresh:

  • /makes/
  • /models/
  • /years/
  • /generations/
  • /modifications/

Search methods — must be user-initiated

The following endpoints must be called only in response to a real user action (site visitor, application user). They must not be called by search robots, crawlers, spiders or parsing scripts:

  • /search/by_models/
  • /by_rim/search/
  • /by_rim/search/modifications/
  • /by_tire/search/
  • /by_tire/search/modifications/
  • /by_hf_tire/search/
  • /by_hf_tire/search/modifications/

The human-initiated-only rule also covers the Wheel Configurator ../fit/ method — see the Configurator appendix.