auto-data.net APIwww.auto-data.net ↗
Access specs for 53,500+ cars via the auto-data.net API. Browse brands, models, generations, and variants to retrieve engine, performance, and dimension data.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/a203509b-10c5-4784-8bd6-00bd8f4608db/list_brands' \ -H 'X-API-Key: $PARSE_API_KEY'
List all car brands available in the database (376+ brands). Returns brand names, slugs, and URL paths for use with get_models.
No input parameters required.
{
"type": "object",
"fields": {
"total": "integer count of brands returned",
"brands": "array of objects with keys: name (string), slug (string), url_path (string)"
},
"sample": {
"data": {
"total": 376,
"brands": [
{
"name": "212",
"slug": "212-brand-382",
"url_path": "/en/212-brand-382"
},
{
"name": "Abarth",
"slug": "abarth-brand-200",
"url_path": "/en/abarth-brand-200"
},
{
"name": "BMW",
"slug": "bmw-brand-86",
"url_path": "/en/bmw-brand-86"
}
]
},
"status": "success"
}
}About the auto-data.net API
The auto-data.net API provides structured access to specifications for over 53,500 automobiles across 376+ brands through 6 endpoints. Starting with list_brands, you can traverse the full vehicle hierarchy — brands, models, generations, variants — down to granular spec data covering engine output, dimensions, drivetrain configuration, and weight. The get_specifications endpoint returns named sections of spec key/value pairs alongside FAQ-style key specs for any individual variant.
Navigating the Vehicle Hierarchy
The API is organized as a four-level hierarchy. list_brands returns all available brands with name, slug, and url_path fields. Pass a brand_slug (e.g., bmw-brand-86) to get_models to get every model for that brand, including production year ranges. From there, get_generations accepts a model_slug and returns generation names, slugs, and thumbnail image_url values. Finally, get_variants takes a generation_slug and lists every trim and engine option with its production years — each variant slug feeds directly into get_specifications.
Specification Detail
get_specifications is the most data-dense endpoint. It returns a title string, an optional image_url, a key_specs object with FAQ-style question-answer pairs (e.g., top speed, fuel consumption), and a specifications object whose keys are section names — such as performance, engine, dimensions, or drivetrain — each mapping to a flat object of spec name/value pairs. The exact sections present vary by vehicle type, so consumers should handle missing sections gracefully.
Search and Discovery
The search endpoint accepts a free-text query (e.g., Toyota Corolla, Audi A4) and returns up to 30 results. Each result carries a type field classified as brand, model, generation, or variant, along with a slug and url_path. This makes it practical to skip manual hierarchy traversal when you already know the vehicle name and want to jump directly to a generation or variant slug.
Coverage and Data Shape
The database covers 53,500+ automobiles spanning over 376 brands. Model entries include production year strings where available, though some return null for years. Specification sections and field names are drawn from the source and may differ between vehicle categories (passenger cars, commercial vehicles, etc.), so downstream code should treat the specifications object as a dynamic map rather than a fixed schema.
- Build a vehicle lookup tool that resolves a user's car make/model/year to full engine and performance specifications.
- Populate a database of trim-level variants with production year ranges using
get_variantsfor market research on historic model availability. - Compare fuel consumption and CO2 figures across generations of the same model by iterating
get_generationsthenget_specifications. - Power an autocomplete search field for car configurators using the
searchendpoint'stype-classified results. - Extract dimension data (length, width, wheelbase) from
get_specificationsto support fitment or logistics applications. - Generate structured datasets of drivetrain configurations (FWD/RWD/AWD, transmission type) across an entire brand's lineup.
- Cross-reference horsepower and torque values from
key_specsto build performance ranking tables across vehicle classes.
| 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 auto-data.net have an official developer API?+
What does `get_specifications` actually return, and is the spec schema consistent across all vehicles?+
title, an optional image_url, a key_specs object with short answers to FAQ-style questions, and a specifications object whose section names and field names vary by vehicle type. Passenger cars may have sections like Performance, Engine, and Dimensions, while other vehicle types may expose different or fewer sections. Treat the spec object as a dynamic map.Does the API return pricing or market valuation data for vehicles?+
Does the `search` endpoint support filtering by vehicle type or year range?+
search endpoint accepts only a free-text query string and returns up to 30 results classified by type (brand, model, generation, or variant). There are no filter parameters for year range, body style, or fuel type. You can fork this API on Parse and revise it to add filtered search behavior on top of the hierarchy endpoints.Are there pagination parameters for endpoints like `list_brands` or `get_models` that return large result sets?+
list_brands and get_models return all results in a single response with a total count — there are no pagination parameters. For brands with very large model catalogs this means the full list is returned at once. If you need paginated access, you can fork this API on Parse and add offset or page parameters to the endpoint logic.