# US Health Facility License Emails · Official Rosters (`corent1robert/us-health-facility-license-leads`) Actor

Official state health-facility licenses with published emails — nursing homes, hospitals and ASCs. Facility, administrator, phone, county. One row per license. Public data. No login.

- **URL**: https://apify.com/corent1robert/us-health-facility-license-leads.md
- **Developed by:** [Corentin Robert](https://apify.com/corent1robert) (community)
- **Categories:** Lead generation, Automation, Business
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.49 / 1,000 facility with emails

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## US Health Facility License Emails · Official Rosters

Export **licensed health facilities** from **official state licensing tables**: facility name, **published email**, phone, administrator, county.

**No login. No API key. Not CMS Compare. Not Google Maps.**

Emails and phones **only when the state publishes them** — never invented, never guessed from a website.

Today the Actor covers **Pennsylvania, New Jersey, and Missouri** (~2.2k licensed rows). More states are added only when the public roster includes a mailbox.

| State | Roster | Email | Phone |
|-------|--------|-------|-------|
| Pennsylvania (DOH nursing homes) | ~666 | Every sampled row | Published on the roster |
| New Jersey (DOH hospitals & ASCs) | ~1,450 | ~98% | Published on the roster |
| Missouri (DHSS ASCs) | ~120 | Every row | Every row |

### Who is this for?

| You are… | Typical goal | Suggested setup |
|----------|--------------|-----------------|
| Staffing / travel nurse vendor | Licensed facilities with a mailbox | Pennsylvania · contacts on |
| Med-device / foodservice / linen | Territory list with an administrator | One county · 20 rows, then raise Max |
| Agency / SDR | One row per facility in the CRM | Dataset view **Outreach CRM** |
| Market research | Count licensed operations | All three states · contacts optional |

**What you get by default:** facility name, published email, phone, city, county, facility type. This is **not** CMS star ratings.

### Quick start

1. Open the Actor in Apify Console.
2. Keep **Pennsylvania** (email on every nursing-home row) or add **New Jersey** / **Missouri**.
3. Leave **Only rows with email or phone** on for a first CRM export.
4. Click **Start**.
5. Download JSON, CSV, Excel, or HTML — views **Overview** or **Outreach CRM**.

**Max facilities = 0** → no Actor-side ceiling. **Free plan: 20 / run.**

### Ready-made examples

| Example | Best for |
|---------|----------|
| Pennsylvania nursing home emails | Highest email fill, named administrator |
| New Jersey hospital & ASC emails | Larger acute-care roster |
| Missouri ASC emails | Surgery centers with administrator email |
| Three-state 20-row sample | Quick Try |

### What it extracts

| Category | Fields |
|----------|--------|
| Identity | `facilityName`, `contactName`, `licenseNumber`, `facilityType` |
| Contact | `contactEmail`, `contactPhone`, `website` |
| Location | `address`, `city`, `stateCode`, `postalCode`, `county` |
| License | `licenseStatus`, `capacity` (beds when published) |

Empty source fields stay empty. We do not invent mailboxes. Download JSON, CSV, Excel, or HTML from the Dataset tab.

### How it works

1. Read the public licensing table for each state you picked (Pennsylvania first when you choose all three — highest email fill).
2. Copy facility, contact, email, phone and county **when they are printed**.
3. Skip government and placeholder mailboxes.
4. Write one row as soon as it matches your filters — the Dataset fills during the run.

### Input

| Parameter | Type | Default | Description |
|-----------|------|---------|-------------|
| `states` | array | `["PA"]` Try | `PA`, `NJ`, `MO`, or `ALL` (all three, email-first order). |
| `county` | string | empty | Optional. `Allegheny`, `Allegheny County`, and mixed case all match. |
| `onlyWithContact` | boolean | `false` (`true` in Try) | Keep only rows with a published email or phone. |
| `maxItems` | integer | `20` | **0** = no numerical cap. **Free plan: 20 / run.** |

```json
{ "states": ["PA"], "onlyWithContact": true, "maxItems": 20 }
```

```json
{ "states": ["NJ"], "county": "Morris", "onlyWithContact": true, "maxItems": 20 }
```

```json
{ "states": ["ALL"], "onlyWithContact": true, "maxItems": 20 }
```

### Output example

```json
{
  "providerKey": "PA-711002",
  "facilityName": "Embassy of Saxonburg",
  "contactName": "Rebecca Shoop",
  "contactEmail": "administrator@ehsaxonburg.net",
  "contactPhone": "(724) 352-9445",
  "website": "https://embassyhealthcare.net",
  "city": "Saxonburg",
  "stateCode": "PA",
  "county": "Butler",
  "facilityType": "Nursing home"
}
```

### How much does it cost to scrape health facility licenses?

Pay-per-event. List price includes a $0.00005 start. FREE pays the most; Gold+ less. These dumps usually finish in **under a minute** for a 20-row Try.

| Scenario | FREE | Bronze | Silver | Gold |
|----------|------|--------|--------|------|
| 20 facilities with email | ~$0.08 | ~$0.07 | ~$0.06 | ~$0.05 |
| 20 facilities with phone | ~$0.05 | ~$0.04 | ~$0.04 | ~$0.03 |

Free Apify plan: **20 facilities per run**. Paid plans follow your max charge.

### Is it legal to scrape health facility licenses?

This Actor copies data the states publish on **public** licensing tables. Names, emails and phones are personal data — your use must comply with HIPAA marketing rules where they apply, GDPR, CAN-SPAM, TCPA and any rules that apply to you. This is not legal advice. See [Apify on the legality of web scraping](https://blog.apify.com/is-web-scraping-legal/).

Independent tool. Not affiliated with Pennsylvania DOH, New Jersey DOH or Missouri DHSS.

### Local development

```bash
cd us-health-facility-license-leads
npm install
cp .actor/INPUT.json storage/key_value_stores/default/INPUT.json
apify run --purge
```

Use `apify run` (not `npm start`). Root `input.json` is merged locally; CLI KV input wins on key collision. Local `storage/` is not synced to Apify Console.

`npm test` runs mapper and county tests (no network).

### FAQ

**Do you invent emails?** No. A mailbox appears only when the licensing table prints one.

**Is this CMS Nursing Home Compare?** No. CMS Compare is ratings, staffing and (often) a phone. This Actor copies **state license tables that print an email**.

**Why only three states?** Those public rosters include a statewide email field. We do not sell a phone-only SKU as “emails”.

**Is this the whole United States?** No. Three states with a public mailbox on the register. We add a state when that condition is met.

**Do I need an API key?** No.

### Support

Questions, custom scrapers, or extra states: <corentin@outreacher.fr>.

Ready? Keep Pennsylvania, leave contacts on, and click Start.

# Actor input Schema

## `states` (type: `array`):

One or more states. Try starts on Pennsylvania (emails on every nursing-home row).

## `county` (type: `string`):

Keep one county (e.g. Allegheny, Morris, Clay). “Allegheny County” also works. Leave empty for the whole state.

## `onlyWithContact` (type: `boolean`):

Skip facilities that do not publish a mailbox or phone.

## `maxItems` (type: `integer`):

Stop after this many matching facilities. **0 = no numerical cap**.

## Actor input object example

```json
{
  "states": [
    "PA"
  ],
  "onlyWithContact": true,
  "maxItems": 20
}
```

# Actor output Schema

## `dataset` (type: `string`):

All exported licensed facilities.

## `overview` (type: `string`):

Facility, location and published contacts.

## `outreachCrm` (type: `string`):

Administrator, email, phone and website.

## `runLog` (type: `string`):

Plain-text progress for this run.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "states": [
        "PA"
    ],
    "onlyWithContact": true,
    "maxItems": 20
};

// Run the Actor and wait for it to finish
const run = await client.actor("corent1robert/us-health-facility-license-leads").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "states": ["PA"],
    "onlyWithContact": True,
    "maxItems": 20,
}

# Run the Actor and wait for it to finish
run = client.actor("corent1robert/us-health-facility-license-leads").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "states": [
    "PA"
  ],
  "onlyWithContact": true,
  "maxItems": 20
}' |
apify call corent1robert/us-health-facility-license-leads --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,corent1robert/us-health-facility-license-leads"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/NmaEcERc6TZfaxLwe/builds/z8rrXydPRnBpXEoq7/openapi.json