POST /api/nhtsa/safety-ratings
Price: 10 credits
Get NHTSA NCAP crash-test ratings for one vehicle variant: overall, frontal, side, side-pole and rollover stars, rollover probability, crash-test photos and videos, driver-assistance equipment, and complaint, recall and investigation counts.
Take `id` from nhtsa/safety-ratings/search, which lists the rated variants of a make, model and year. Ratings are star values 1 to 5 as text, or Not Rated when the test was not run.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)vehicle_id string required — NCAP vehicle id from nhtsa/safety-ratings/search (examples: "9096")@type string (default: "NhtsaSafetyRating")id string requireddescription string nullablemake string nullablemodel string nullablemodel_year integer nullableoverall_rating string nullableoverall_front_crash_rating string nullablefront_crash_driver_side_rating string nullablefront_crash_passenger_side_rating string nullablefront_crash_image string nullablefront_crash_video_url string nullableoverall_side_crash_rating string nullableside_crash_driver_side_rating string nullableside_crash_passenger_side_rating string nullableside_crash_image string nullableside_crash_video_url string nullablecombined_side_barrier_and_pole_front_rating string nullablecombined_side_barrier_and_pole_rear_rating string nullableside_barrier_overall_rating string nullablerollover_rating string nullablerollover_rating_2 string nullablerollover_probability number nullablerollover_probability_2 number nullabledynamic_tip_result string nullableside_pole_crash_rating string nullableside_pole_image string nullableside_pole_video_url string nullableelectronic_stability_control string nullableforward_collision_warning string nullablelane_departure_warning string nullablecomplaint_count integer nullablerecall_count integer nullableinvestigation_count integer nullable422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.412 — No rated vehicle with that id Retrying will not help: either the entity does not exist, or the input points at a different one.429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.X-Retry-After — Seconds to wait before retrying. Present only on 429.