CPSC Product Recalls Scraper

Find official U.S. Consumer Product Safety Commission recalls for catalog review, marketplace product-safety monitoring and supplier research. Search by product keyword and recall date, then export complete recall records as JSON or CSV.

Try One Recall

Open the one-recall toy Task. One complete result costs $0.003 in result-event charges. A search may return no matches; a successful run is not a promise that a matching recall exists.

{
  "productNames": ["toy"],
  "startDate": "2026-01-01",
  "endDate": "",
  "maxResults": 1
}

Use an empty endDate for today's UTC date. productNames must be an array of nonblank strings; an intentional empty array removes the product filter. Duplicate keywords are searched once. maxResults must be an integer from 1 through 1000. It limits returned records, not the size of an upstream response or CSV download. The Actor rejects malformed supplied filters or limits instead of silently performing a different search.

The linked one-result Task and the Actor's saved example are separate inputs. Check the prefilled end date when running the Actor directly; clear it when you want the date range to extend through today.

Output And Missing Values

Each paid row has a recall number, recall date, title, description, product names, hazards and remedies. Duplicate recall numbers within a run are saved once.

Field	Meaning
recallNumber	Official recall number and within-run deduplication key
recallId	API identifier; the recall number when using CSV fallback
recallDate	Source recall date; CSV dates use midnight without an inferred timezone
title, description	Official recall heading and description
products, hazards, remedies	Lists of source-provided descriptions
manufacturers, retailers, distributors	Source-provided names; empty lists when unavailable
consumerContact, url	API values when supplied; null for CSV fallback
query	Product keyword for the first matching search; null for an unfiltered search
sourceType, scrapedAt, raw	Record type, UTC extraction time and original source row

CSV list fields can contain a combined source string rather than individually separated organizations. The Actor does not invent missing URLs or contact data. RUN_SUMMARY.sourceUsed distinguishes the API from the weekly CSV fallback.

Billing

The price is $0.003 per complete saved recall, or $3 per 1,000 results. The same recall returned on a later run is charged again; deduplication is within a run, not across schedules. There is no free first run or free repeated baseline. Check the current pricing and run-cost details in Apify Console before scaling.

Diagnostics, retries and empty searches do not create result-event charges. Matching incomplete records examined before the result limit fail validation before the batch is written, so they and any staged prefix are not billed. In CSV fallback, a keyword-matching record with an invalid date also fails the search: its date eligibility cannot be established. Infrastructure may still be consumed by failed or empty runs; zero result events is not a guarantee of zero run cost.

Sources, Limits And Troubleshooting

The Actor tries the official CPSC Recalls API first. On a primary fetch failure, it discards staged primary results and uses the official weekly recall CSV. The CSV is a periodically published snapshot, not a real-time source; it may lag the API. CSV keyword matching checks the heading, product, description and hazard text, which can differ from the API's product-name matching. Neither path promises all worldwide recalls or exhaustive product-safety coverage.

Each source has at most three fetch attempts. The CSV download is capped at 30 MB. Result limits are not a maximum-total-cost control. Use Apify's runtime and charge controls, and inspect the run summary before widening a search.

• No matching rows: inspect the date range and product keyword. A valid empty search has RUN_SUMMARY.status=SUCCEEDED and zero saved rows.
• Both sources unavailable: the run can finish with RUN_SUMMARY.status=SOURCE_UNAVAILABLE, completed=false and zero rows. This is not a recovered source or a complete search, even if the platform run says succeeded. Retry later after checking source availability.
• Invalid input or incomplete source data: the run fails with a free summary containing errorType; correct the input or report the source issue. Do not treat a failed run as evidence that no recalls exist.

Use Cases And Responsible Use

Build a human-reviewed recall queue for an ecommerce catalog, monitor products sold by suppliers, or compare recall descriptions with internal product records. Recall matching requires careful product/model review; a keyword match alone does not establish that a particular seller's item is recalled. Verify consequential safety, insurance, legal or takedown decisions against official CPSC information. This Actor organizes public source records and does not provide legal advice or certify that a product is safe.