openFDA exposes drug, device, biologic, food, and tobacco data as JSON over a REST API. Drugs@FDA also publishes the orange book as a flat-file download for exclusivity and patent linkages. The 510(k) and PMA device databases publish their own bulk files. Most sites combine openFDA for the headline metadata with Drugs@FDA for exclusivity and label files.

openFDA permits generous read access with an API key. Cache responses per the configured duration so the API is hit once per refresh rather than per page view. For very large pulls, the openFDA team also publishes daily downloadable JSON archives that bypass the API entirely.

Supplements are tied to the original application number. Pull the supplements list from openFDA and render it as a timeline list mapping on each approval page. Labeling updates are linked from the supplements; render the latest labeling URL as the primary label link with prior versions in a history block.

Yes, and you should. openFDA flags marketing-status and withdrawal-reason fields. Drive a status badge on the page from those fields, optionally noindex withdrawn products via meta mapping if you do not want them ranking as current options, and keep the page reachable for historical research.

Yes. Schema.org Drug is the right type for pharmaceutical approvals with proprietaryName, nonProprietaryName, manufacturer, and activeIngredient fields. MedicalDevice fits device clearances. Render JSON-LD via tag mapping on the base page; the application type drives the @type selection.

510(k) records have a slightly different schema (K-number instead of NDA, predicate device, regulatory product code). Run a parallel page group with its own base template and URL prefix (/fda/devices/{slug}/), or merge with drug pages via an application-type column that drives the template variant.

Render only the agency-approved indication text via tag mapping from the openFDA indications field. Do not paraphrase or summarize claims; quote the label. The page should read as a factual record of the approval, not as medical advice, and the footer should include a disclaimer pointing users to clinician guidance for treatment decisions.

openFDA typically reflects new approvals within days of FDA action. Once your ingest job picks up the new row, SleekRank generates the URL on the next cache refresh. Most teams run a daily delta pull plus a manual flush on big approval days so high-traffic approvals go live within hours of the FDA announcement.