CPSC Product Recalls Scraper - SaferProducts Data
Pricing
from $5.00 / 1,000 results
CPSC Product Recalls Scraper - SaferProducts Data
Scrape full CPSC product recall data from SaferProducts.gov - retailers, UPCs, hazards, remedies, units affected. No API key. Export JSON/CSV for compliance monitoring.
Pricing
from $5.00 / 1,000 results
Rating
0.0
(0)
Developer
Brandt May
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
3 days ago
Last modified
Categories
Share
CPSC Product Recalls Scraper - Full SaferProducts.gov Recall Data
The deepest, cleanest CPSC recall feed on Apify - every recall flattened to one row with retailers, UPCs, hazards, remedies, and units affected. No API key required.
What it does
This CPSC product recalls scraper queries the official CPSC SaferProducts.gov recalls API and flattens deeply nested responses into one clean record per recall. Unlike a bare keyword scraper, it returns the full recall detail buyers actually need for automated compliance monitoring - recalling manufacturers, importers, and retailers, product UPCs, hazard descriptions, remedy options, and units affected. You can filter by keyword, product name, manufacturer, exact recall number, or date range, then export the US consumer product recalls dataset to JSON, CSV, or Excel. It requires no API key because it reads a public government data source. This is the CPSC leg of a three-agency recalls suite alongside FDA and NHTSA scrapers - combine all three for a single FDA + NHTSA + CPSC recall aggregator feed.
Who it's for
- Retail & e-commerce compliance teams removing recalled SKUs from shelves and listings
- Quality assurance & product-safety teams monitoring hazards across their catalog
- Online marketplaces screening third-party listings against active recalls
- Insurers assessing risk tied to recalled products and reported injuries
- Importers & distributors tracking recall activity by manufacturer
- Journalists & investigators reporting on recall trends and safety incidents
What you get / Output
Each run produces a flat dataset with one record per recall. Fields:
| Field | Description |
|---|---|
recallId | Internal CPSC recall record identifier |
recallNumber | Official CPSC recall number (e.g. 26596) |
recallDate | Date the recall was announced |
title | Recall headline |
description | Full recall description text |
products | Recalled product name(s) |
productModels | Affected model numbers / variants |
unitsAffected | Number of units recalled |
hazards | Hazard descriptions (fire, choking, suffocation, lithium battery, etc.) |
injuries | Reported injuries or incidents |
remedies | Remedy options (refund / repair / replace) |
manufacturers | Recalling manufacturer(s) |
retailers | Where the product was sold (retailer / channel) |
importers | Importer(s) of record |
upcs | Product UPC codes |
soldAt | Sold-at labels / storefront details |
imageUrl | Product image URL |
consumerContact | Consumer contact info for the recall |
url | Official CPSC recall webpage |
Input / How to query
Set any combination of filters. Leave a field empty to skip it.
| Input | What it does |
|---|---|
keyword | Full-text match across title, description, hazard, product, manufacturer, or retailer (e.g. fire, lithium battery, Amazon) |
productName | Case-insensitive partial match on product name (e.g. crib, heater) |
manufacturer | Case-insensitive partial match on manufacturer (e.g. Samsung) |
recallNumber | Exact lookup of one recall by number - overrides all other filters |
recalledSince | Only recalls on or after this date (YYYY-MM-DD) |
recalledUntil | Only recalls on or before this date (YYYY-MM-DD) |
Under the hood the actor walks history in year-window chunks and applies your keyword filter client-side, so date-range pulls stay complete and reliable.
Example use cases
- E-commerce compliance sweep - run
keyword=lithium batteryweekly to catch new battery-hazard recalls before they hit your marketplace listings. - Catalog match by manufacturer - pull every recall for a supplier via
manufacturer=Samsungand reconcile against your active SKUs. - UPC-level recall check - export the full feed and join on the
upcsfield to flag any recalled UPC in your inventory system. - Litigation research - use
recallNumberfor an exact recall, orproductNameto gather all recalls for a product family with hazards, injuries, and remedies attached. - Historical trend analysis - set
recalledSinceandrecalledUntilto pull a multi-year window for reporting on recall volume by hazard or category.
Recurring use / scheduling
This actor is built for automated monitoring, not one-off pulls. Use Apify Schedules to run it on a cron (e.g. every morning or every Monday) with a rolling recalledSince window so each run only returns fresh recalls. Because recallNumber is a stable unique key, you can deduplicate across runs by keying on recallNumber (or recallId) in your downstream store - append only records you haven't seen before, and wire new rows into alerts, a Slack/email notification, or your compliance dashboard.
FAQ
How do I get CPSC product recall data without an API key?
This actor reads the public CPSC SaferProducts.gov recalls API directly - no key, no signup, no auth. Set your filters and run it; results land in an Apify dataset ready to export.
Is there an API for SaferProducts.gov recalls?
Yes - CPSC publishes a public recalls API, and this actor wraps it into a clean, flat schema. You get one row per recall with retailers, UPCs, hazards, and remedies already unpacked from the raw nested JSON.
How can I monitor new product recalls automatically?
Schedule the actor on a cron with a rolling recalledSince date. Each run returns recent recalls; dedupe on recallNumber and push new rows to an alert or dashboard for hands-off monitoring.
How do I export CPSC recalls to CSV or Excel?
Every run writes a dataset you can download as CSV, Excel, JSON, or XML from the Apify console, or pull via the Apify API for a product recall JSON / CSV export into your own systems.
How do I search product recalls by UPC or manufacturer?
Filter by manufacturer for partial-match manufacturer search, or export the full feed and match on the upcs field to find recalls tied to a specific UPC in your catalog.
How do I get recall data with retailers, hazards, and remedies?
Those are first-class output fields here: retailers, hazards, and remedies (refund / repair / replace) come on every record, along with unitsAffected and injuries - the detail most bare recall scrapers drop.
How do I set up product recall alerts for my e-commerce store?
Schedule the actor, dedupe on recallNumber, and connect the new rows to a notification integration (email, Slack, webhook) or your monitoring stack so your store is alerted the moment a relevant recall posts.
What is the best way to track consumer product recalls for compliance?
Run a scheduled pull filtered to your product categories or hazards, store results keyed on recallNumber for a clean audit trail, and reconcile the products, upcs, and manufacturers fields against your inventory.
How do I pull historical CPSC recalls by date range?
Set recalledSince and recalledUntil (both YYYY-MM-DD). The actor chunks history into year windows so multi-year pulls come back complete.
Can I combine CPSC, FDA, and NHTSA recall data in one feed?
Yes - this is the CPSC leg of a three-agency suite. Pair it with the matching FDA and NHTSA actors and merge their datasets into a single FDA + NHTSA + CPSC recall aggregator feed on a shared schedule.
Data source & notes
- Source: the official U.S. Consumer Product Safety Commission (CPSC) SaferProducts.gov recalls API - public U.S. government data, free to access and use.
- No API key is required.
- Coverage is limited to what CPSC publishes: consumer products (toys, appliances, electronics, furniture, nursery, sporting goods, etc.). Vehicle recalls are NHTSA's domain and food/drug/cosmetic recalls are FDA's - use the companion actors for those.
- The actor reflects CPSC's own data; it does not add, infer, or correct fields beyond flattening the API response.
- Actor:
maydit/us-product-recalls-scraper(idDqX2SMVuwVL8nPeYB).