Autodoc APIautodoc.es ↗
Access Autodoc.es vehicle makes, models, parts search, OE cross-references, and fitment data via 7 structured endpoints. Covers the full Spanish auto parts catalog.
What is the Autodoc API?
The Autodoc.es API exposes 7 endpoints covering the complete vehicle-to-part lookup chain on Spain's autodoc.es auto parts catalog. Starting with get_vehicle_makes to retrieve all manufacturers, you can drill down through models and engine variants, search parts by Spanish keyword or exact part number, and fetch full part details including OE cross-reference numbers, technical specifications, pricing in EUR, and vehicle compatibility lists.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/9c78ad41-8cdd-4c24-979f-3924df4608f8/get_vehicle_makes' \ -H 'X-API-Key: $PARSE_API_KEY'
Retrieve all vehicle manufacturers available in the catalog. Returns makers grouped by popularity (top 10 recognized) and alphabetically. Each maker carries an ID usable with get_vehicle_models to drill into that manufacturer's model tree.
No input parameters required.
{
"type": "object",
"fields": {
"total": "integer total number of makers across all groups",
"makers": "array of maker objects each with id (int), name (string), group (string label such as 'Los fabricantes más reconocidos'), euro_reg (boolean), synonyms (array of strings)"
},
"sample": {
"data": {
"total": 186,
"makers": [
{
"id": 16,
"name": "BMW",
"group": "Los fabricantes más reconocidos",
"euro_reg": true,
"synonyms": []
},
{
"id": 121,
"name": "VOLKSWAGEN",
"group": "Los fabricantes más reconocidos",
"euro_reg": true,
"synonyms": [
"Volkswagen",
"Volkswagen",
"Volkswagen"
]
}
]
},
"status": "success"
}
}About the Autodoc API
Vehicle Hierarchy Navigation
The API follows the same three-level vehicle selection used on autodoc.es. get_vehicle_makes returns every manufacturer in the catalog — grouped as top-recognized makers and alphabetical remainder — with each maker carrying an id integer for downstream calls. Pass that maker_id to get_vehicle_models to get all model lines for that manufacturer, each with a date range in the name, grouped by series, and including synonyms. From there, get_vehicle_variants on a model_id breaks down by fuel type (e.g. Gasolina, Diésel) and returns variant objects with power specs and date ranges. These variant IDs feed vehicle-specific part filtering.
Parts Search and Category Browsing
search_parts accepts a Spanish keyword or exact part number string and returns grouped autocomplete results with group_type values such as popular queries, category, and product. Because the catalog is Spanish-language, queries like pastillas de freno or disco de freno produce richer hits than English equivalents. For bulk lookups, search_parts_batch accepts up to 50 part numbers in a single call and returns one result object per input, in order, each with query, success, article_id, part_number, and brand fields — useful for resolving a list of known OEM numbers at once.
get_category_parts retrieves paginated listings for a category identified by a category_slug with numeric suffix (e.g. disco-de-freno-10132). Optionally supply a car_slug such as vw/golf/golf-v-variant-1k5/23263-1-4 to filter results to a specific vehicle. Each part in the response includes article_id, part_number, brand_name, price, rrp_price, currency, category_name, and category_id.
Full Part Details
get_part_details requires an article_id and a brand_slug (e.g. brembo, bosch, zimmermann) and returns the most complete record in the API: ean barcode, sku, full product name, images array, price, rrp_price in EUR, oe_numbers (each with oe_number string and brands array indicating which OEMs use it), technical specification key-value pairs, interchange or equivalent parts, and a vehicle compatibility list. This is the primary endpoint for building part detail pages or verifying fitment against a known OE number.
The Autodoc API is a managed, monitored endpoint for autodoc.es — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when autodoc.es changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official autodoc.es API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Build a Spanish-market parts finder that chains get_vehicle_makes → get_vehicle_models → get_vehicle_variants → get_category_parts to show vehicle-filtered listings
- Resolve a batch of OEM part numbers to Autodoc article IDs and current EUR prices using search_parts_batch
- Enrich a parts database with OE cross-reference numbers and fitment data from get_part_details oe_numbers and compatibility fields
- Compare rrp_price vs price across multiple brands within a category to surface discount margins
- Generate structured product feeds for brake, suspension, or filter categories using get_category_parts with category_slug and pagination
- Verify whether a specific part number from a supplier matches an autodoc.es listing by checking article_id and ean from get_part_details
- Map manufacturer model trees for Volkswagen, BMW, or Mercedes-Benz using get_vehicle_models with the documented maker IDs
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 200 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
| Team | $300/mo | 20,000 | 300 req/min |
| Company | $1,000/mo | 100,000 | 500 req/min |
Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.