From a vehicle picker in your first wheel store to compatibility across a large B2B catalog. Every plan includes both lookup directions; capacity, integration assistance and support determine the scope.
A straightforward way to add vehicle compatibility to your store.
Monthly access · agreed quote
Discuss Start ↗More capacity and closer support for an active online store.
Monthly access · agreed quote
Discuss Business ↗A fitment workflow shaped around your catalog and business processes.
Individual proposal
Discuss your integration ↗Access to the vehicle catalog, vehicle-to-wheel specifications and wheel-to-vehicle matching through the v1 JSON API. Results include PCD, diameter, width, offset ranges and axle center bores where available in the catalog, with support for same-width and staggered setups. The public finder and API use the same effective fitment rules.
We agree minute and day quotas for your company before activation. All of your company’s API keys share those quotas; issuing another key does not increase your allowance. IP allowances are configured per key. We review traffic expectations, caching and the number of integration servers when choosing the configuration.
If a request exceeds its quota, the API returns HTTP 429. Your integration should handle the response and respect Retry-After. A higher quota is agreed with our team; exceeding a limit does not automatically purchase an upgrade.
The recurring fee covers the agreed API access and support. Building a selector, mapping your product catalog, connecting a commerce platform or developing a custom workflow is scoped and quoted separately. We confirm the price, quotas, billing period and implementation deliverables before activation. Sending an access request does not start a paid subscription.
Start includes documentation and basic integration guidance. Business adds launch review and priority handling of support requests. Custom lets us agree the support scope and operational requirements for your platform. Response times, service commitments and custom development are confirmed in the proposal; no fixed SLA is included by default.
Tell us which makes, model generations and year ranges your business needs. Coverage and available parameters vary by catalog entry. Compatibility data supports product filtering; physical clearance, wheel design or a modified vehicle may require separate verification. Product prices, warehouse stock and orders remain in your own system.
Yes. Contact us to agree the new quotas, support scope, price and activation date. Plan changes are handled by our team.
Use the public vehicle and wheel finders, then send us representative vehicles and your workflow. We will discuss coverage and any evaluation access before you commit.
We can scope implementation with TurtleDev, from reviewing product fields to building the selector and backend connection. This work is quoted separately from API access.
We consider expected API traffic, company quotas, key IP allowances, support needs and the implementation scope. Include these details in your request so we can propose a suitable plan.
Share your store or platform, expected traffic and the fitment workflow you need. We will agree the plan and integration with you.
Discuss API access ↗