Medicare Medical Equipment Supplier Scraper

What does this Actor do?

Medicare Medical Equipment Supplier Scraper fetches publicly available Medicare DMEPOS (Durable Medical Equipment, Prosthetics, Orthotics & Supplies) supplier records directly from CMS's official open data API. Each record includes the supplier's name, National Provider Identifier (NPI), specialty/category, and full address.

Optionally, the Actor can enrich each supplier by looking up its NPI in the public NPPES NPI Registry to add a phone number and, for organizations, an authorized contact name and title.

This Actor uses only official CMS and NPPES government data APIs - no scraping of medicare.gov pages is involved, so results are accurate, structured, and not subject to bot-blocking.

Why scrape Medicare DME supplier data?

• Build a lead list of DME suppliers by US state or specialty
• Research active Medicare-billing suppliers for market analysis
• Verify a supplier's NPI, address, and specialty against official CMS records
• Cross-reference DME suppliers with other B2B medical equipment datasets
• Identify supplier contact points for outreach or compliance checks

Features

• Pulls directly from CMS's official DMEPOS-by-supplier open data API
• Filter by US state and/or supplier specialty/category
• Optional NPPES enrichment for phone and authorized contact name/title
• Automatic pagination and deduplication by NPI
• Respects maxItems

Input

Field	Type	Required	Default	Description
state	string	No	""	Two-letter US state abbreviation to filter suppliers (e.g. CA)
supplierCategory	string	No	""	Exact CMS specialty/category description to filter by
maxItems	integer	No	100	Maximum supplier records to fetch. Set 0 for unlimited
enrichContacts	boolean	No	true	Look up each supplier's NPI in NPPES to add phone/contact details
proxyConfiguration	object	No	{ "useApifyProxy": false }	Not required - the CMS/NPPES APIs are open government data sources

Output

{
    "supplierName": "Reconstructive Hand To Shoulder Of Indiana, Llc",
    "npi": "1003000399",
    "supplierType": "Organization",
    "category": "General Surgery",
    "industry": "General Surgery",
    "contactName": "Michael Pannunzio",
    "contactTitle": "Partner",
    "phone": "317-249-2616",
    "address": "13431 Old Meridian Street, Suite 225",
    "city": "Carmel",
    "state": "IN",
    "zipCode": "46032",
    "country": "US",
    "verifiedSupplier": true,
    "source": "Medicare (CMS DMEPOS Supplier Data)",
    "scrapedAt": "2026-08-19T12:00:00.000Z"
}

Fields with no equivalent in Medicare's public data (e.g. productName, employeeCount, website, email) are always returned as null rather than guessed.

Output fields

Field	Description
supplierName	Supplier/company name, or individual practitioner name
npi	National Provider Identifier
supplierType	Organization or Individual
category / industry	CMS supplier specialty/category
contactName, contactTitle	Authorized contact (organizations only, via NPPES)
phone	Phone number (via NPPES enrichment)
address, city, state, zipCode, country	Registered location
verifiedSupplier	true - the supplier appears in official CMS Medicare billing data
source, scrapedAt	Data provenance and fetch timestamp

Use cases

• Generate DME supplier lead lists filtered by state or specialty
• Feed a CRM with verified Medicare supplier contacts
• Research supplier density and coverage by region
• Support compliance/due-diligence checks on DME suppliers
• Combine with other CMS datasets for deeper market analysis

Pricing

Apify usage is billed according to this Actor's configured pricing plan on the Apify Store.

FAQ

Where does this data come from? CMS's official "Medicare Durable Medical Equipment, Devices & Supplies - by Supplier" open dataset (data.cms.gov), plus the public NPPES NPI Registry for contact enrichment. Both are official U.S. government open data sources.

Why is phone sometimes null? Phone numbers come from NPPES enrichment, which requires a registered LOCATION address with a phone number on file. Not every NPI record has one.

Does this include DME product/catalog data? No. The CMS supplier dataset is aggregated Medicare billing data per supplier, not a product catalog - productName, brand, and similar product fields are always null.

Why doesn't state/supplierCategory support partial matches? The underlying CMS API requires exact-match filter values for these fields.

Disclaimer

This Actor is an independent tool and is not affiliated with, endorsed by, or sponsored by the Centers for Medicare & Medicaid Services (CMS) or Medicare.gov. It only accesses official, publicly published open government data. Users are responsible for complying with applicable terms of use, laws, and privacy requirements when using the collected data.

Preview