Brazilian Vehicles and Prices
Vehicle
Vehicles information from Fundação Instituto de Pesquisas Econômicas - Fipe
NHTSA safety recalls by model year, make and model with component, consequence and remedy
API key
Required
HTTPS
Supported
Browser calls
Unconfirmed
Status
Not yet checked
A starting template for NHTSA Vehicle Recalls. Replace ENDPOINT with the path from the official documentation, which we link above rather than guess at.
# Requires an API key. Check the docs for whether it goes in a header or a query parameter.
curl -s "https://rapidapi.com/ENDPOINT" \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Accept: application/json"Aggregated from one public source (public-apis), then normalised and checked by us.
Report an issue with this listing ↗Vehicle
Vehicles information from Fundação Instituto de Pesquisas Econômicas - Fipe
Vehicle
NHTSA Product Information Catalog and Vehicle Listing
Vehicle
US NHTSA owner-complaint & recall data as vehicle failure patterns by year, make & model; open CSV/JSON datasets + a machine-readable catalog
Vehicle
Find auto body shops by ZIP code, city, location, or profile
Vehicle
UK motorcycle reliability ranked by first-time MOT pass rates
Vehicle
Fair-price valuation and yearly road tax (IUC) for used cars in Portugal
Answered from what our own scheduled checks found, not from the provider's marketing.
NHTSA Vehicle Recalls is listed in our free catalogue, but it requires an API key, so you will need to register before your first call. Providers frequently reserve higher limits and commercial use for paid plans.
Yes. NHTSA Vehicle Recalls authenticates with an API key. Keep it server-side rather than in browser code, because anything in your frontend bundle is readable by anyone who opens developer tools.
We could not confirm CORS support for NHTSA Vehicle Recalls. Test it from a browser before relying on it client-side; if the request succeeds in curl but fails in the console, CORS is the reason.
Yes. NHTSA Vehicle Recalls serves over HTTPS, so you can call it from a secure page without triggering a mixed-content block.