Recall Enforcement: searching FDA drug data

The drug/enforcement.json endpoint holds drug product recall enforcement reports. We break down one working example and point out the parameters that matter.

January 9, 2026 · 5 min read · drug/enforcement.json

What this endpoint does

This article covers drug/enforcement.json, the openFDA route for Recall Enforcement. Drug product recall enforcement reports. We are not the FDA — we just help you query their public API.

Who uses it

Pharmacy apps, academic studies, and newsrooms use drug endpoints to cross-check labels, shortages, and safety filings. Expect Latin trade names, misspellings, and duplicate brand entries — normalization is on you.

Example request

Paste this into a browser or our Explorer (swap the search term as needed):

GET https://api.fda.gov/drug/enforcement.json?search=classification:Class+I&limit=5

You should see JSON with meta.results.total telling you how many matches exist.

Searching the data

Start with search=classification:Class+I in our Explorer or your own HTTP client. Each endpoint documents its own field list on open.fda.gov. Common knobs: limit (how many rows), skip (offset for paging), sort (field:asc or field:desc), and count (aggregate unique values).

Tips that save time

If a query times out, tighten your search or lower limit. The public API is shared infrastructure.

limit — usually capped at 1,000 per call
skip — walk through large result sets
count=some_field.exact — quick frequency tables

Before you rely on this data

openFDA Explorer is an independent website. We are not affiliated with, endorsed by, or operated by the U.S. Food and Drug Administration (FDA).

FDA public data is useful for research and general interest. It is not medical advice. Talk to a qualified healthcare professional about your health. openFDA data may be incomplete or reported voluntarily — treat it as a starting point, not a verdict.