Datadory notebook
Drug Name Autocomplete Rxterms Api Data: Dataset Structure and Field Coverage
Datadory delivers drug name autocomplete rxterms api data covering comprehensive field definitions, entity mappings, and historical time series — structured for direct analytics and delivered on demand.
1,744 datasets. Pick your catch.
How do you wire RxTerms autocomplete into a pharmacy app?
Integration is deliberately thin - the whole point of a key-free autocomplete API is that nothing stands between a user's typing and a ranked list of names. Four steps cover a working build:
Three operating rules come straight from NLM's terms. Stay under the advised soft limit of 25 requests per second; get in touch with NLM before passing 50,000 calls in a day; and never place PHI or PII inside a request string. Because the service is provided "AS IS" with no availability guarantee, cache responses client-side and debounce input so a fast typist does not burn through the request budget on partial words.
What fields come back with each matched drug name?
RxTerms is modeled for prescribing, not merchandising. Granularity is one row per drug name and route, and the attributes that ride along with each match are the clinically load-bearing ones: strength, dose form and route of administration. A prescriber typing the first few letters of "amoxicillin" gets name-plus-form candidates they can act on immediately instead of a flat list of strings to disambiguate by hand.
When a build needs to go from finished name to substance, the ingredient table carries 2,342 rows in the same service under the same contract. And because the neighboring tables share one host, the identical autocomplete pattern extends to diagnosis codes (ICD-10-CM FY2026, about 75,000 codes), lab orders (about 109,000 LOINC rows) and provider identity (the 9.37 million-record NPI registry, served from the CMS file dated 2026-08-10). One JSON shape covers four distinct lookup problems, which is why teams that adopt it for drug names rarely stop at drug names.
Which datasets pair with RxTerms in a retail build?
An autocomplete box is the front door; the rooms behind it are a product master, a labeling store, an approval record and a provider registry. All four sit inside the same free slice, and every one of them is served by an official API rather than a crawl, which keeps every join in the stack programmatic and reproducible. Five pairings cover most retail builds, from resolving exactly what was ordered to proving who was allowed to prescribe it.
Pick up where this leaves off
Every one of these ships with sample rows before you commit to anything.
NLM Clinical Table Search Service
DISPLAY_NAME · DISPLAY_NAME_SYNONYM · STRENGTHS_AND_FORMS …+4 more
GoodRx Drug Prices & Pharmacy Finder
Walgreens.com Pharmacy & Drug Catalog
Want rows instead of a pitch? Name the datasets.
API, files, or your warehouse. Daily, weekly, or hourly.
Get a sampleQuestions worth asking
Is there a free drug name autocomplete API?
Yes. The U.S. NLM Clinical Table Search Service offers key-free autocomplete JSON over about 25 clinical tables, including RxTerms with roughly 9,300 drug names carrying strengths, forms and routes. No registration is required, and the advised soft limit is 25 requests per second.
Do I need an integration key for RxTerms autocomplete lookups?
No. NLM serves the Clinical Table Search Service to the general public free of charge with no registration step. Stay under the advised 25 requests per second, contact NLM above 50,000 calls per day, and keep PHI or PII out of your requests.
How many drug names does RxTerms cover?
Roughly 9,300 names, modeled as one row per drug name and route with strength and dose form attached. The same service adds 2,342 ingredient rows, about 75,000 ICD-10-CM codes and the 9.37 million-record NPI registry for adjacent lookups.