Product Recall Aggregator — FDA, NHTSA & CPSC avatar

Product Recall Aggregator — FDA, NHTSA & CPSC

Pricing

Pay per usage

Go to Apify Store
Product Recall Aggregator — FDA, NHTSA & CPSC

Product Recall Aggregator — FDA, NHTSA & CPSC

Unified US product-recall feed across FDA (food, drug, device), NHTSA (vehicles) and CPSC (consumer products), normalized to one schema. For compliance, insurance, legal and retail monitoring. Pay per result.

Pricing

Pay per usage

Rating

0.0

(0)

Developer

ziv shay

ziv shay

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

2 days ago

Last modified

Categories

Share

Product recall data from all three official US agencies in one normalized feed — an FDA recall scraper, NHTSA vehicle recalls, and CPSC consumer-product recalls merged into a single recall API feed.

Built for compliance, insurance, legal, and retail/QA monitoring teams who need to watch every US product recall without stitching together three different government feeds. Each agency publishes its own official data in its own shape — this actor pulls FDA (openFDA food/drug/device), NHTSA (vehicles), and CPSC (consumer products), then normalizes and dedupes them into one schema. No API key required; it's the official public recall data, just unified.

If you monitor recalls today you're probably querying openFDA, NHTSA, and CPSC separately and reconciling fields by hand. This does CPSC NHTSA recalls plus FDA in a single run, ready to drop into a dataset or alert pipeline.

What you get

FieldDescription
agencySource agency: FDA, NHTSA, or CPSC
categoryRecall category: food, drug, device, vehicle, or product
titleRecall title / product description
brandBrand or manufacturer name
hazardThe hazard or reason for the recall
dateRecall date (ISO 8601)
urlLink to the official recall notice
remedyRecommended remedy / corrective action

Input

FieldTypeDefaultDescription
categoriesarray["all"]Which categories to pull. Use "all" or a subset of food, drug, device, vehicle, product
daysBackinteger90Only return recalls issued within the last N days
maxItemsinteger500Maximum number of recalls to return

Example input

{
"categories": ["food", "drug", "vehicle"],
"daysBack": 30,
"maxItems": 200
}

Example run output

{
"agency": "FDA",
"category": "food",
"title": "Listeria Risk in Pre-Cut Cantaloupe Trays",
"brand": "FreshFields Produce",
"hazard": "Potential Listeria monocytogenes contamination",
"date": "2026-06-12",
"url": "https://www.fda.gov/safety/recalls-market-withdrawals-safety-alerts/freshfields-cantaloupe",
"remedy": "Do not consume. Return to place of purchase for a full refund."
}

Use cases

  • Compliance teams monitoring whether any recalled product touches their supply chain across food, drug, device, and consumer goods.
  • Insurance underwriters and claims teams tracking vehicle and product recalls tied to liability exposure.
  • Legal / litigation researchers building recall timelines for product-liability matters.
  • Retail and QA monitoring teams pulling a single daily feed of all US recalls instead of three separate agency checks.

Why this vs single-agency feeds

The wedge is the unified schema. Most tools and feeds give you one agency at a time, in different shapes — openFDA looks nothing like the NHTSA recalls API, which looks nothing like CPSC. This actor merges FDA + NHTSA + CPSC into one normalized, deduped dataset so you monitor all US recalls in a single run. It's the official public recall data — the value is that it's consolidated, not exclusive.

Pricing

Pay per result — you're billed only for the recall records returned, no subscription.

Keywords

product recall data, FDA recall scraper, recall API feed, CPSC NHTSA recalls, FDA NHTSA CPSC recalls, openFDA recall scraper, vehicle recall data, consumer product recall feed, food recall API, drug recall data