Use cases / Grocery and food apps
RecallDB for grocery and food apps
The problem
Shoppers want to know whether something in their cart or pantry is recalled. FDA and USDA publish notices in different formats, and barcodes are buried in the text.
RecallDB extracts UPC and EAN codes from the notices and returns the lot codes and best-by dates exactly as written. It never decides whether a package matches; the shopper compares the codes.
Endpoints that help
Example
curl https://recalldb.app/v1/barcode/036000291452 \
-H "Authorization: Bearer $RECALLDB_KEY"Free and Pro
Free (beta): 1,000 requests a month; /v1/new up to 1 hour old.
Pro (planned): Free (beta) is for non-commercial use: build and test on it. A product or service you sell needs Pro, which is planned (commercial use, about 50,000 requests a day, instant webhooks, 100 VINs per batch call); join the waitlist and we write once when it opens. Real-time /v1/new is planned for Pro.
Every answer names the agency and links its official notice. RecallDB reports what notices say; it never tells anyone that a car or product is free of recalls.