Drug enforcement / recall report

Enforcement reports are event records, not product catalogs. Each one documents that FDA announced a recall action: how severe it is (classification), where it stands (status), which firm recalled the product, why, and the textual distribution pattern describing where affected product went.

openFDA's Drug Enforcement / Recall API exposes the feed two ways:

• JSON API — over the FDA Recall Enterprise System (RES), covering drug enforcement/recall reports from 2004 to present, one record per enforcement report/event.
• Bulk export — a single file of about 3.8 MB holding 17,876 records, small enough to load whole into a notebook.

The dataset is tagged fda, drug-recalls, enforcement-reports and consumer-safety on the safety side, and pharmacy-operations and supply-chain-risk on the operations side — the same events serve both audiences.

FDA itself warns the feed should not be used for tracking recall lifecycle status. Treat every record as a snapshot of an announcement, not a live case management system; a recall still listed as ongoing may have closed weeks earlier.

Volume is the second planning input. With 17,876 reports accumulated since 2004 — roughly 3.8 MB compressed — this is a low-volume, high-severity feed. Teams that need continuous monitoring should schedule refreshes around API rate limits instead of assuming a firehose.

1. Confirm one-record-per-event semantics. openFDA documents granularity as 'One record per enforcement report/event' — denormalized feeds that duplicate an event per product line inflate recall counts.

1. Check the start date. Coverage runs from 2004 to present; older histories need other sources.

1. Prefer the bulk export for baselines. 17,876 records in a ~3.8 MB single-file download makes a local baseline trivially cheap, with the API used for incremental updates.

Where to see it in context: drug-retail data.

Access and licensing concepts that sit next to enforcement-report feeds: - api-rate-limit — Publisher-imposed caps on request volume, backed by contractual clauses such as openFDA's Right to Limit. - commercial delivery terms-public-domain — A Creative Commons dedication waiving copyright so data can be reused without attribution; in this slice it attaches to two Kaggle uploads and to US Census API dataset metadata, though the excavator image set's description still asserts DataCluster Labs ownership over larger portions.