Local-first recall matching
Listing and catalog input is normalized, searched against connected recall records, scored, and returned with matched fields so your team can see why a result appeared.
Recall screening API
Screen resale listings and product catalogs for recall risk.
CatalogRecall API helps resale marketplaces, baby gear sellers, and inventory tools check product names, brands, UPCs, model numbers, and lot codes against official recall sources before items go live.
Match
POST /v1/recalls/match
Search
GET /v1/recalls/search
Freshness
GET /v1/recalls/sources
Usage
GET /v1/usage
API capabilities
Recall screening your team can review and act on.
Live openFDA fallback
When local data finds no match, optional live checks can double-check FDA food enforcement.
Lot verification states
Strong product matches with missing lot or date information are routed to manual verification.
Freshness indicators
Source summaries show when each dataset was last checked and whether it is fresh.
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
Publish, 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."
}Coverage
Know what the API can check before you trust the result.
The coverage view shows which official datasets are connected today, what product categories each source covers, and where manual verification still matters.
CPSC recall notices
Consumer products, baby gear, toys, electronics, appliances, household items, and sports gear.
openFDA food enforcement
FDA-regulated food enforcement reports prepared for product and lot-code matching.
Live openFDA fallback
Optional backup check before returning a local no-match result for food-related inputs.
USDA FSIS
Meat, poultry, and egg recalls for broader food coverage.
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 100 to 500 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.
Developer toolkit
Start checking products in three steps.
01
Create an API key and store it server-side.
02
Send product fields to POST /v1/recalls/match.
03
Route possible_match, likely_match, and needs_lot_verification to review.
curl "$CATALOGRECALL_API_URL/v1/recalls/match" \
-H "Authorization: Bearer $CATALOGRECALL_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"productName": "Graco stroller",
"brand": "Graco",
"category": "baby gear",
"liveCheck": true
}'Pilot pricing
Start small, scale when checks become routine.
Free
$0
500 API calls per month for testing recall checks and validating the 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.
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.
Bug report
Found something off? Send it straight to the repo.
Reports create a GitHub issue for CatalogRecall API. Include the page, what happened, and what you expected.
- Destination
- GitHub issue queue
- Best detail
- URL, steps, expected result
Pilot ready