# Product Recall Scraper — CPSC Safety Recalls (`hichemdev/product-recalls-scraper`) Actor

Scrape official US CPSC product safety recalls: recall number and date, product, units affected, hazard, injuries reported, remedy (refund, repair, replace), recalling firm, importers, country of manufacture, where it was sold and product images. Filter by date, product or keyword. No API key.

- **URL**: https://apify.com/hichemdev/product-recalls-scraper.md
- **Developed by:** [Hichem Ben Moussa](https://apify.com/hichemdev) (community)
- **Categories:** Business, E-commerce, News
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.00 / 1,000 recalls

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

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 Scraper — CPSC Safety Recalls & Hazards

Scrape **official US product safety recalls** from the Consumer Product Safety Commission — the authoritative source for recalls of consumer goods, from nursery products and appliances to power tools and lithium-battery devices.

Get the recall number and date, the product and units affected, the hazard, reported injuries, the remedy offered, the recalling firm and every company named, country of manufacture, where it was sold, and product images.

No API key required.

### What you get

| Field | Description |
|---|---|
| `recallNumber` | CPSC recall number |
| `recallDate` | Date the recall was announced |
| `title` | Official recall headline |
| `description` | Full recall description, HTML stripped |
| `productName`, `productType`, `productModel` | The recalled product and its CPSC category |
| `unitsAffected` | Units in the US market, as a **number** |
| `unitsAffectedText` | The CPSC's own wording, e.g. *"About 177 (In addition, about 52 were sold in Canada)"* |
| `hazardDescription` | What can go wrong, in the CPSC's words |
| `injuriesDescription` | Incidents and injuries reported to date |
| `remedyOptions` | Clean remedy categories: **Refund**, **Repair**, **Replace** |
| `remedyInstructions` | Exactly what consumers are told to do |
| `recallingFirm` | The firm behind the recall |
| `manufacturers`, `importers`, `distributors` | Companies named in the notice |
| `manufacturerCountries` | Where the product was made |
| `soldAt` | Retailers, channels, date range and price point |
| `consumerContact` | Phone, e-mail and web contact for the recall |
| `image`, `imageCaption` | Product photo |
| `url` | Full recall notice on cpsc.gov |

### Example input

```json
{
  "recallDateStart": "2026-01-01",
  "keyword": "lithium",
  "maxRecalls": 100
}
```

Filter at the source with `productName`, `recallTitle` or `manufacturer`, or filter the returned set with `keyword`, which matches the title, description, product, hazard, seller and companies together.

Leave the dates empty and the actor pulls the **last 12 months**, newest first, so a default run stays fast instead of downloading the whole archive.

### Example output

```json
{
  "recallNumber": "26746",
  "recallDate": "2026-09-11",
  "title": "MONDRAKER USA Recalls Mountain Bicycles Equipped with ONOFF Handlebars",
  "productName": "Mondraker mountain bicycles equipped with ONOFF S9 Carbon MTB handlebars.",
  "productType": "Bicycles & Accessories",
  "unitsAffected": 177,
  "unitsAffectedText": "About 177 (In addition, about 52 were sold in Canada)",
  "hazardDescription": "The affected handlebars may crack or fracture during use, which can lead to loss of control, posing a risk of serious injury or death from fall hazard.",
  "injuriesDescription": "The firm has received five reports of the handlebars breaking, including two injuries involving a fall resulting in minor abrasions.",
  "remedyOptions": ["Replace"],
  "recallingFirm": "MONDRAKER USA, LLC, of Boulder, Colorado",
  "manufacturerCountries": ["Taiwan"],
  "soldAt": "Evolucion Innovations, The Path Bike Shop and bicycle stores nationwide from December 2024 through June 2026 for about $5,000 to $12,000.",
  "url": "https://cpsc.gov/Recalls/2026/MONDRAKER-USA-Recalls-Mountain-Bicycles..."
}
```

### Who uses this

- **Retail and marketplace compliance** — pull new recalls daily and delist affected products before a regulator or a customer finds them
- **Product safety and QA teams** — watch hazards and countries of manufacture in your own category
- **Product-liability lawyers** — build a timeline of recalls for a manufacturer or a product class
- **Insurers and risk analysts** — recall frequency and units affected by firm and category
- **Consumer apps and newsletters** — a live recall feed with images, hazards and remedies
- **Supply-chain teams** — catch a component recall that reaches your own bill of materials

A common setup is a scheduled daily run with `recallDateStart` set to the last week, feeding a webhook that alerts your team on any new recall matching your brands or categories.

### What this data does and does not contain

- **Scope is US consumer products.** Vehicles and tires are regulated by NHTSA, and food, drugs and cosmetics by the FDA, so those recalls are not in this dataset.
- **`hazardTypes` is usually empty.** The CPSC has a coded hazard-category field but has stopped populating it on recent recalls, so the actor returns it when present and gives you the full `hazardDescription` in every case. Filter on the description text rather than the codes.
- **`productUPCs` is rarely populated.** Most notices identify products by model and description instead of barcode. The field is included for the records that do carry UPCs, but do not build a barcode-matching pipeline on the assumption it is always there.
- **`soldAt` is a sentence, not a list.** The CPSC publishes retailers, channels, dates and prices as one block of prose, so the actor exposes it as text rather than inventing a structured retailer list from it.
- **`manufacturers` is often empty while `importers` is filled** — for imported goods the CPSC names the US importer as the responsible firm. Use `recallingFirm`, which falls back through manufacturer, importer and distributor.
- `unitsAffected` and `injuriesDescription` reflect what was published at announcement; the CPSC sometimes revises figures later.

### Pricing

Pay per result. Each recall returned counts as one result. A daily monitoring run typically returns only a handful of records, so continuous monitoring stays inexpensive.

### Notes

- Data comes from the CPSC's public recall web service.
- This is an unofficial actor and is not affiliated with the CPSC.

# Actor input Schema

## `recallDateStart` (type: `string`):

Earliest recall date, as YYYY-MM-DD. Defaults to the last 12 months when left empty.

## `recallDateEnd` (type: `string`):

Latest recall date, as YYYY-MM-DD. Leave empty for today.

## `keyword` (type: `string`):

Keep only recalls whose title, description, product, hazard or manufacturer mentions this word - for example lithium, choking or fire.

## `productName` (type: `string`):

Filter by product name at the source, e.g. stroller, helmet, space heater.

## `recallTitle` (type: `string`):

Filter by words in the official recall headline.

## `manufacturer` (type: `string`):

Filter by the recalling firm or manufacturer name.

## `maxRecalls` (type: `integer`):

Stop after this many recalls.

## `proxyConfiguration` (type: `object`):

Optional. A proxy is not required for this actor.

## Actor input object example

```json
{
  "recallDateStart": "2026-01-01",
  "maxRecalls": 50,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

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

All scraped items as JSON.

## `overview` (type: `string`):

Browse results in the Apify Console.

# 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 = {
    "recallDateStart": "2026-01-01",
    "maxRecalls": 50
};

// Run the Actor and wait for it to finish
const run = await client.actor("hichemdev/product-recalls-scraper").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 = {
    "recallDateStart": "2026-01-01",
    "maxRecalls": 50,
}

# Run the Actor and wait for it to finish
run = client.actor("hichemdev/product-recalls-scraper").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 '{
  "recallDateStart": "2026-01-01",
  "maxRecalls": 50
}' |
apify call hichemdev/product-recalls-scraper --silent --output-dataset

```

## MCP server setup

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

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/0hjfnDGGhasdZw5bB/builds/3hFLbdWYu5TjhIQye/openapi.json