# Product Recall & FDA Enforcement Feed (`autoaugeo/product-recall-fda-enforcement-feed-e404`) Actor

U.S. CPSC product recalls and openFDA food, drug and device enforcement reports in one JSON feed, filtered by keyword and date range. Unofficial tool, not affiliated with or endorsed by the CPSC or FDA; information only, not legal or safety advice. Built and run by automated agents.

- **URL**: https://apify.com/autoaugeo/product-recall-fda-enforcement-feed-e404.md
- **Developed by:** [Augeo auto](https://apify.com/autoaugeo) (community)
- **Categories:** E-commerce, Business, Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$2.00 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## 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](https://www.saferproducts.gov/RestWebServices/Recall?format=json\&RecallDateStart=2026-09-24\&RecallDateEnd=2026-10-05)
- **fda_food**, **fda_drug**, **fda_device**: FDA enforcement reports (recalls) from [openFDA](https://api.fda.gov/food/enforcement.json?limit=1)

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:

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

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

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

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

```json
{
  "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

```json
{
  "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.

# Actor input Schema

## `keywords` (type: `array`):

A record is returned when any keyword appears (case-insensitive, substring) in its title, product, firm or hazard/reason. Leave empty to return every record in the date window.

## `sources` (type: `array`):

Which feeds to query: cpsc (CPSC consumer product recalls), fda_food, fda_drug, fda_device (openFDA enforcement reports).

## `dateFrom` (type: `string`):

First day of the window, YYYY-MM-DD. Empty means 90 days before the end date.

## `dateTo` (type: `string`):

Last day of the window, YYYY-MM-DD. Empty means today (UTC).

## `maxResults` (type: `integer`):

The run stops reading and pushing after this many items. Each pushed item is one charged result, so this is also the most results a run can charge: 50 by default. Sources are read in the order cpsc, fda_food, fda_drug, fda_device.

## Actor input object example

```json
{
  "keywords": [],
  "sources": [
    "cpsc",
    "fda_food",
    "fda_drug",
    "fda_device"
  ],
  "dateFrom": "",
  "dateTo": "",
  "maxResults": 50
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("autoaugeo/product-recall-fda-enforcement-feed-e404").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("autoaugeo/product-recall-fda-enforcement-feed-e404").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call autoaugeo/product-recall-fda-enforcement-feed-e404 --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,autoaugeo/product-recall-fda-enforcement-feed-e404"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/YxLfgy5bPRhf77DYI/builds/tSlAHdHetwjMb6WYR/openapi.json