database api · rest + mcp · source-linked

Drug Product Data API

Search US drug products and related identifiers through one API.

Built for Health-data engineers, pharmacy platforms, benefits-data teams, and healthcare AI builders joining US drug-product identifiers for internal reference workflows.

Request the sample Read the API reference API reference

GET/v1/drugs

cURL

authenticated production request

curl --get \
  "https://api.rxatlas.dev/v1/drugs" \
  --data-urlencode "ndc=75834-258" \
  --data-urlencode "limit=5" \
  --header "Authorization: Bearer $API_KEY"

135,544

records

sources

150

email sample

Full release 2026-09-16 · dated 2026-09-16. The sample bundle is delivered by email; production API calls require paid access.

record and matching

Understand what one result represents

FDA and NLM sources expose product NDCs, package NDCs, SPLs, RxCUIs, application numbers, and optional enrichments at different grains, so a production integration must preserve their relationships without inventing one universal drug identifier.

Product NDC and package NDC are different grains

One served row represents one openFDA product NDC. Segmented product NDCs and normalized package NDC11 values can resolve to that product, while package codes, SPL set IDs, RxCUIs, and application numbers remain source-linked associations rather than unsafe merge keys.

Evaluate the NDC response contract

Request the email-delivered evaluation bundle to inspect product and package identifiers, null enrichment, schema, and provenance, then review the API reference for strict filters, pagination, authentication, bulk NDC resolution, coverage output, and REST or MCP integration details.

measured release evidence

Coverage claims carry a date and definition

Evaluate field completeness, source scope, freshness, record grain, and provenance against the dated full release—not against the evaluation bundle alone.

FDA product-NDC rows

135,544

Rows in the current dated release, with one row per openFDA product NDC.

Product NDC coverage

100%

Share of exported FDA product rows carrying the authoritative two-segment product NDC used as the release identity.

SPL link coverage

100%

Share of exported FDA product rows associated with at least one DailyMed SPL set identifier.

Multi-source coverage

82.74%

Share of exported FDA product rows receiving active provenance from more than one contracted public source.

Application-number coverage

72.75%

Share of exported FDA product rows with a served NDA, ANDA, BLA, or source marketing marker.

NADAC price coverage

14.90%

Share of exported FDA product rows with a latest-effective, source-linked NADAC per-unit value.

Freshness policy

Weekly refresh

Maximum age 8 days. Oldest measured source refresh: 2026-09-16.

Weekly releases identify source dates. Product feeds, Drugs@FDA, and REMS use an eight-day bound; PMR/PMC, IID, and CMS SDUD use explicit 100-day bounds.

Coverage methodology Sources and licences Provenance model

limitations

Know the limits before purchase

Coverage values are release-specific; recheck the current coverage and source evidence before relying on optional RxCUI, NADAC, label, shortage, or enforcement enrichment.

The API is reference infrastructure and must not be used as medical, prescribing, coding, reimbursement, or regulatory advice.

Not a clinical drug compendium, prescribing system, interaction checker, or pill-identification service.

Not medical, reimbursement, coding, formulary-placement, or regulatory advice.

RxCUI, NADAC, application-number, label, and enforcement enrichment is not guaranteed for every product.

next step

Evaluate the data before you buy

Download a representative sample by email, review current coverage, and choose the access model that fits your workload.

Get sample by email View pricing