Consumer Product Recalls Monitor: FDA, CPSC & NHTSA

Track official US product recalls from one Actor: FDA food, drug and medical-device enforcement reports (openFDA), CPSC consumer product recalls (SaferProducts.gov) and NHTSA vehicle recalls. Results come back as one clean, flat, consistent dataset. Turn on Only new recalls and schedule it to get a recall alert feed that never repeats itself.

All data comes from free, official US government APIs. No scraping, no proxies, no login.

Who uses it

• Compliance and quality teams: watch for recalls touching your ingredients, suppliers or product categories.
• Retailers and grocers: catch Class I food and consumer product recalls before shelves are affected.
• Amazon, Walmart and eBay sellers: monitor CPSC and FDA recalls on the product types you sell, and avoid listing recalled items.
• Journalists and researchers: pull every recall by firm, hazard or date range into CSV or JSON.
• Law firms: find new recalls (product liability, class actions) by manufacturer or keyword as they are published.
• Insurers, importers, 3PLs, consumer apps: feed recall data into your own systems via API.

Features

• Five sources: fda-food, fda-drug, fda-device, cpsc, nhtsa.
• Date range or "last N days" (default 30).
• Keyword filter (product, description, reason, firm) and firm/manufacturer filter.
• FDA classification filter (Class I / II / III).
• NHTSA lookup by make, model and model year.
• Only new mode: remembers seen recall IDs in a named key-value store, so scheduled runs return only new recalls.
• Optional raw record for each result.

Input example

{
  "sources": ["cpsc", "fda-food"],
  "lastNDays": 14,
  "keywords": ["peanut", "undeclared", "lithium"],
  "fdaClassifications": ["Class I"],
  "maxResults": 200,
  "onlyNew": true
}

NHTSA example (make and model year are required, model optional):

{ "sources": ["nhtsa"], "nhtsaMake": "Ford", "nhtsaModel": "F-150", "nhtsaModelYears": ["2020", "2021"] }

The default input (no changes) returns up to 100 recalls from the last 30 days across CPSC and FDA, in under a minute. NHTSA is queried per vehicle, so the date range is not applied to it.

Output example

{
  "source": "cpsc",
  "recallId": "27017",
  "date": "2026-10-08",
  "product": "Decathlon America Recalls Van Rysel GRVL AF Bicycles Due to Risk of Serious Injury or Death from Crash Hazard",
  "description": "This recall involves adult multi-terrain gravel bicycles ...",
  "reason": "The recalled bicycles' front lock nut can loosen during use, causing the front wheel to dislodge ...",
  "firm": "Decathlon America LLC, of San Francisco, California",
  "classification": "None reported",
  "distribution": "Recreational Equipment, Inc. (REI) ...",
  "remedy": "Consumers should stop using the recalled bicycles immediately ...",
  "url": "https://www.cpsc.gov/Recalls/2027/..."
}

Fields: source, recallId, date, product, description, reason, firm, classification, distribution, remedy, url (plus raw when enabled). For FDA, classification is Class I/II/III and distribution is the distribution pattern (states). For CPSC, classification holds reported injuries. For NHTSA it flags "Park it" / "Park outside" warnings.

How to schedule recall alerts

1. Set your filters and tick Only new recalls.
2. Click Schedule (Actor page, top right) and pick a cron such as 0 8 * * * for daily.
3. Add an integration (email, Slack, Google Sheets, webhook, Zapier, Make) triggered on run success.
4. Each run now returns only recalls not seen before. Use a different State store name per monitor.

Pricing

Pay per result: about $2 per 1,000 recalls (event recall-result). You only pay for recalls actually returned; set Max results to cap spend. Only new mode keeps scheduled runs cheap.

FAQ

Where does the data come from? Official US government APIs: openFDA (FDA enforcement reports), CPSC Recalls API and NHTSA recalls API.

How fresh is it? As fresh as the agencies publish. FDA enforcement reports update weekly; CPSC and NHTSA update as recalls are posted.

Do I need an API key? No. An optional openFDA key raises rate limits for very large pulls.

Why did NHTSA return nothing? NHTSA needs a make and at least one model year. Leave model empty to check every model of that make and year.

Is this legal advice or medical advice? No. Data is provided as published by agencies and may be incomplete. Verify with the source URL before acting.

Can I get the full original record? Enable Include raw record.

Built by Winters Works. Issues and feature requests are welcome in the Issues tab.

Is it legal? (public data only)

Yes, in the sense that it only reads public or official data: official US government APIs (openFDA, CPSC, NHTSA). It does not log in, bypass paywalls or access private data. You remain responsible for how you use the results, including privacy, copyright and marketing laws. Not affiliated with or endorsed by the data sources.

Quick start and cost

Run it with the prefilled input to see sample output in seconds; the default run costs only a few cents at most. Then adjust the input and schedule it.

Use from code and AI agents

Call it from any language with the Apify API, or let an AI agent find and run it through the Apify MCP server.

from apify_client import ApifyClient
run = ApifyClient("<YOUR_APIFY_TOKEN>").actor("wintersworks/us-product-recalls-monitor").call(run_input={"sources": ["cpsc", "fda-food", "fda-drug", "fda-device"], "lastNDays": 30, "maxResults": 10})
items = ApifyClient("<YOUR_APIFY_TOKEN>").dataset(run["defaultDatasetId"]).list_items().items

Results land in the run's dataset (JSON, CSV, Excel). Set a maximum charge per run in the run options to cap spend.

About

Built and maintained by Winters Works. Questions or feature requests: open an issue on the Actor page or email wintersworks.shop@gmail.com.