Find recall notice candidates by UPC or GTIN
Send a GTIN as a string to preserve leading zeroes. The API validates GTIN-8, UPC-A, EAN-13 or GTIN-14 check digits and normalizes to 14 digits. An invalid check digit is rejected rather than guessed.
POST /v1/recalls/check
Authorization: Bearer YOUR_KEY
Content-Type: application/json
{"gtin":"810002862779"}The bounded sample includes a notice whose description explicitly labels UPC 810002862779 even though its structured UPC array is empty. Our deterministic extraction preserves the exact source span and checksum validation. Inspect that record and its evidence. This one case demonstrates field enrichment, not a broad accuracy advantage over the official API or competitors.
Many notices lack usable identifiers. Model mentions in prose stay text candidates, and matching a product identifier does not resolve lot, serial or remedy restrictions. No-match results are named no_candidates_in_scope, never safe.
Create a free key · REST/MCP setup · Current scope and freshness.