# US Product Recall Monitor (CPSC) (`texxupport/cpsc-recall-monitor`) Actor

- **URL**: https://apify.com/texxupport/cpsc-recall-monitor.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 Product Recall Monitor (CPSC)

Get clean, structured data on US consumer product recalls published by the U.S. Consumer Product Safety Commission (CPSC). Filter by keyword and date, and run it on a schedule to get an alert-style feed of new recalls only.

The Actor reads the CPSC's public recall service at run time. It needs no API key, no proxies and no login.

### Who it is for

- **Online sellers** (marketplaces, print-on-demand, dropshipping, handmade) who want to know when a recall hits their product category.
- **Compliance, insurance and risk teams** tracking recalls for a brand, retailer or hazard type.
- **Journalists and researchers** who need recall data as a spreadsheet or JSON.
- **AI agents and automations** that need a simple, reliable "what was recalled lately?" tool.

### What you get

One row per recall, newest first. Each row includes the recall date, title, CPSC page link, description, products (name, model, type, units), hazards, injuries, remedies and remedy options (refund, repair, replace), manufacturers, retailers, importers, distributors, countries of manufacture, UPCs and image links.

Two yes/no flags are worked out from the recall text. Treat them as hints and check the CPSC page:

- `injuryReported`: true when the injury text reports any injury, false when it says none, null when there is no injury text.
- `deathMentioned`: true when the text mentions a death or "fatal". It can also be true when the text describes a risk ("potentially fatal burns") rather than a reported death.

Example row (illustrative values):

```json
{
  "recallId": 20001,
  "recallNumber": "26801",
  "recallDate": "2026-09-30",
  "title": "ExampleCo Recalls Children's Bike Helmets Due to Impact Hazard",
  "url": "https://example.test/recalls/20001",
  "productNames": ["ExampleCo Kids Bike Helmet"],
  "hazards": ["The helmet can fail to protect in a crash, posing a risk of head injury."],
  "injuryReported": false,
  "deathMentioned": false,
  "remedyOptions": ["Refund"],
  "retailers": ["Example Online Store"],
  "manufacturerCountries": ["China"]
}
```

### Input

| Field | What it does |
| --- | --- |
| `keywords` | Keep only recalls that mention at least one of these words or phrases in the title, description, product, brand, retailer or hazard. Empty keeps everything. |
| `excludeKeywords` | Drop any recall that mentions one of these. |
| `daysBack` | How many days before the end date to look. Default 30. Ignored when you set `dateFrom`. |
| `dateFrom` | First recall date to include, written YYYY-MM-DD. |
| `dateTo` | Last recall date to include, written YYYY-MM-DD. Default today (UTC). |
| `onlyNew` | Deliver only recalls this Actor has not already delivered to you. Run it on a schedule for alerts. |
| `maxResults` | Stop after this many recalls. Default 100, up to 10,000. |

Keywords are matched by this Actor, so the service is only asked for the date range. A very wide range downloads thousands of recalls, so use `dateFrom` and `dateTo` or `daysBack` to keep runs small.

### Alerts on a schedule

1. Set `onlyNew` to true and add your `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 `cpsc-recall-monitor-state` in your own Apify account.

### 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

- Covers **consumer products** regulated by the CPSC. Vehicle recalls (NHTSA) and food, drug and medical device recalls (FDA) are not included.
- Data is shown as the CPSC published it. Recalls can be updated after publication. Check the CPSC page linked in each row before acting on a recall.
- This is information, not legal or compliance advice.
- If the CPSC service is down or slow, the Actor retries a few times and then stops with a clear message.

### Data source and disclaimer

Recall data comes from the public Recalls service of the U.S. Consumer Product Safety Commission (cpsc.gov). This Actor is not affiliated with or endorsed by the CPSC or any government agency.

### Support

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

# Actor input Schema

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

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

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

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

## `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 to you.

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

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

## Actor input object example

```json
{
  "keywords": [
    "helmet",
    "stroller",
    "candle"
  ],
  "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 = {
    "keywords": [
        "helmet",
        "stroller",
        "candle"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("texxupport/cpsc-recall-monitor").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 = { "keywords": [
        "helmet",
        "stroller",
        "candle",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("texxupport/cpsc-recall-monitor").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 '{
  "keywords": [
    "helmet",
    "stroller",
    "candle"
  ]
}' |
apify call texxupport/cpsc-recall-monitor --silent --output-dataset

```

## MCP server setup

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

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/xnKnYb3ArHVpJ3h1q/builds/0YdYj1OfvLMlgVfFe/openapi.json