autodoc.co.uk APIautodoc.co.uk ↗
Access Autodoc's full auto parts catalog via API: browse car makers, models, engines, search parts, get specs, prices, OE numbers, and find compatible alternatives.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/70de51f9-9aaa-46f7-89f2-d9e784c78466/get_car_makers' \ -H 'X-API-Key: $PARSE_API_KEY'
Returns a list of all car manufacturers/makers available on Autodoc, grouped by popularity.
No input parameters required.
{
"type": "object",
"fields": {
"makers": "array of maker objects each containing id (integer), name (string), and group (string)"
},
"sample": {
"data": {
"makers": [
{
"id": 16,
"name": "BMW",
"group": "Popular carmakers"
},
{
"id": 121,
"name": "VW",
"group": "Popular carmakers"
},
{
"id": 5,
"name": "AUDI",
"group": "Popular carmakers"
}
]
},
"status": "success"
}
}About the autodoc.co.uk API
The Autodoc API covers 6 endpoints that expose the full Autodoc auto parts catalog, from vehicle hierarchy to part specifications. Starting with get_car_makers, you can walk the complete tree of manufacturers, models, and engine variants, then use search_parts to find components by keyword, part number, or article number — with results that include product titles, categories, and URLs ready for downstream detail lookups.
Vehicle Hierarchy
The API exposes a three-level vehicle hierarchy. get_car_makers returns all manufacturers available on Autodoc, each with an integer id, a name, and a group indicating popularity tier. Pass any maker_id to get_car_models to receive the model list for that brand, grouped by series. From there, get_car_engines accepts a model_id and returns engine variants grouped by fuel type — each engine object carries its own id and name for use in downstream part matching.
Parts Search and Product Detail
search_parts accepts a free-text query — brand-specific article numbers like RIDEX 7999410 work as well as generic terms like brake pads. Results are typed objects: suggestion, category, or product, each carrying a title and a url path. Those URL paths feed directly into get_product_details, which returns a product's name, brand, price (formatted with currency symbol), a specs object mapping specification names to values, an article_number, and an oe_numbers array of OE/OEM reference strings when available.
Compatible Alternatives
get_equivalent_products takes the same URL path format as get_product_details and returns an equivalents array. Each entry includes the alternative part's brand, part_number, price (or null if unlisted), and a url path for further detail lookup. This makes it straightforward to compare compatible replacements across different manufacturers for a given part.
- Build a vehicle-to-parts lookup tool using the maker → model → engine hierarchy endpoints
- Cross-reference OE/OEM numbers from
get_product_detailsagainst your own parts database - Compare prices across compatible replacement parts using
get_equivalent_products - Populate a parts catalog with specs, article numbers, and brand data from
get_product_details - Search by article number to resolve a specific part and retrieve its full specification sheet
- Identify all available brands supplying a given replacement part for a specific vehicle engine variant
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 250 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Autodoc have an official public developer API?+
What does `get_product_details` return beyond price and name?+
get_product_details returns a specs object containing named technical attributes (such as dimensions or material grades, depending on the part type), an oe_numbers array listing OEM reference numbers cross-referenced by the listing, an article_number, and the brand name. The oe_numbers field may be empty for parts that have no OE references listed on Autodoc.Does the API return customer reviews or ratings for parts?+
Can I filter `search_parts` results to a specific vehicle or engine?+
search_parts endpoint accepts a free-text query string only; there is no built-in vehicle filter parameter. The vehicle hierarchy endpoints (get_car_makers, get_car_models, get_car_engines) handle vehicle scoping separately. You can fork the API on Parse and revise it to combine vehicle context with part search in a single endpoint.Are stock availability or inventory levels included in product responses?+
get_product_details returns price, specs, and OE numbers but does not include stock or availability status. You can fork the API on Parse and revise it to add an endpoint that retrieves availability data if Autodoc surfaces it on the product page.