US Product Recall Compliance Monitor
Pricing
$30.00 / 1,000 matched recall alerts
US Product Recall Compliance Monitor
Match CPSC product recalls and FDA food enforcement records against brands and keywords using official public APIs.
Match CPSC product recalls and FDA food enforcement records against brands and keywords using official public APIs.
What this Actor does
Monitor official U.S. consumer-product and food recall feeds for brands, hazards, and product terms. The Actor normalizes CPSC and FDA records, explains each match, assigns a non-legal severity label, and preserves the official source.
Typical use cases
- Marketplace seller compliance monitoring
- Importer and distributor watchlists
- Brand and product safety alerts
- Insurance and risk-research feeds
Quick start
{"sinceDate": "2026-07-01","untilDate": "2026-07-13","sources": ["cpsc", "fda"],"brands": ["Acme"],"keywords": ["battery", "allergen"],"onlyMatches": true,"maxResults": 50}
Input
| Field | Required | Description |
|---|---|---|
sinceDate | Yes | ISO start date. |
untilDate | Yes | ISO end date; maximum window 31 days. |
sources | Yes | cpsc, fda, or both. |
brands | No | Up to 20 brand terms. |
keywords | No | Up to 20 product or hazard terms. |
onlyMatches | No | Omit unmatched official records. |
maxResults | No | Combined hard cap, maximum 100. |
Pricing draft
Pay per event: matched-recall — $0.030 for one official record returned after filtering.
Sources and compliance
The Actor uses the official CPSC Recall Retrieval Web Service and openFDA Food Enforcement API. Results can be delayed, incomplete, corrected, or withdrawn and are informational only — not legal, medical, or regulatory advice. No consumer contact fields are emitted.
Reliability, support, and privacy
The Actor enforces a 31-day window, a combined output cap of 100, a 10 MB streamed CPSC response cap, a 5 MB streamed FDA response cap, 45-second source timeouts, and the Apify charge allowance. CPSC does not expose a result-limit parameter, so its date-bounded response is rejected before JSON parsing if the byte cap is exceeded. Use the Apify support channel with a run ID and redacted input. Never include credentials. Users control Apify storage retention.