Product Recall & FDA Enforcement Feed

Unofficial tool. Not affiliated with or endorsed by the U.S. CPSC or FDA. Data comes from the CPSC Recalls API and openFDA; it may be delayed or incomplete, is for information only and is not legal or safety advice.

Built and run by automated agents.

What it does

Give it keywords and a date window. It reads four public U.S. government feeds and returns the matching records in one flat schema:

• cpsc: consumer product recalls from the CPSC Recalls API
• fda_food, fda_drug, fda_device: FDA enforcement reports (recalls) from openFDA

Every item carries fetched_at, the UTC timestamp of the run that fetched it, so you always know how fresh a record is.

Who it is for

E-commerce sellers and sourcing teams who want to check a product type, a brand or a supplier name against recent recalls before listing or reordering, or to run the same check on a schedule and watch for new records.

Use cases

• Check a product category before listing it. Run keywords such as stroller, space heater or magnet against the last 90 days and read what was recalled and why before you source or list a similar item.
• Monitor a supplier or brand name for new CPSC recalls. Put the firm or brand name in keywords, select the cpsc source and run it on a schedule.
• Weekly FDA food, drug and device enforcement report watch. Select fda_food, fda_drug or fda_device, leave the keywords empty or add terms such as undeclared or sterility, and run it once a week.
• Feed recall alerts into a sheet or Slack. The Actor only writes a dataset; Apify integrations can pass the dataset of each run on to a spreadsheet or a Slack channel.
• Keep a compliance evidence log. Every item carries fetched_at, so a stored dataset shows which records the two sources returned for your keywords and when the check ran.

Input

Field	Type	Default	Meaning
keywords	array of strings	[] (no filter)	A record matches when any keyword is a case-insensitive substring of its title, product, firm or hazard/reason. Empty returns every record in the window.
sources	array	all four	Any of cpsc, fda_food, fda_drug, fda_device.
dateFrom	string YYYY-MM-DD	empty = 90 days before dateTo	Start of the window (CPSC recall date, FDA report date).
dateTo	string YYYY-MM-DD	empty = today (UTC)	End of the window.
maxResults	integer 1 to 1000	50	The run stops reading and pushing after this many items. It limits the number of paid results per run.

A run with an empty input {} uses these defaults: all four sources, no keyword filter, the last 90 days and at most 50 results. Sources are read in the order cpsc, fda_food, fda_drug, fda_device; once maxResults is reached the remaining sources are not read. To see a later source, select only that source or raise maxResults.

Example inputs

CPSC recalls that mention strollers or cribs in the last 90 days:

{
  "keywords": ["stroller", "crib"],
  "sources": ["cpsc"]
}

FDA food enforcement reports that mention an undeclared ingredient or an allergen, up to 100 items:

{
  "keywords": ["undeclared", "allergen"],
  "sources": ["fda_food"],
  "maxResults": 100
}

Every record from all four sources in one 7-day window:

{
  "keywords": [],
  "sources": ["cpsc", "fda_food", "fda_drug", "fda_device"],
  "dateFrom": "2026-09-29",
  "dateTo": "2026-10-05",
  "maxResults": 1000
}

Output

One dataset item per matching record. The Output tab of a run shows an Overview table with the date, source, title, firm, hazard or reason, FDA class, FDA status and record link; the full items hold all 13 fields below.

Field	Meaning
source	cpsc, fda_food, fda_drug or fda_device
recall_id	CPSC recall number or FDA recall number
date	ISO date (YYYY-MM-DD): CPSC recall date or FDA report date
title	CPSC recall title; for FDA, the firm plus a shortened product description
product	Product name(s) (CPSC) or full product description (FDA)
firm	Manufacturer, importer or distributor (CPSC; the seller text when none is listed) or recalling firm (FDA)
hazard_or_reason	CPSC hazard text or FDA reason for recall
classification	FDA class (Class I, Class II, Class III); null for CPSC
status	FDA recall status (for example Ongoing, Terminated); null for CPSC
remedy	CPSC remedy text; null for FDA
distribution	FDA distribution pattern; null for CPSC
url	Official record page when the source provides one (CPSC); null for FDA
fetched_at	ISO timestamp of the run that fetched the record

Sample item

{
  "source": "fda_food",
  "recall_id": "H-1258-2026",
  "date": "2026-09-02",
  "title": "H & U Inc. dba Sun Noodle - Sura Tanmen Hot and Sour Flavor Premium Japanese Noodles & Soup Base. Retail package net wt. 15.4oz. Product is ramen noodle kit which co...",
  "product": "Sura Tanmen Hot and Sour Flavor Premium Japanese Noodles & Soup Base. Retail package net wt. 15.4oz. Product is ramen noodle kit which contains noodles and Soba soup packet. Item #05410 retail package, UPC 085315054108 Item #05410.1 cardboard box (12 packages per case), UPC 085315054105 Product is Perishable Frozen or Refrigerated and made by Sun Noodle Hawaii 1933 Colburn Street, Honolulu, HI",
  "firm": "H & U Inc. dba Sun Noodle",
  "hazard_or_reason": "Soba sauce packet, which contains bonito, sardine, and mackerel (fish), was packed into Sura Tanmen Hot and Sour Flavor ramen noodle package kit, but fish species are not declared on finished product label.",
  "classification": "Class I",
  "status": "Terminated",
  "remedy": null,
  "distribution": "Distribute in HI.",
  "url": null,
  "fetched_at": "2026-10-05T12:00:00.000Z"
}

Price

$0.002 per result. One result is one dataset item. Records that do not match, duplicates and failed requests are never pushed and never charged.

Limits

• Keyless openFDA access has a quota that is shared per IP address, so a run may return fewer FDA items than exist. When a source keeps failing after two retries the run logs it and continues with the other sources; if every source fails, the run fails and charges nothing.
• At most 10 requests per source per run. For each FDA source that means the newest 1,000 enforcement reports in the window are scanned; use a shorter window to go further back.
• Data may lag the agencies: openFDA enforcement data is updated about weekly, and a recall can be announced before it appears in either feed.
• Keyword matching is a plain substring match. It does not understand synonyms, plurals of irregular words or model numbers written differently.
• An empty result does not mean a product is safe or was never recalled.

Run it on a schedule

1. Leave dateFrom and dateTo empty. The window then always ends today (UTC) and starts 90 days earlier, so each scheduled run moves forward by itself.
2. Save the input as a task and add a schedule to it in Apify (daily or weekly; openFDA enforcement data is updated about weekly).
3. Dedupe downstream on source + recall_id. That pair identifies a record across runs.

The Actor itself keeps no memory between runs. Every run returns the whole window again, including records that earlier runs already returned, and every returned item is a charged result. To keep repeated runs small, set dateFrom to a recent day or lower maxResults.

FAQ

Is this an official CPSC or FDA tool? No. It is an unofficial tool that reads the public CPSC Recalls API and openFDA and is not affiliated with or endorsed by either agency.

Does it need an API key or a proxy? No. Both sources are read without a key, a login or a proxy.

Why did I get fewer FDA items than I expected? Keyless openFDA access has a quota shared per IP address, and a run makes at most 10 requests per source, which covers the newest 1,000 enforcement reports in the window for each FDA source. Use a shorter window to reach older records.

Does an empty result mean the product is safe? No. An empty result only means no record in the selected sources and window matched your keywords. The data can lag the agencies, and keyword matching is a plain substring match.

Sources

• U.S. Consumer Product Safety Commission (CPSC) Recalls API: https://www.saferproducts.gov/RestWebServices/Recall?format=json&RecallDateStart=2026-09-24&RecallDateEnd=2026-10-05
• openFDA enforcement reports, U.S. Food and Drug Administration: https://api.fda.gov/food/enforcement.json?limit=1

Both are public U.S. government data. No API key, login or proxy is used.