API key
Request statistics
Not just an API, but an intelligence layer for trustworthy vehicle data.
We turn fragmented listings from many sources into one clean, comparable and predictable dataset. The system removes noise, merges duplicates, standardizes entities and gives you data you can build on without operational chaos.
Inspection reports become one consistent data standard
Sources deliver inspections in different formats, from structured APIs to scans and PDFs. We normalize conclusions, checks, damage, diagnostics, media and files into one predictable contract, so integrations do not need source-specific parsers.
Duplicates are detected even without VIN
When VIN is missing, the system compares photos, specifications, listing history and dozens of indirect signals. Merge decisions are based on multiple indicators, which makes the result feel almost like magic.
Makes and models are normalized into one standard
Each make and model can have dozens or hundreds of synonyms. This database is maintained by a real person, because order and high confidence in this layer cannot be fully delegated to AI.
Locations become precise and comparable
Any location is mapped into one shared location database: country, region, city and coordinates. Each car can receive latitude and longitude, enabling smarter sorting, radius search and geographic analytics.
Vehicle options are standardized as their own system
AI models handle complex, local and multilingual option names, while a human reviews the cases where the model is uncertain. The result is a strong, extensible taxonomy that is usable for filters.
Requests by day
—Requests by month
—Important note before using the API
/cars is intended for downloading all cars. It uses scroll pagination: the server creates a temporary scroll context, and the number of requests used to continue that pagination cannot be technically unlimited.
/search is intended for searching cars with filters. It does not have that technical scroll-request limit, but the maximum pagination window is limited to 10k results.
Recommended sync flow: 2-3 times per day, walk through the full /cars feed and store the received cars. Every car that was not present in the latest completed full pass should be treated as archived in your system.
Archived cars disappear from /search and /cars, but usually remain available in the database for about 1 month. During that period /cars/{car_id} and /listing/{domain_id}/{listing_id} can still return them with an archive marker. After roughly 1 month they can disappear from those endpoints too.
Vehicle inspection reports
A car can include standardized inspection reports. The lightweight has_inspections boolean indicates that at least one non-archived report is linked to an active listing.
Endpoint behavior
- GET /search
- Returns has_inspections only. The inspections array is intentionally omitted to keep search responses compact.
- GET /cars
- Returns has_inspections and inspections. The array contains public, non-archived reports linked to active listings visible to the API key.
- GET /cars/{car_id}
- Returns all public, non-archived reports linked to the car’s active listings visible to the API key.
- GET /listing/{domain_id}/{listing_id}
- Returns reports for the exact domain_id and listing_id pair only.
Public report format
{
"report_id": "inspection_987654",
"status": "published",
"visibility": "public",
"language": "ko",
"created_at": "2026-05-31T04:27:33+00:00",
"system_updated_at": "2026-07-07T12:30:00+00:00",
"vehicle_ref": {
"domain_id": 123,
"listing_id": "987654",
"site_car_id": null,
"vin": "..."
},
"vehicle_snapshot": {},
"source": {},
"conclusions": {},
"source_claims": [],
"inspection_blocks": [],
"checked_items": [],
"diagnostic_errors": [],
"media": [],
"files": [],
"limitations": []
}Contract rules
- When no report is available, inspections is an empty array.
- Only reports with visibility public and a status other than archived are returned.
- Reports are sorted by system_updated_at descending, created_at descending, then report_id ascending.
- language identifies the source report language, not the interface language. Translate standardized keys in the client application.
- vehicle_snapshot is historical context captured with the report. Current values from the main car object take precedence.
- created_at is the source creation time. system_updated_at is the time the report was stored or refreshed in the API data layer.
API enum values
Use the numeric ID in API requests. Each group shows a compact preview; open the full list to search, select values for /search and copy request-ready fragments.
Endpoints
Parameters are added to the GET request automatically.
Prompt for your AI coding agent
Copy this block and send it to Codex, Claude, Copilot or another AI agent so it understands the API, limits, endpoints and your current key context.