{
"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'
Após se cadastrar, cada desenvolvedor recebe uma chave de acesso à API pessoal, uma combinação única de letras e dígitos para acessar nosso endpoint de API. Para autenticar com a Monitor de Recall de Veículos API basta incluir seu token Bearer no cabeçalho Authorization.
| Cabeçalho | Descrição |
|---|---|
Authorization
|
Obrigatório
Deve ser Bearer access_key. Veja "Sua chave de acesso à API" acima quando você estiver inscrito.
|
Sem compromisso de longo prazo. Faça upgrade, downgrade ou cancele a qualquer momento.
Pesquise campanhas de recall de veículos normalizadas da NHTSA por marca, modelo, ano e componente, com correspondência de VIN marca-modelo-ano e frescor da fonte em JSON
Campanhas de recall de veículos NHTSA normalizadas construídas a partir dos arquivos planos oficiais NHTSA FLAT_RCL retornados como JSON consistente
Não. Os resultados são fornecidos como estão podem estar atrasados ou incompletos e devem ser confirmados com o registro da fonte oficial
Sim uma busca que não encontra nada é uma resposta bem-sucedida com uma lista vazia
Não. Os planos da Zyla incluem os pontos finais listados aqui; o feed /recalls/changes não faz parte desta lista
Cada endpoint retorna dados JSON relacionados a recalls de veículos O endpoint GET Sources fornece informações sobre fontes de dados e atualidade O endpoint GET Search Recalls retorna detalhes sobre campanhas de recall com base em vários critérios de pesquisa O endpoint GET Get Campaign recupera detalhes específicos da campanha enquanto o endpoint GET Stats oferece estatísticas sobre o corpus de recalls O endpoint GET VIN Recalls decodifica VINs e os combina com recalls relevantes
Os campos chave variam por ponto final. Por exemplo, o ponto final GET Buscar Lembretes inclui campos como `número_da_campanha`, `fabricante` e `tipo_de_lembrete`. O ponto final GET Obter Campanha fornece `id`, `fonte` e `componentes`. O ponto final GET Lembretes VIN inclui `vin`, `decodificado` e `status_de_lembrete_aberto`. A estrutura de resposta de cada ponto final é projetada para fornecer informações relevantes sobre lembretes de maneira eficiente
O endpoint Search Recalls aceita parâmetros como `make`, `model`, `model_year`, `component`, `campaign_number`, `date_range` e `keyword`. Os usuários podem personalizar suas solicitações combinando esses parâmetros para filtrar resultados de acordo com atributos específicos do veículo ou detalhes do recall
Os dados de resposta são organizados em um formato JSON estruturado. A resposta de cada endpoint geralmente inclui metadados (como `total`, `limit` e `offset`) seguidos por um array `data` contendo registros detalhados. Por exemplo, a resposta da pesquisa GET Recall inclui uma lista de campanhas de recall, cada uma com seu próprio conjunto de atributos
Os dados são originados dos arquivos planos da Administração Nacional de Segurança no Tráfego Rodoviário (NHTSA), especificamente do conjunto de dados FLAT_RCL. Isso garante que as informações sejam derivadas de registros oficiais do governo, embora possam estar sujeitas a atrasos ou incompletude
A precisão dos dados é mantida por meio de atualizações regulares do NHTSA, que republica os arquivos FLAT_RCL. A API também inclui campos como `last_verified_at` para indicar quando os dados foram confirmados pela última vez, ajudando os usuários a avaliar a confiabilidade das informações
Casos de uso típicos incluem verificar recalls em marcas e modelos de veículos específicos pesquisar o histórico de segurança de veículos e garantir a conformidade com regulamentos de segurança Os desenvolvedores podem integrar esses dados em aplicações que informam os consumidores sobre questões de segurança veicular
Se uma busca não retornar resultados, a API fornecerá uma lista vazia no array `data`, juntamente com uma contagem `total` de zero. Os usuários devem implementar verificações em suas aplicações para lidar com tais casos de forma elegante, possivelmente informando os usuários que nenhuma chamada foi encontrada para sua consulta