FDA Drugs@FDA Approvals & Product Search Scraper API

Search the official, no-key openFDA Drugs@FDA endpoint and receive one normalized dataset item per FDA application. Each found row includes nested products, active ingredients, strengths, dosage forms, routes, source-reported marketing statuses, therapeutic-equivalence codes when present, submissions/actions, dates, and FDA document links.

Useful for regulatory research, drug-product catalogs, sponsor/application monitoring, and source-backed data pipelines.

Deterministic first run

Empty input searches exact brand Ozempic and returns exactly one application row with nested product and submission evidence. The bounded first run costs at most $0.0021: $0.0001 actor start + $0.002 for one dataset item.

{
  "brandName": "Ozempic",
  "maxResults": 1,
  "maxScan": 1
}

Search examples

Application and product:

{
  "applicationNumber": "NDA213051",
  "productNumber": "001",
  "maxResults": 10,
  "maxScan": 100
}

Submission/action research:

{
  "sponsorName": "NOVO",
  "submissionType": "SUPPL",
  "submissionStatus": "AP",
  "submissionDateFrom": "20240101",
  "submissionDateTo": "20261231",
  "sort": "submissions.submission_status_date:desc",
  "maxResults": 25,
  "maxScan": 100
}

Filters are combined with AND. Supported fields include brand/generic/sponsor, application and product number, dosage form, route, source marketing status, submission type/status/action date, and therapeutic-equivalence code when present. skip is bounded to 25,000, maxScan to 1,000 source candidates, and maxResults to 500 total paid application rows. The actor honors an Apify maximum-total-charge limit before source pagination and writes output in bounded batches.

Output

A FOUND row includes:

• application number and sponsor
• stable summary arrays for brands, generic names, products, strengths, dosage forms, routes, and marketing statuses
• nested products and active ingredients
• nested submissions/actions and FDA document links
• harmonized openFDA NDC, RxCUI, SPL, UNII, substance, manufacturer, and pharmacologic-class identifiers when available
• exact official API query URL, source update date, retrieval timestamp, source total/scan bounds, scope, and evidence notice

Arrays remain [] when the source omits a field. Searches that return no qualifying application produce an explicit NO_MATCH item. Invalid input produces INVALID_INPUT; an official-source failure after bounded retries produces SOURCE_UNAVAILABLE. These outcome rows are evidence about the bounded attempt—not proof that a drug/application is absent.

Reliability

The client uses bounded pagination, response-size limits, request timeouts, and four attempts for transport errors, HTTP 408/429/5xx responses, response-body failures, and malformed JSON. Retry-After is honored where practical. openFDA may limit or restrict API access, and FDA warns that openFDA results should be treated as unvalidated.

Evidence boundaries

Drugs@FDA records describe FDA applications, products, and regulatory submissions/actions. They do not establish:

• current market availability or whether a product is actively sold
• current drug shortages
• recalls or recall resolution
• current prescribing guidance or the complete current label
• comparative effectiveness
• safety or suitability for a particular patient
• complete Orange Book patent or exclusivity information
• medical advice

A source-reported product marketing status is an administrative field, not proof of present availability. A submission status/action date is not patient guidance. Review the linked FDA materials and the appropriate current FDA recall, shortage, labeling, Orange Book, and safety resources. Do not rely on this output to make medical-care decisions.

Pricing

Pay per event: $0.0001 per start + $0.002 per dataset item. maxResults is a total response cap, not a per-page or per-product cap; nested products and submissions remain within the single paid application row.