# US Product, Food & Drug Recalls - CPSC and FDA Search (`kdhan/us-product-recalls`) Actor

Search official US recalls by product or company name: CPSC consumer product recalls plus FDA food, drug and device enforcement reports. Hazard or reason, recalling firm, FDA class, status, remedy and official link. Keyless public APIs, no personal data.

- **URL**: https://apify.com/kdhan/us-product-recalls.md
- **Developed by:** [Doohan Kim](https://apify.com/kdhan) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.00 / 1,000 recall records

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, Food & Drug Recalls - CPSC and FDA Search

Search official US recalls by product or company name in one run. Sources (public, no API key):

- **cpsc** - Consumer Product Safety Commission recalls (saferproducts.gov).
- **fda-food**, **fda-drug**, **fda-device** - FDA enforcement reports via openFDA.

### Input (all optional)

| Field | Meaning |
|---|---|
| `searchTerms` | Product or company names, e.g. `crib`, `Kroger`. Empty = latest recalls of the last 30 days. |
| `sources` | `cpsc`, `fda-food`, `fda-drug`, `fda-device`. Default: all four. |
| `recalledAfter` | `YYYY-MM-DD`. Only recalls started on or after this date. |
| `hazardKeyword` | Keep only recalls whose hazard/reason text contains this word. |
| `maxResultsPerTerm` | 1-100 per search term and source (default 10). |

### Output (one row per recall)

`source`, `recallId`, `recallNumber`, `recallDate`, `reportDate`, `title` (CPSC), `productName`, `description`,
`hazard` (CPSC hazard text / FDA reason for recall), `recallingFirm`, `classification` (FDA Class I-III; CPSC has none),
`status` (FDA), `regions` (CPSC: country of manufacture; FDA: firm city/state and distribution pattern),
`unitsAffected`, `remedy` and `remedyOptions` (CPSC only; openFDA has no consumer action field), `url`,
`dataAsOf`, `dataAsOfBasis`, `disclaimer`.

FDA rows link to the openFDA record (the enforcement report query by recall number); CPSC rows link to the cpsc.gov notice.

### Honest limits

- A search that matches nothing returns a `found: false` row (free). A source that fails returns `found: null`
  with an `error` - that does **not** mean there is no recall.
- CPSC has no dataset timestamp: its `dataAsOf` is the retrieval time. FDA `dataAsOf` is openFDA `meta.last_updated`.
- openFDA allows 240 requests/minute and 1,000/day per IP without a key. The Actor waits 0.5 s between requests,
  backs off on HTTP 429 and stops at 300 requests per run.
- Email addresses and phone numbers are removed from text fields; street addresses of FDA firms are not returned.
- Not affiliated with CPSC or FDA. openFDA: "Do not rely on openFDA to make decisions regarding medical care."
  Always confirm on the official recall notice. Data credit: "Data provided by the U.S. Food and Drug Administration
  (https://open.fda.gov)" and the U.S. Consumer Product Safety Commission.

### Pricing event

`recall-record` - one per recall row returned (not-found and failed rows are free).

# Actor input Schema

## `searchTerms` (type: `array`):

Product or company names, for example crib or Kroger. Leave empty for the latest recalls.

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

cpsc, fda-food, fda-drug, fda-device. Default: all four.

## `recalledAfter` (type: `string`):

Only recalls started on or after this date. With no search terms the default is 30 days ago.

## `hazardKeyword` (type: `string`):

Optional. Keep only recalls whose hazard or reason text contains this word, for example choking or salmonella.

## `maxResultsPerTerm` (type: `integer`):

Upper limit for each search term in each source. You are charged per recall record returned.

## Actor input object example

```json
{
  "sources": [
    "cpsc",
    "fda-food",
    "fda-drug",
    "fda-device"
  ],
  "maxResultsPerTerm": 10
}
```

# Actor output Schema

## `recalls` (type: `string`):

Recall records with hazard or reason, firm, classification, status, remedy, official link, data freshness and disclaimer.

# 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 = {
    "sources": [
        "cpsc",
        "fda-food",
        "fda-drug",
        "fda-device"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("kdhan/us-product-recalls").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 = { "sources": [
        "cpsc",
        "fda-food",
        "fda-drug",
        "fda-device",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("kdhan/us-product-recalls").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 '{
  "sources": [
    "cpsc",
    "fda-food",
    "fda-drug",
    "fda-device"
  ]
}' |
apify call kdhan/us-product-recalls --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,kdhan/us-product-recalls"
        }
    }
}
```

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/yhQ51ckXcEHdDqjPy/builds/b5OOtWTJxnd10dlei/openapi.json