openFDA enforcement export

The openFDA bulk archive behind the FDA recall page: a food enforcement export of 29,310 records reaching back to 2004-era event IDs.

Every openFDA response carries a licence URL intended to govern bulk redistribution.

In this catalog it appears concretely: - FDA Recalls listings (terms of use) — "the underlying openFDA food enforcement export holds 29,310 records". - Same (catalog record) — "openFDA holds the multi-decade archive back to 2004-era event IDs"; "returns a licence URL (open.fda.gov/license) with every response".

Same is the second reference point worth knowing: "openFDA holds the multi-decade archive back to 2004-era event IDs"; "returns a licence URL (open.fda.gov/license) with every response". Reading the two together shows how much variation sits underneath one shared label.

A label on a listing is not a deliverable. Teams that license on the strength of a product-name match routinely find the shipped files cover a narrower slice than they assumed, and backfilling history afterwards costs more than the license ever did.

The failure mode is concrete: a source can carry the openFDA enforcement export label while differing from what you need on exactly the dimension that matters — the underlying openFDA food enforcement export holds 29,310 records. Comparing two sources on that line usually settles the choice faster than any feature matrix.

You rarely have to take a vendor's word for it. 82.4% of the 1,744 datasets Datadory catalogs are free to access, and FDA Recalls listings lets you inspect the real artifact before any budget is committed.

Treat every claim of this attribute as testable:

1. Read FDA Recalls listings's record on terms of use — "the underlying openFDA food enforcement export holds 29,310 records" — then confirm the delivered artifact matches before you license anything. 2. Read Same's record on catalog record — "openFDA holds the multi-decade archive back to 2004-era event IDs"; "returns a licence URL (open.fda.gov/license) with every response" — then confirm the delivered artifact matches before you license anything. 3. Pin down update cadence in writing. Across this catalog, 22.6% of 1,744 datasets refresh daily and 64 still arrive only through a manual request form, so ask exactly how fresh each release is. 4.

Adjacent concepts worth reading next: - bot detection blocking - food recall notice