Medical Taxonomy API
Pricing
Pay per usage
Medical Taxonomy API
Lookup NUCC provider taxonomy codes, search healthcare specialties, and resolve public NPPES provider taxonomy chains by NPI. Writes one normalized taxonomy result per input to the Apify dataset.
Pricing
Pay per usage
Rating
0.0
(0)
Developer
jts
Actor stats
0
Bookmarked
2
Total users
1
Monthly active users
20 hours ago
Last modified
Categories
Share
What this Actor does
Lookup NUCC provider taxonomy codes, search healthcare specialties, and resolve public NPPES provider taxonomy chains by NPI. Writes one normalized taxonomy result per input to the Apify dataset.
Input example
Input fields
Provide NUCC taxonomy codes, public NPI numbers, or specialty search terms. The Actor calls the Medical Taxonomy API and writes one response per input.
codes(array, user input): NUCC provider taxonomy codes to resolve. Use this when you already have the 10-character NUCC code and need normalized grouping, classification, specialization, parent/child relationships, and CMS specialty crosswalk data.npis(array, user input): Optional 10-digit public NPI numbers to resolve through the public NPPES registry. The Actor returns the provider taxonomy chain and marks which taxonomy is primary when NPPES publishes that signal.queries(array, user input): Optional specialty search terms. Use plain healthcare specialty words such as cardiology, dermatology, radiology, emergency medicine, or nurse practitioner when you do not know the exact NUCC code.apiBaseUrl(string, optional override): Override of the upstream API base URL. Defaults to runtime.baseUrl from service.json.
Output dataset
Each dataset item is one normalized response from the Medical Taxonomy API.
input: Original code, NPI, or query.result: Full API response envelope.
Developer notes
Set MEDICAL_TAXONOMY_API_KEY as an Apify secret environment variable. The Actor forwards it as X-API-Key to the upstream API.
Use apiBaseUrl only for local or staging QA. Production runs default to the deployed API base URL from service.json.
For advanced testing, a requests array can call explicit API paths; normal users should use the service-specific fields above.
Run locally
Deploy
