CPSC recalls
Useful for baby gear, toys, furniture, appliances, electronics, and other consumer product categories.
Recall screening API
Screen resale listings and product catalogs for recall risk.
Check product names, brands, UPCs, model numbers, and lot codes against connected recall sources before resale items go live.
Match
POST /v1/recalls/match
Search
GET /v1/recalls/search
Freshness
GET /v1/recalls/sources
Usage
GET /v1/usage
Source coverage
Show what was checked and what still needs verification.
CatalogRecall API exposes source state so a review team can see which connected datasets produced candidates, which live fallback ran, and when official verification is still required.
openFDA food enforcement
Food recall and enforcement records with product descriptions, firms, classifications, lot details, and dates.
openFDA fallback
Optional live food lookup when local data finds no match, reported
in sourceChecks.
NHTSA and scan jobs
Vehicle equipment sources, saved scans, webhooks, and full upload/download workflows belong on the roadmap until shipped.
API capabilities
Workflow-ready matching for messy product rows.
CatalogRecall API is the normalization and matching layer between imperfect catalog data and connected recall sources. It gives your system enough evidence to continue normal review, route a row to manual review, or ask for lot and date details.
Normalize the row before matching
Product names, brands, categories, UPCs, models, SKUs, lot codes, and manufacture dates are cleaned into a matchable shape before the API searches connected recall records.
Explain why a candidate appeared
Responses include confidence scores, matched fields, score breakdowns, compact recall summaries, source links, and detail paths for deeper verification.
Route uncertainty to review
Statuses such as possible_match,
likely_match, and
needs_lot_verification map cleanly to marketplace
review queues.
Support API and CSV validation
Start with POST /v1/recalls/match for one listing or
request a free CSV scan when you need a quick pilot before
integration.
Workflow
A clearer review loop for messy resale data.
Send product fields
Product name, brand, category, UPC, model, SKU, lot code, or manufacture date.
Score candidates
Normalize input, retrieve candidates, match fields, and calculate confidence.
Decide next step
Continue normal review, route to manual review, verify lot details, or check the official notice before action.
Playground
Test a recall check with your API key.
Use your deployed API URL and key to run a live match. Without a key, the playground shows a sample response so you can still see the integration shape.
Response
{
"status": "needs_lot_verification",
"topConfidence": 0.82,
"sourceChecks": [
{
"source": "catalogrecall_database",
"status": "checked"
},
{
"source": "openFDA_food_live",
"status": "checked"
}
],
"warning": "Verify against the official recall notice before taking action."
}Use cases
Built for teams screening products before resale.
Pre-listing marketplace review
Flag possible recalled secondhand listings before publication, especially baby gear, toys, and appliances.
CSV inventory scans
Send up to 100 product rows and get a recall-risk CSV with confidence scores and source links.
Inventory software add-on
Add recall screening to consignment, daycare, or catalog tools without building recall ingestion yourself.
Field guides
Recall screening examples for the first wedge.
Start with the workflows where messy product rows, manual review, and source verification matter most.
Used baby gear screening
Strollers, cribs, swings, high chairs, toys, and model fields.
Consignment workflow
How resale teams route possible matches before listings continue.
CSV product scanner
What to include in an export and how to read the returned CSV.
Why no_match is cautious
The exact language to show in internal review tools.
Pilot pricing
Start small, scale when checks become routine.
Free CSV scan
$0
Up to 100 rows for validating fit before your team writes an integration.
Request scanFree API
$0
500 API calls per month for testing recall checks and response shape.
Starter
$19
2,500 API calls per month for testing a real integration with light recall-check volume.
Developer
$79
15,000 API calls per month for pilot workflows, review queues, and recurring checks.
CSV Pilot
$99+
Assisted recurring scans when exports are ready but an API integration is not.
Enterprise
Custom
Custom API-call volume, batch scanning, catalog monitoring, webhook alerts, and contract terms.
CatalogRecall API provides automated matching against connected recall
data sources. A
no_match result does not guarantee that a product is safe
or not recalled. Teams should verify possible matches against official
source notices before taking action.
Contact
Help, setup questions, and bug reports.
Send email for account help, checkout questions, integration support, or anything that looks broken. Include the page, what happened, and what you expected.
- Destination
- hello@catalogrecallapi.com
- Best details
- URL, API route, steps, expected result
FAQ
What should I include in a useful bug report?
Send the page URL, API route, timestamp, steps to reproduce, actual response, and expected result. For API issues, include the HTTP status and error code, never the raw API key.
Can I send a CSV instead of integrating first?
Yes. Use the free CSV scan page for up to 100 rows. Include product name plus any brand, model, UPC, lot code, category, or manufacture-date fields you already have.
What does a scan result mean?
Results are automated recall matches against connected sources.
A no_match result does not mean an item is safe;
possible matches should be checked against official notices.
Where do checkout and API-key questions go?
Email the support inbox with your plan, checkout email, route used, and response code. Raw API keys are shown once and are not sent by email.
Support inbox
hello@catalogrecallapi.com
For bugs, add "Bug report" to the subject and include steps to reproduce. For help, include your plan, API route, and the response code or error message.
Pilot ready