Vehicle owner complaints

GET https://api.api.sh/vehicles/v1/complaints
1 credit / call public data try it in the playground →

Owner complaints filed with NHTSA for a make, model and year: ODI number, incident and filing dates, components, the owner's description, crash, fire, injuries and deaths, partial VIN and products involved; counts by component. Filter by component, crash, fire or injuries; sort newest or oldest. Pass next_page back as page; null on the last page.

Every response includes credits_used: the credits this call cost.

Parameters

nametypedescription
makerequired string Make. Example: honda
modelrequired string Model. Example: accord
yearrequired integer Model year. Example: 2012
component string Component contains this text, e.g. engine, brakes.
crash boolean true: only complaints involving a crash.
fire boolean true: only complaints involving a fire.
injuries boolean true: only complaints with injuries.
sort newest | oldest newest (default) or oldest filing date.
limit integer Per page (default 50, max 200).
page integer Page (default 1).

Every endpoint also takes fresh, raw, fields (see lean responses and caching).

Example

curl "https://api.api.sh/vehicles/v1/complaints?make=honda&model=accord&year=2012" \
  -H "x-api-key: $APISH_KEY"

Response

A JSON object with the fields described above, plus raw (the source's own data), cached, fetched_at and credits_used. Errors return {"success": false, "error": "…"} with the HTTP status (see errors). A lookup that ran but found nothing (404) costs the price above; refused calls and errors on our side are free (what's charged).

The fastest way to see the full response is the playground: it runs this endpoint with your account and shows the exact JSON.