shipapis
StarSubmit an APISubmit API

NPPES vs openFDA API

Same instrument, two spec sheets — measured, not claimed.

APINPPESNEW—openFDA APINEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSnono
HTTPSyesyes
Card requirednono
Commercial useyesunclear
Data licenseU.S. Government (public NPI data)Unverified
Free tierFree — no key requiredFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

NPPES vs openFDA API: common questions

Which is more reliable, NPPES or openFDA API?

On our scheduled checks, openFDA API leads on measured uptime — NPPES at —% versus openFDA API at —% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Do NPPES and openFDA API need an API key?

Neither needs a paid key — NPPES is callable with no signup, and openFDA API is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call NPPES and openFDA API from the browser?

Neither sends browser-friendly CORS headers reliably, so call NPPES and openFDA API from a server or proxy rather than client-side. The CORS and HTTPS rows above show exactly what we detected for each.

Are NPPES and openFDA API free for commercial use?

NPPES allows commercial use on its free tier, and openFDA API has unclear commercial terms. We track service terms and the data license as separate fields — see the Commercial use and Data license rows above, and confirm both before shipping either in a paid product.