A practical route from your catalog to API integration.
An HTTPS JSON API that connects to your backend. Start with the vehicles and wheel workflows that matter to your business.
1. Define the workflow and review coverage
Tell us whether customers start with a car, a wheel or a complete set. Include the makes, generations, year ranges, product fields and expected request volume you need.
2. Agree company access
Our team creates the company account and configures access status, shared minute/day quotas and key IP allowances. Save the key securely: the full value is shown once on issuance.
- Authenticate with X-API-Key or Authorization: Bearer.
- Make your first request from the server running the integration; its IP is registered automatically.
- Company access and billing status are currently managed by the administrator.
3. Build the selector and map results
Fetch the vehicle catalog, use the returned slugs for fitment requests, and map the response to your stock. Width-specific ET ranges and complete staggered pairs are important when applying compatibility rules.
- Consult the API guide and downloadable OpenAPI specification.
- Handle empty results as a successful search with no matches.
- Keep keys out of browser JavaScript, mobile bundles and repositories.
4. Test, monitor and maintain
Test representative vehicles, mixed diameters and axle bores. Handle 400/403/404/429 responses deliberately, respect Retry-After, and review corrections that affect cached results.
- Cache brand/model lists on your backend to reduce quota usage.
- Choose a fitment cache lifetime with your team; there is no push invalidation API today.
- Version v1 is in the request path. Agree changes and operational requirements with us.