Daily Edition Sources +4

API Discovery: Check a Barcode Against France's Recall List

France's official RappelConso data can turn a scanned GTIN into a product-recall match—if the agent checks the lot, date, and government notice instead of treating a name hit as proof.

Diagram Punk poster showing a barcode flowing through the official RappelConso API to a lot-and-date check and government recall notice, with a warning that no match does not mean safe.
Diagram Punka barcode is a lead, not a verdict.
repos source trail evidence
4 source signals 0 repos 4 source signals
Evidence: 4 source signals / July 11, 2026 / Daily Edition
Open Edition Evidence below

API discovery: A live query to the French government's RappelConso Explore API for barcode 3701002416628 returned one July 10 recall: a 90-gram aperitif product, with its lot, durability date, stated listeria risk, instructions not to consume it, and a link to the official recall sheet.

Try it on a receipt

Give an agent the barcodes from a household inventory or shopping receipt. It can query each identifier, flag an exact recall candidate, and return the brand, model, affected lot or date, official action, and government notice. The useful output has three states: exact record to verify, possible name match needing identifiers, or no match found in this query.

Copy-paste agent instruction

Use only the official RappelConso dataset at https://data.economie.gouv.fr/api/explore/v2.1/catalog/datasets/rappelconso-v2-gtin-espaces/records. For each barcode I give you, query where=search(*,"BARCODE") and request the product, identification, risk, consumer-action, publication-date, and official-notice fields. Require an exact GTIN match, then compare the lot, model, and date before flagging it. Link the official recall sheet. If nothing matches, say "no match found in this query"—never "safe." Do not infer a match from the brand alone.

Test caveat

The sample query worked without authentication on July 11, but this is a screening workflow, not a safety oracle. Records, rate policy, and availability can change; product identity may depend on a lot or date that a barcode does not encode. A miss is not proof of safety, and every hit should end at the current official notice.

Evidence Trail

Receipts below the story

The article above is the public narrative. This section keeps the source trail and limits on the same page.

Edition
DateJuly 11, 2026
LaneDaily Edition
Confidence78%
Sources4
Repossource trail

Primary Evidence

Evidence Limits

  • An API match is a lead to verify against the exact product, lot, date, and official notice; it is not a diagnosis or an automatic safety decision.
  • An empty query result means only that the request found no matching record. It must never be presented as proof that a product is safe.
  • The endpoint answered without a key in the July 11 test, but access, rate limits, availability, update latency, and record completeness can change.
Letters & Corrections

Send a note to the desk

Corrections, missing context, or a follow-up lead.