# US Recall Alerts: Products, Vehicles, Food, Drugs (`texxupport/all-agency-recall-alerts`) Actor

One feed for US recalls from the CPSC (consumer products), NHTSA (vehicles), and FDA (food, drugs, devices). Filter by keyword, agency and date, get clean rows with hazards and remedies, and schedule runs to get only new recalls.

- **URL**: https://apify.com/texxupport/all-agency-recall-alerts.md
- **Developed by:** [Kye Williams](https://apify.com/texxupport) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $4.00 / 1,000 recall delivereds

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

## US Recall Alerts: Products, Vehicles, Food, Drugs

One feed of US recalls from three federal agencies, in one clean format:

- **CPSC**: consumer products (toys, furniture, electronics, appliances, baby gear)
- **NHTSA**: vehicles, vehicle equipment, tires and child car seats
- **FDA**: food, drugs and medical devices

Filter by agency, keyword, date and FDA risk class, and run it on a schedule to get an alert-style feed of new recalls only. It needs no API key, no proxies and no login.

### Who it is for

- **Online sellers and retailers** who need to know when a recall hits a product category.
- **Compliance, insurance and risk teams** tracking recalls for a brand, supplier or hazard.
- **Food, health and automotive businesses** watching their own sector.
- **Journalists and researchers** who need recall data as a spreadsheet or JSON.
- **AI agents and automations** that need one simple "what was recalled lately?" tool.

### What you get

One row per recall, newest first, with the same main fields for every agency:

| Field | Meaning |
| --- | --- |
| `agency`, `category` | Where the recall comes from and what kind it is (Consumer product, Vehicle, Equipment, Tire, Child seat, Food, Drug, Medical device). |
| `recallId`, `recallNumber`, `recallDate` | Identifiers and the date used for filtering. |
| `title`, `summary`, `hazard` | What was recalled and why. |
| `severity` | FDA risk class (Class I is the most serious). Empty for CPSC and NHTSA. |
| `firms`, `products`, `remedy`, `status` | Companies, products or vehicles, the fix offered, and the FDA status. |
| `url` | The agency page for the recall. |
| `details` | Everything agency-specific: CPSC injuries, retailers and UPCs; NHTSA component, affected units, vehicle list and "do not drive" flag; FDA distribution, quantity, lot codes and dates. |

Example row (illustrative values):

```json
{
  "agency": "FDA",
  "category": "Food",
  "recallId": "fda-F-1001-2026",
  "recallDate": "2026-09-23",
  "title": "Example Sprouts, LLC: Crunchy Protein Sprout Mix, 5 oz",
  "hazard": "May be contaminated with Salmonella.",
  "severity": "Class I",
  "firms": ["Example Sprouts, LLC"],
  "status": "Ongoing",
  "url": "https://www.accessdata.fda.gov/scripts/ires/index.cfm?Event=90001"
}
```

### Input

| Field | What it does |
| --- | --- |
| `agencies` | Which sources to read. Default: all five (CPSC, NHTSA, FDA food, FDA drugs, FDA devices). |
| `keywords` | Keep only recalls that mention at least one of these words or phrases. Empty keeps everything. |
| `excludeKeywords` | Drop any recall that mentions one of these. |
| `fdaClasses` | Keep only FDA recalls in these risk classes. Does not affect CPSC or NHTSA. |
| `daysBack`, `dateFrom`, `dateTo` | The date window. Default: the last 30 days. |
| `onlyNew` | Deliver only recalls this Actor has not already delivered for this exact combination of agencies, keywords and classes. |
| `maxResults` | Stop after this many recalls. Default 100, up to 10,000. |

### Alerts on a schedule

1. Set `onlyNew` to true and add your `agencies` and `keywords`.
2. Schedule the Actor (for example daily) from the Apify Console.
3. Each run delivers only recalls you have not seen. If a run stops early because of your maximum cost per run, the recalls it did not deliver are delivered by the next run.

The "already delivered" list is kept in a storage called `all-agency-recall-alerts-state` in your own Apify account, with one list per distinct search.

### Pricing

You pay per recall delivered (pay per event), plus Apify's normal platform usage for the run. See the Pricing tab for the current price. Set a maximum cost per run in the run options to cap spending: the Actor stops as soon as the cap is reached.

### Limits and good to know

- **FDA rows are one per recalled product.** A single FDA recall event with several products becomes several rows. The `details.eventId` field groups them.
- **NHTSA rows are one per recall campaign**, with every affected make, model and year listed. NHTSA publishes no date-range service, so this Actor reads NHTSA's daily file of all recalls since 2010. The date used is the day NHTSA received the manufacturer's report, which can be a little earlier than the public announcement.
- If one agency's service is down, the run still delivers the others and says in its status which agency could not be read. Its recalls arrive in a later run.
- openFDA allows a limited number of requests per day without a key. Normal use is far below it.
- Data is shown as each agency published it, and recalls can be updated afterwards. Check the agency page linked in each row before acting.
- This is information, not legal, medical or compliance advice.

### Data sources and disclaimer

Recall data comes from the public services of the U.S. Consumer Product Safety Commission (cpsc.gov), the National Highway Traffic Safety Administration (nhtsa.gov) and the U.S. Food and Drug Administration (open.fda.gov). This Actor is not affiliated with or endorsed by any government agency. openFDA data is provided by the FDA and is unvalidated; do not use it to make decisions about medical care.

### Support

Found a problem or want another field? Open an issue on this Actor's Issues tab.

# Actor input Schema

## `agencies` (type: `array`):

Which recall sources to read.

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

Only keep recalls that mention at least one of these words or phrases in the title, description, product, firm or hazard. Leave empty to keep every recall.

## `excludeKeywords` (type: `array`):

Drop any recall that mentions one of these words or phrases.

## `fdaClasses` (type: `array`):

FDA recalls are rated Class I (most serious), II or III. Only FDA recalls in the chosen classes are kept. This does not affect CPSC or NHTSA recalls.

## `daysBack` (type: `integer`):

How many days before the end date to look. Ignored when you fill in a start date.

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

First recall date to include, written YYYY-MM-DD.

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

Last recall date to include, written YYYY-MM-DD. Defaults to today (UTC).

## `onlyNew` (type: `boolean`):

Turn this on and run the Actor on a schedule to get an alert-style feed. The Actor remembers which recalls it already delivered for this exact combination of agencies and keywords.

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

Stop after this many recalls. You pay per recall delivered, so this also caps your cost.

## Actor input object example

```json
{
  "agencies": [
    "cpsc",
    "nhtsa",
    "fda-food",
    "fda-drug",
    "fda-device"
  ],
  "keywords": [
    "helmet",
    "airbag",
    "peanut"
  ],
  "fdaClasses": [
    "Class I",
    "Class II",
    "Class III"
  ],
  "daysBack": 30,
  "onlyNew": false,
  "maxResults": 100
}
```

# Actor output Schema

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

Every recall delivered by this run, as a table you can download as CSV, Excel or JSON.

# 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 = {
    "agencies": [
        "cpsc",
        "nhtsa",
        "fda-food",
        "fda-drug",
        "fda-device"
    ],
    "keywords": [
        "helmet",
        "airbag",
        "peanut"
    ],
    "fdaClasses": [
        "Class I",
        "Class II",
        "Class III"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("texxupport/all-agency-recall-alerts").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 = {
    "agencies": [
        "cpsc",
        "nhtsa",
        "fda-food",
        "fda-drug",
        "fda-device",
    ],
    "keywords": [
        "helmet",
        "airbag",
        "peanut",
    ],
    "fdaClasses": [
        "Class I",
        "Class II",
        "Class III",
    ],
}

# Run the Actor and wait for it to finish
run = client.actor("texxupport/all-agency-recall-alerts").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 '{
  "agencies": [
    "cpsc",
    "nhtsa",
    "fda-food",
    "fda-drug",
    "fda-device"
  ],
  "keywords": [
    "helmet",
    "airbag",
    "peanut"
  ],
  "fdaClasses": [
    "Class I",
    "Class II",
    "Class III"
  ]
}' |
apify call texxupport/all-agency-recall-alerts --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,texxupport/all-agency-recall-alerts"
        }
    }
}
```

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/B1ZFhZwDRbFrdfMGw/builds/gH7Q5fT6pXFsLVEgU/openapi.json