{
"disclaimer": "Vehicle recall records are normalized from public NHTSA flat files (FLAT_RCL). They are U.S. government works, may be delayed or incomplete, and are not a safety guarantee. This API does not report whether a specific VIN's recall has been repaired. Confirm the official notice and check [contact details removed] or the vehicle manufacturer.",
"limitation": {
"per_vin_repair_status": "not_available_from_public_source",
"match_basis_for_vin_lookup": "make_model_year",
"consumer_tool": "[contact details removed]",
"manufacturer": "The vehicle manufacturer is the source of unrepaired-VIN status."
},
"data": [
{
"source": "NHTSA-FLAT-RCL",
"role": "bulk_ingest_and_change_detection",
"urls": [
"[contact details removed]",
"[contact details removed]"
],
"dictionary_url": null,
"cadence": "NHTSA republishes FLAT_RCL_PRE_2010.zip and FLAT_RCL_POST_2010.zip most days. This service ingests both files together once a day. A failed download does not remove campaigns from the previous good snapshot.",
"last_success": "2026-11-16T04:33:57+00:00",
"last_attempt": "2026-11-16T04:33:57+00:00",
"last_status": "ok",
"records": 30461,
"license": "NHTSA records are U.S. government works and are in the public domain. Wryborg's normalization, hashes, and change feed are derived data. Wryborg is not affiliated with NHTSA or the U.S. Department of Transportation."
},
{
"source": "NHTSA-RECALLS-API",
"role": "official_lookup_by_make_model_year_and_campaign",
"urls": [
"[contact details removed]",
"[contact details removed]"
],
"docs": "[contact details removed]",
"note": "ReportReceivedDate on this API is day/month/year. The stored report_received_date comes from flat-file RCDATE (YYYYMMDD)."
},
{
"source": "NHTSA-VPIC",
"role": "vin_decode_only",
"urls": [
"[contact details removed]",
"[contact details removed]"
],
"rate_limit": "NHTSA describes vPIC as rate-controlled and does not publish a stable numeric quota. This service calls DecodeVinValues once per VIN request. A vPIC failure is upstream_unavailable, not an empty recall list. DecodeVinValuesBatch is documented here and is not called by this API.",
"license": "U.S. government work."
}
]
}
curl --location --request GET 'https://zylalabs.com/api/15010/vehicle+recall+monitor+api/39574/sources' --header 'Authorization: Bearer YOUR_API_KEY'
{
"total": 938,
"limit": 1,
"offset": 0,
"plan": "free",
"history_from": "2025-11-17",
"warnings": [],
"data": [
{
"id": "nhtsa-26V745000",
"campaign_number": "26V745000",
"source": "NHTSA",
"source_url": null,
"consumer_url": null,
"dictionary_url": null,
"retrieved_at": "2026-11-15T04:08:41+00:00",
"last_verified_at": "2026-11-16T04:33:57+00:00",
"last_updated": "2026-11-15T04:08:41+00:00",
"ingested_at": "2026-11-15T04:08:41+00:00",
"content_hash": "sha256:e566e2e058a98c9de4d398cd70e18224c01a7f51162fb8769718e05a9015032f",
"manufacturer": "Winnebago Towable",
"manufacturers": [
"Winnebago Towable",
"Winnebago of Indiana, LLC"
],
"manufacturer_campaign_numbers": [
"44448365"
],
"recall_type": "V",
"components": [
"EQUIPMENT:OTHER:LABELS"
],
"component": "EQUIPMENT:OTHER:LABELS",
"make_model_years": [
{
"make": "WINNEBAGO",
"model": "THRIVE",
"year_from": 2026,
"year_to": 2026,
"years": [
2026
]
}
],
"summary": "Winnebago Towable (Winnebago) is recalling certain 2026 Thrive travel trailers. The original Gross Vehicle Weight Rating (GVWR) and Gross Axle Weight Rating (GAWR) were not listed the certification label after vehicle alterations. As such, these vehicles fail to comply with the requirements of 49 CFR Part 567, \"Certification.\"",
"consequence": "If the values of the GVWR and GAWR differ from the original label values, it can lead to unintentionally overloading the trailer, increasing the risk of a crash.",
"remedy": "Winnebago will provide corrected labels, free of charge. Owner letters are expected to be mailed January 7, 2027. Owners may contact Winnebago customer service at 1-[contact details removed] Ext. 5220. Winnebago's number for this recall is 44448365.",
"notes": null,
"report_received_date": "2026-11-12",
"record_created_date": "2026-11-12",
"owner_notified_date": null,
"manufacture_begin": "2025-10-28",
"manufacture_end": "2025-11-12",
"potential_units_affected": 18,
"park_it": false,
"park_outside": false,
"influenced_by": "MFR",
"fmvss": [
"567"
],
"regulation_part": []
}
],
"disclaimer": "Vehicle recall records are normalized from public NHTSA flat files (FLAT_RCL). They are U.S. government works, may be delayed or incomplete, and are not a safety guarantee. This API does not report whether a specific VIN's recall has been repaired. Confirm the official notice and check [contact details removed] or the vehicle manufacturer."
}
curl --location --request GET 'https://zylalabs.com/api/15010/vehicle+recall+monitor+api/39575/search+recalls?limit=1' --header 'Authorization: Bearer YOUR_API_KEY'
{
"id": "nhtsa-26V745000",
"campaign_number": "26V745000",
"source": "NHTSA",
"source_url": null,
"consumer_url": null,
"dictionary_url": null,
"retrieved_at": "2026-11-15T04:08:41+00:00",
"last_verified_at": "2026-11-16T04:33:57+00:00",
"last_updated": "2026-11-15T04:08:41+00:00",
"ingested_at": "2026-11-15T04:08:41+00:00",
"content_hash": "sha256:e566e2e058a98c9de4d398cd70e18224c01a7f51162fb8769718e05a9015032f",
"manufacturer": "Winnebago Towable",
"manufacturers": [
"Winnebago Towable",
"Winnebago of Indiana, LLC"
],
"manufacturer_campaign_numbers": [
"44448365"
],
"recall_type": "V",
"components": [
"EQUIPMENT:OTHER:LABELS"
],
"component": "EQUIPMENT:OTHER:LABELS",
"make_model_years": [
{
"make": "WINNEBAGO",
"model": "THRIVE",
"year_from": 2026,
"year_to": 2026,
"years": [
2026
]
}
],
"summary": "Winnebago Towable (Winnebago) is recalling certain 2026 Thrive travel trailers. The original Gross Vehicle Weight Rating (GVWR) and Gross Axle Weight Rating (GAWR) were not listed the certification label after vehicle alterations. As such, these vehicles fail to comply with the requirements of 49 CFR Part 567, \"Certification.\"",
"consequence": "If the values of the GVWR and GAWR differ from the original label values, it can lead to unintentionally overloading the trailer, increasing the risk of a crash.",
"remedy": "Winnebago will provide corrected labels, free of charge. Owner letters are expected to be mailed January 7, 2027. Owners may contact Winnebago customer service at 1-[contact details removed] Ext. 5220. Winnebago's number for this recall is 44448365.",
"notes": null,
"report_received_date": "2026-11-12",
"record_created_date": "2026-11-12",
"owner_notified_date": null,
"manufacture_begin": "2025-10-28",
"manufacture_end": "2025-11-12",
"potential_units_affected": 18,
"park_it": false,
"park_outside": false,
"influenced_by": "MFR",
"fmvss": [
"567"
],
"regulation_part": []
}
curl --location --request GET 'https://zylalabs.com/api/15010/vehicle+recall+monitor+api/39576/get+campaign&recall_id=Required' --header 'Authorization: Bearer YOUR_API_KEY'
{
"total": 938,
"park_it": 23,
"park_outside": 25,
"last_30_days": 62,
"date_range": {
"min": "2025-11-17",
"max": "2026-11-12"
},
"history_from": "2025-11-17",
"plan": "free",
"disclaimer": "Vehicle recall records are normalized from public NHTSA flat files (FLAT_RCL). They are U.S. government works, may be delayed or incomplete, and are not a safety guarantee. This API does not report whether a specific VIN's recall has been repaired. Confirm the official notice and check [contact details removed] or the vehicle manufacturer."
}
curl --location --request GET 'https://zylalabs.com/api/15010/vehicle+recall+monitor+api/39577/stats' --header 'Authorization: Bearer YOUR_API_KEY'
{
"vin": "1HGCM82633A004352",
"match_basis": "make_model_year",
"open_recall_status": "not_available_from_public_source",
"open_recall_status_detail": "NHTSA does not publish a public API for whether this VIN's recalls are unrepaired. Matches are campaigns for the decoded make, model, and model year (match_basis \"make_model_year\"). Per-VIN repair status requires [contact details removed] or the vehicle manufacturer.",
"consumer_recall_lookup_url": null,
"decoded": {
"make": "HONDA",
"model": "Accord",
"model_year": 2003,
"vehicle_type": "PASSENGER CAR",
"body_class": "Coupe",
"manufacturer": "AMERICAN HONDA MOTOR CO., INC.",
"error_code": "0",
"error_text": "0 - VIN decoded clean. Check Digit (9th position) is correct",
"source": "NHTSA-VPIC",
"source_url": null
},
"total": 0,
"limit": 1,
"offset": 0,
"plan": "free",
"history_from": "2025-11-17",
"omitted_by_plan": 24,
"warnings": [
{
"code": "no_exact_model_match",
"message": "No campaign matched this decoded model name. Flat-file model names sometimes differ from vPIC (for example SILVERADO 1500 versus Silverado). An empty list is not a clean bill of health and is not a per-VIN repair status."
},
{
"code": "history_clamped",
"message": "24 model-year match(es) are outside the free plan window and were omitted. This is not a determination that the vehicle has no recalls."
}
],
"data": [],
"disclaimer": "Vehicle recall records are normalized from public NHTSA flat files (FLAT_RCL). They are U.S. government works, may be delayed or incomplete, and are not a safety guarantee. This API does not report whether a specific VIN's recall has been repaired. Confirm the official notice and check [contact details removed] or the vehicle manufacturer."
}
curl --location --request GET 'https://zylalabs.com/api/15010/vehicle+recall+monitor+api/39578/vin+recalls?limit=1&vin=Required' --header 'Authorization: Bearer YOUR_API_KEY'
After signing up, every developer is assigned a personal API access key, a unique combination of letters and digits provided to access to our API endpoint. To authenticate with the Vehicle Recall Monitor API simply include your bearer token in the Authorization header.
| Header | Description |
|---|---|
Authorization
|
Required
Should be Bearer access_key. See "Your API Access Key" above when you are subscribed.
|
No long-term commitment. Upgrade, downgrade, or cancel anytime.
Search normalized NHTSA vehicle recall campaigns by make, model, year and component, with VIN make-model-year matching and source freshness in JSON.
Normalized NHTSA vehicle recall campaigns built from the official NHTSA FLAT_RCL flat files, returned as consistent JSON.
No. Results are provided as-is, may be delayed or incomplete, and should be confirmed against the official source record.
Yes. A search that matches nothing is a successful response with an empty list.
No. Zyla plans include the endpoints listed here; the /recalls/changes feed is not part of this listing.
Each endpoint returns JSON data related to vehicle recalls. The GET Sources endpoint provides information about data sources and freshness. The GET Search Recalls endpoint returns details about recall campaigns based on various search criteria. The GET Get Campaign endpoint retrieves specific campaign details, while the GET Stats endpoint offers statistics about the recall corpus. The GET VIN Recalls endpoint decodes VINs and matches them to relevant recalls.
Key fields vary by endpoint. For example, the GET Search Recalls endpoint includes fields like `campaign_number`, `manufacturer`, and `recall_type`. The GET Get Campaign endpoint provides `id`, `source`, and `components`. The GET VIN Recalls endpoint includes `vin`, `decoded`, and `open_recall_status`. Each endpoint's response structure is designed to deliver relevant recall information efficiently.
The Search Recalls endpoint accepts parameters such as `make`, `model`, `model_year`, `component`, `campaign_number`, `date_range`, and `keyword`. Users can customize their requests by combining these parameters to filter results according to specific vehicle attributes or recall details.
Response data is organized in a structured JSON format. Each endpoint's response typically includes metadata (like `total`, `limit`, and `offset`) followed by a `data` array containing detailed records. For instance, the GET Search Recalls response includes a list of recall campaigns, each with its own set of attributes.
The data is sourced from the National Highway Traffic Safety Administration (NHTSA) flat files, specifically the FLAT_RCL dataset. This ensures that the information is derived from official government records, although it may be subject to delays or incompleteness.
Data accuracy is maintained through regular updates from the NHTSA, which republishes the FLAT_RCL files. The API also includes fields like `last_verified_at` to indicate when the data was last confirmed, helping users assess the reliability of the information.
Typical use cases include checking for recalls on specific vehicle makes and models, researching vehicle safety history, and ensuring compliance with safety regulations. Developers can integrate this data into applications that inform consumers about vehicle safety issues.
If a search returns no results, the API will provide an empty list in the `data` array, along with a `total` count of zero. Users should implement checks in their applications to handle such cases gracefully, possibly by informing users that no recalls were found for their query.
To obtain your API key, first sign in to your account and navigate to the API you want to use. From the API's Pricing section, choose a plan and complete the subscription process. Once subscribed, return to the API page and you will see your API Access Key displayed at the top of the documentation page. You can use this key to authenticate your requests.
You can’t switch APIs during the free trial. If you subscribe to a different API, your trial will end and the new subscription will start as a paid plan.
The free trial lasts for 7 days and allows you to make up to 50 API requests.
No, the free trial is available only once, so we recommend using it on the API that interests you the most. Most of our APIs offer a free trial, but some may not include this option.
Yes. If the API offers a free trial, you will see a "Free 7-Day Trial" option in its Pricing section. The trial lasts for 7 days and allows up to 50 API requests, enabling you to evaluate the API before subscribing to a paid plan.
Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.
You can monitor your API usage through the response headers included with every request:
x-zyla-api-calls-monthly-used: Shows the total number of API requests you have used during the current billing period.
x-zyla-api-calls-monthly-remaining: Shows the number of API requests you have remaining for the current billing period.
Yes, you can cancel your subscription at any time. Simply go to the Pricing section of the API you're subscribed to and click the "Unsubscribe" button.
Please note that upgrades, downgrades, and cancellations take effect immediately. Once your subscription is canceled, access to the service will end immediately, regardless of any remaining API calls in your quota.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund