SoloCatalog.com

The catalogue, through your API

VIN and frame decoding, model browsing, parts searches, diagrams, callouts and applicability use the same catalogue data and coverage as the website. Every account includes 100 free API requests to try it, with no card. Every paid subscription includes API access and shares its search allowance with registered website embeds.

Get a free API key Subscription plans

Authentication

Sign in with Google and create a secret key under My account → SoloCatalog API. The first 100 requests of an account are free; after that the key needs a subscription. Save it when it is first shown. Send it from your server in the Authorization header. Test keys work only in the test billing environment; website embed keys cannot authenticate API calls. Revoke unused keys in your account.

Decode a VIN or frame

curl https://solocatalog.com/api/v1/vin/decode \
  -H "Authorization: Bearer $SOLOCATALOG_API_KEY" \
  -H 'Content-Type: application/json' \
  -d '{"vin":"JTNBF4FK0D3000000","lang":"en"}'

This synthetic VIN is a documentation example; catalogue coverage varies. Languages: en, az, ru. Supply VIN/frame identifiers as 5–40 letters, digits or hyphens.

Quick lookup

POST /api/v1/lookup accepts a JSON body. Each mode returns the same supported catalogue results used by SoloCatalog’s partner integration:

ModeBodySearch units
Search parts by VIN{"vin":"YOUR_VIN","q":"brake"}2 (decode + search)
Find model candidates{"mode":"models","brand":"Toyota","q":"Camry 70"}0
Search a selected model{"model":"MODEL_KEY","q":"brake"}1
List diagrams{"mode":"diagrams","vin":"YOUR_VIN"}1 (decode)
Get diagram parts{"mode":"diagram","model":"MODEL_KEY","diagram":"FIGURE_ID"}0

Use model keys returned by mode: models. Queries are limited to 80 characters, model keys to 200. Optional lang uses the languages above. Model candidates require fitment verification, just as on the website.

Full catalogue access

For the website’s complete catalogue operations, replace an existing catalogue URL’s /api/ prefix with /api/v1/catalogue/. Preserve the query string. Send your Bearer key on every request, including images. JSON responses rewrite relative catalogue links to authenticated API URLs.

GET /api/v1/catalogue/catalogues/toyota/models
GET /api/v1/catalogue/catalogues/toyota/specifications?model=CAMRY
GET /api/v1/catalogue/catalogues/bmw/models
GET /api/v1/catalogue/catalogues/bmw/models/{modelId}/open
GET /api/v1/catalogue/catalogues/bmw/models/{modelId}/parts/search?q=brake
GET /api/v1/catalogue/epc/{region}/{groupCode}/figures
GET /api/v1/catalogue/epc/{region}/{groupCode}/figures/{figureNumber}
GET /api/v1/catalogue/epc/{region}/{groupCode}/parts/{partId}/applicability

Keep all vehicle, configuration, production-date and applicability query parameters returned by decoding or used by the website. IDs and available operations vary by brand and source release. Diagram responses retain callouts, part rows and image links; image URLs return their original binary content type. The convenience lookup returns a smaller result summary.

Supported route families include the enabled brand model catalogues, VIN-scoped figures and parts, Toyota EPC, native and local diagrams, Mitsubishi Japan frames, and legacy vehicle/assembly routes where deployed. Account, admin, billing, partner credentials and security endpoints are excluded.

Mitsubishi frame decoding is also available as POST /api/v1/catalogue/mitsubishi/japan/frames/decode with {"frame":"CU2W-0000000"}. Use X-Catalog-Lang: en (or az/ru) for full catalogue requests.

Shared limits and billing

Starter, Growth, Pro and agreed Enterprise quotas remain the existing subscription quotas. VIN/frame lookups and part-number/name searches consume the same monthly counter as website embeds. Browsing, diagrams, image downloads and callouts consume no search units. Accepted searches consume their units when admitted, including no-match results and downstream failures, matching existing embed accounting. Validation rejected before admission does not consume units.

Free requests. While an account has no active subscription, each API request of any kind counts as one of its 100 free requests (up to 20 a minute). They do not renew. Responses carry X-Search-Plan: free, and when they are used the API answers 402 with a link to the plans.

Subscriptions. Searches pause at the subscription allowance; browsing remains available while the subscription is active. All API requests share a per-minute rate limit across the account’s keys (default 60). The allowance resets at the subscription billing-period boundary. Cancellation takes effect according to the existing paid-through subscription period. Without an active subscription only the free requests are available. No API surcharge or automatic overage charges.

Responses include X-Search-Limit, X-Search-Remaining and X-Search-Reset (UTC, subscriptions only). Concurrent responses show a snapshot at admission.

StatusMeaning
400Invalid request
401Missing, wrong, revoked or wrong-environment API key
402Free requests used, or active subscription required
404Unsupported operation or catalogue record unavailable
429Shared search quota or per-minute rate limit reached; rate responses include Retry-After
5xxTemporary catalogue or service failure

Use the API from your backend. Do not put secret keys into browser JavaScript, image tags, query strings or embed snippets. Responses are private and should not be cached publicly.

AI assistants (MCP)

The same lookups are available to AI assistants through the Model Context Protocol. Add https://solocatalog.com/mcp as a custom connector (Streamable HTTP). Light use needs no key; send your API key as Authorization: Bearer YOUR_API_KEY to count calls against your subscription instead of the free allowance. Tools: decode_vin, search_parts, find_models, list_diagrams, get_diagram_parts, lookup_part_number. Connector guide

Manage API keys and usage · Plans · Browse the catalogue · Support