NPI Registry Scraper
Pricing
from $0.30 / 1,000 provider records
NPI Registry Scraper
Search and export public CMS NPI Registry healthcare provider records by NPI, specialty, name, organization, and location.
Search the public CMS NPI Registry by NPI number, specialty, provider name, organization or location. Export provider identities, taxonomies, practice and mailing addresses, phone numbers and registry dates to CSV, JSON, Excel or the Apify API.
Use this NPI Registry scraper for provider-directory enrichment, healthcare prospect research and roster reconciliation. It returns public registry records, not patient data or independent credential verification. Each run saves at most 1,200 records. It is not a complete national registry download.
Quick start
- Open the input form and clear the sample NPI numbers if you only want a specialty or location search.
- Enter a small search, such as the example below, then click Start.
- Open the dataset and export the records or retrieve them through the API.
{"taxonomyDescription": "Cardiology","city": "Seattle","state": "WA","maxResults": 20,"includeRaw": false}
Prefer a video guide? This short Apify walkthrough shows you how to set up and run an Actor. It uses a different Actor, but the setup steps are the same.
What you get
One public registry provider row with its NPI, individual or organization identity, available taxonomy, practice and mailing contact fields, registry dates and source link. Optional raw source records can accompany the normalized fields. Registry status and contact entries do not establish licensure, eligibility or guaranteed outreach addresses.
Who is it for?
- Provider-directory teams enriching known NPIs with public registry context.
- Healthcare-market researchers reviewing focused specialty and location samples.
- Roster administrators reconciling their own provider identifiers and registry names.
- Data developers importing normalized public records and optional raw source detail.
How you can use the data
- Review a Seattle cardiology sample. Use the existing specialty, city and state with a small explicit cap and raw records off. Clear sample NPI prefills first, then retain NPI, taxonomy, source links and available practice fields rather than claiming complete local coverage.
- Reconcile one known NPI. Use the existing 1679576722 lookup with a one-record cap and raw source enabled. Join the exact NPI to your roster, keeping registry status and dates without treating that record as an independent license or eligibility check.
- Build a focused organization sample. Use the existing clinic/Austin/TX recipe with organization entity type and a small cap. Review registry names and address fields because a location match need not equal the displayed primary practice address.
- Compare your own registry snapshots. Keep NPI, registry lastUpdated and collection time in your destination for later reconciliation. Public phone and endpoint fields can be missing or stale and are not guaranteed marketing email addresses. Any validation, matching decisions or alerts happen in your own workflow.
Input settings
| Setting | API key | Purpose |
|---|---|---|
| NPI numbers | npiNumbers | Exact 10-digit identifiers, looked up before any search. |
| Specialty | taxonomyDescription | Registry taxonomy description, such as Cardiology. |
| Individual name | firstName, lastName | Provider name filters. |
| Organization | organizationName | Clinic, hospital, pharmacy or other organization name. |
| Location | city, state, postalCode, countryCode | Registry location filters. The form supplies US for country. |
| Entity type | enumerationType | Blank for both, NPI-1 for individuals or NPI-2 for organizations. |
| Result limit | maxResults | Default 20. Effective maximum 1200 across lookups and search. |
| Source record | includeRaw | Default true. Adds the complete source record as raw. |
| Connection settings | proxyConfiguration | Optional proxy configuration. Direct by default. See field help. |
No field is globally required. Without NPIs or substantive search criteria, the Actor looks up sample NPI 1679576722. Country alone does not initiate a search. If enumerationType is supplied without a specialty, name, organization, city, state or postal code, search is skipped with an explicit warning, without substituting the sample. Explicit exact NPI lookups still run and are not filtered by enumerationType. State also requires a specialty, name, organization, city or postal code; state alone (even with country or entity type) skips search with a warning, without substituting the sample. Any supplied exact NPIs still run.
When NPIs and search criteria are combined, both are processed, sharing the result limit. Repeated NPIs are saved once. There is no sorting option or guaranteed ranking.
Wildcards in specialty, first/last name, organization, city and postal-code filters require at least two leading characters: use Jo*, not J* or *. The input form and API reject shorter wildcard prefixes before startup. Entry paths bypassing schema validation skip an invalid search with a warning in RUN_SUMMARY, while preserving any supplied exact-NPI lookups. Exact names without wildcards may be shorter.
Customer max-cost and timeout limits are checked before startup and further work. If the allowance cannot fit startup plus one record, the Actor stops successfully with a warning and a RUN_SUMMARY limit reason. Allow at least 61 seconds for a bounded 30-second request and safe shutdown; normal requests usually finish much sooner. Collected rows are retained at a limit stop. Genuine request, storage and billing failures still fail the run, including incomplete exact-lookup batches.
Exact NPI lookup
{"npiNumbers": ["1679576722"],"maxResults": 1,"includeRaw": true}
Organizations in a city
{"organizationName": "clinic","city": "Austin","state": "TX","enumerationType": "NPI-2","maxResults": 20}
These are input recipes, not links to saved or published tasks.
Output data
Illustrative, abbreviated shape only—not a verified provider record. Missing source values can be null. Collections can be empty.
{"npi": "0000000000","entityType": "individual","enumerationType": "NPI-1","firstName": null,"lastName": null,"organizationName": null,"credential": null,"primarySpecialty": null,"specialties": [],"taxonomyCodes": [],"practiceCity": null,"practiceState": null,"practicePhone": null,"status": null,"url": "https://npiregistry.cms.hhs.gov/provider-view/0000000000","scrapedAt": "2026-10-25T00:00:00.000Z"}
More output fields
| Group | Fields |
|---|---|
| Identity | npi, entityType, enumerationType, firstName, middleName, lastName, namePrefix, nameSuffix, organizationName, authorizedOfficialName, credential, gender, status |
| Specialties | primarySpecialty, specialties, taxonomyCodes, taxonomies |
| Practice contact | practiceAddress, practiceCity, practiceState, practiceZip, practiceCountry, practicePhone, practiceFax |
| Mailing contact | mailingAddress, mailingCity, mailingState, mailingZip, mailingCountry, mailingPhone, mailingFax |
| Dates | enumerationDate, certificationDate, lastUpdated, createdEpoch, lastUpdatedEpoch |
| Source detail | addresses, endpoints, identifiers, otherNames, practiceLocations, url, scrapedAt, optional raw |
The source determines field availability. status preserves the registry code rather than translating it into a credentialing decision. Electronic endpoints are registry entries, not a promise of marketing email addresses.
Download your results
Open your run's dataset, choose Export and select JSON, CSV or Excel. JSON keeps nested fields together. CSV and Excel are useful when you want to review the records in a spreadsheet.
See Apify's download and export guide for the available formats and field options.
Pricing
The start event is charged once after initial validation and before retrieval or connection setup. A completed empty search can still incur it, while initial validation failures do not. The result event applies to each provider record saved, and a later run failure does not undo saved records or earlier charges.
Per-record result prices increase on every plan from 27 November 2026 (16:00 UTC), with lower rates on higher subscription plans; the start fee is unchanged. Current prices apply until then.
Use a small explicit record limit. See the live Pricing tab for current rates, the scheduled rates and discounts. Apify platform usage and optional proxy charges may also apply.
Tips for best results
- Clear sample NPIs for search-only input. Exact lookups otherwise run before your search under one cap.
- Use specialty and geography to narrow research. This is not a complete national download or automated market partitioner.
- Keep exact identifiers and source dates. They help reconcile records in your own directory.
- Separate registry status from credential decisions. Confirm current licensing through an appropriate independent process.
- Inspect partial counts and final status. Saved exact-lookup records can remain after another lookup fails.
Limits and caveats
Only public CMS NPI Registry records are returned, without patient data or CMS login. This tool is not affiliated with CMS, does not replace the official registry and does not independently verify licensure or eligibility. Electronic endpoints are registry records rather than guaranteed outreach email addresses or physician reviews.
Exact NPI lookups run before combined search criteria under one effective cap of twelve hundred saved records. Repeated NPIs are saved once. Country alone does not initiate search, and absent substantive criteria falls back to the documented sample NPI unless an invalid search was requested. Enumeration type without a specialty, name, organization, city, state or postal code skips search with a warning while preserving explicit exact NPI lookups. No sorting or guaranteed ranking is provided.
No complete national export or automatic market partitioning is supported. Source availability and restrictive filters can yield fewer records than requested. Fields can be null or empty, and public contacts can be absent or outdated. A matched location need not equal the primary practice address. Registry status remains its source code, not a credentialing interpretation.
A completed no-match response can produce an empty dataset, while source or request failures can fail the run. Inaccessibility alone does not establish privacy or deletion. Useful saved records can survive isolated exact-lookup failures. RUN_SUMMARY records counts, lookup failures, completed and pending lookup counts, pending search work and deadline state when it can be written rather than guaranteeing a summary after every failure. Reaching the Actor's own runtime safety cap with work still pending fails the run; a customer-selected shorter timeout or max-cost stop retains a successful limit warning. Perform matching and repeated-export comparisons in your own destination.
Automation and integrations
Save your settings for next time
Once you have an input that works for you, save it as an Apify task. This keeps your settings together so you can use them again without filling in the form from scratch.
Run on a schedule
Need fresh results regularly? You can schedule the Actor or a saved task to run at a time that suits you.
Each scheduled run collects the data again. If you want to compare results or highlight changes, add that step in your own workflow.
Send results to your other tools
Use n8n, Make or Zapier to connect this scraper to the rest of your workflow. For example, you could pass its results to an AI assistant or add records to a spreadsheet. Follow the Apify integration guides for your chosen tool.
For a custom connection, an Apify webhook can notify your app when a run finishes or fails. Your app can then fetch the results or handle the failure.
API usage
Want to collect this data from your own app or automation? The examples below send input to the scraper and show how to collect its results.
The Node.js and Python examples wait for the run to finish before reading its results. The cURL example starts the run and returns its details. Wait for that run to finish, then use its defaultDatasetId to fetch the results.
For setup instructions, see Apify's JavaScript client guide, Python client guide and Actor runs API reference.
cURL
curl -X POST 'https://api.apify.com/v2/acts/fetch_cat~npi-registry-scraper/runs' \-H "Authorization: Bearer $APIFY_TOKEN" \-H 'Content-Type: application/json' \--data @- <<'JSON'{"taxonomyDescription": "Cardiology","city": "Seattle","state": "WA","maxResults": 20,"includeRaw": false}JSON
Node.js
import { ApifyClient } from 'apify-client';const client = new ApifyClient({ token: process.env.APIFY_TOKEN });const run = await client.actor('fetch_cat/npi-registry-scraper').call({"taxonomyDescription": "Cardiology","city": "Seattle","state": "WA","maxResults": 20,"includeRaw": false});const { items } = await client.dataset(run.defaultDatasetId).listItems();console.log(items);
Python
import osfrom apify_client import ApifyClientclient = ApifyClient(os.environ['APIFY_TOKEN'])run = client.actor('fetch_cat/npi-registry-scraper').call(run_input={'taxonomyDescription': 'Cardiology', 'city': 'Seattle', 'state': 'WA', 'maxResults': 20, 'includeRaw': False})print(client.dataset(run['defaultDatasetId']).list_items().items)
API usage notes
This returns a run record, not provider rows. Wait for completion and retrieve items from its defaultDatasetId using the Apify API.
MCP and AI agents
You can ask your AI assistant to collect data with NPI Registry Scraper and help you work with the results. The scraper returns the data, and your assistant can then summarize it, compare records or prepare notes.
Connect your assistant through the Apify MCP server. MCP gives your assistant a way to find this scraper, run it and read the results. Follow the official setup and sign-in guide for your app.
Easier setup with an Apify plugin
If you use a supported coding assistant, the official Apify plugin can set up the connection for you. It connects your assistant to Apify and includes instructions for common tasks. Follow the guide for your particular app.
Use Apify AI in Console
Prefer to keep everything in Apify? Open Apify AI in Console and ask it to find Fetch Cat's NPI Registry Scraper. You can describe the data you want and ask questions about the results.
Apify AI is currently in beta. It asks for confirmation before starting an Actor, and normal run charges apply.
Choose your assistant
- Claude and Claude Code (Anthropic): Apify setup guide.
- ChatGPT and Codex (OpenAI): Apify setup guides.
- Grok Bot (xAI): Apify plugin guide.
- Gemini CLI (Google): MCP server setup guide. Use the server URL below with the HTTP configuration supported by Gemini CLI.
Connect just this scraper
To keep your setup focused on this scraper, add this server configuration to a compatible MCP client:
{"mcpServers": {"apify": {"url": "https://mcp.apify.com?tools=fetch_cat/npi-registry-scraper"}}}
Sign in to Apify when your client asks. If your client uses a Bearer token instead, follow its setup guide and keep the token in its secure configuration. Configuration formats vary by app, so use the linked guide if your client needs a different format.
Use Apify's general server
Already connected to the general Apify MCP server at https://mcp.apify.com? You can use it to find this scraper without adding another server. Ask your assistant to use NPI Registry Scraper by Fetch Cat, or give it the identifier fetch_cat/npi-registry-scraper.
Your assistant can check the available settings and retrieve the results from the returned run. If the run is still working, it should follow that run rather than start it again. Both connection options use Apify's hosted service.
Example requests
- “Use Fetch Cat’s NPI Registry Scraper to collect up to 5 Cardiology providers for Seattle, WA with sample NPI numbers cleared and raw records off. Keep registry identifiers, source links and available practice fields without claiming complete local coverage.”
- “Retrieve NPI 1679576722 with a one-record cap and raw source enabled. Keep registry names, taxonomy, dates and source status for my roster reconciliation without making a licensing decision.”
- “Collect up to 5 clinic organizations for Austin, TX using organization entity type and sample NPIs cleared. Keep available practice and mailing addresses separately, without assuming every location match is the primary practice address or supplying patient data.”
Normal Apify charges apply. Check the live Pricing tab before asking your assistant to run a larger batch.
Pay with x402
If your AI agent has a funded wallet, it can pay for Apify usage through x402. This experimental option lets an agent use Apify without a conventional account.
Apify AGI provides a prepaid API token with a spending cap after payment. Your agent can use that token to run this scraper through the Apify API or an authenticated MCP connection.
Some MCP setups also support paying for each request directly. That is a different payment option, so check the official guide for its availability.
Follow the official guide for wallet setup, supported payment options and current terms. Apify handles the payments. Keep wallet keys and payment tokens in your agent's secure configuration.
Other ways for agents to pay
Apify also supports MPP for prepaid access through AGI and Skyfire for eligible Actors. If your agent already uses one of these, see the agentic payment guide to choose the right setup.
FAQ
Does NPI Registry lookup need a CMS account?
No CMS login is needed for these public records. Apify API calls use your Apify token.
Can I export NPI Registry data to CSV?
Yes. Export the run's dataset as CSV, Excel or JSON, or retrieve it through the API.
Is this an NPI Registry API alternative?
It provides an Apify input form, normalized dataset and API access to public CMS records. It is not affiliated with CMS, and it does not replace the official registry or independent license checks.
Why are there no results or missing contact fields?
Filters may be too specific, and source records may omit fields. Broaden a filter and inspect the run outcome. Missing contact data is not filled with guesses.
Can I download all providers at once?
No. The effective limit is 1,200 saved records per run and searches are bounded by registry availability. Use narrower, purposeful searches.
Can I get emails or physician reviews?
This Actor returns registry contact fields and electronic endpoints, not guaranteed outreach emails or review text. Use a separate appropriate source for those workflows.
Related Actors
- Google Maps Email Extractor & Lead Finder — research local businesses separately from registry identities.
- Google Maps Reviews Scraper — collect public business reviews, which are not in NPI records.
- Website Contact Finder — find contact details on known public websites.
- Website Social Profile Finder — find social links for websites you already know.
- Email MX & Deliverability Verifier — check email-domain mail setup for addresses obtained elsewhere.
Support and feedback
For custom additions or integrations, email hello@fetchcat.dev.
Found an error or have a feature request? Open an issue with the run URL, a non-sensitive input example and what you expected.
Need help sharing it? See Apify’s guide to sharing a run when reporting an issue. Sharing a run can give the developer access to its input, logs and results, so use a run that contains no sensitive data. Please leave out API tokens, passwords, cookies, private documents and personal data. Use a public sample URL or a redacted example instead.
Tried this scraper? We'd love to hear how it worked for you. Leave a review to help others choose the right tool and help us improve it. Your feedback means a lot to us.
Made with care for curious people, AI agents and the possibilities in data. ♥