# HRSA Health Centers (FQHC) Sites Scraper with Contacts (`talcoe/hrsa-health-centers`) Actor

Scrape federally qualified health center (FQHC and Look-Alike) sites from HRSA with address, phone, website, NPI and coordinates, filtered by state, city, type and name, priced per result.

- **URL**: https://apify.com/talcoe/hrsa-health-centers.md
- **Developed by:** [M Usama](https://apify.com/talcoe) (community)
- **Categories:** Lead generation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $5.00 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## 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.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

### What does HRSA Health Centers (FQHC) Sites Scraper do?

It returns every Federally Qualified Health Center (FQHC) and FQHC Look-Alike service delivery site listed by HRSA, about 19,000 active sites across the US and territories. Each record has the site name, parent health center, street address, phone, website, operating hours, NPI, Medicare billing number, coordinates, county, congressional district and more. Filter by state, city, center type, location type or name keywords to keep runs small. Pricing is per result.

### Data source

The public HRSA Data Warehouse download "Health Center Service Delivery and Look-Alike Sites" on data.hrsa.gov, which HRSA refreshes daily.

### Why use it?

- Build lead lists of community health centers for healthcare vendors, EHR and billing companies, staffing firms and medical suppliers.
- Map safety net clinics by state, county or congressional district for research, grants and policy work.
- Find mobile vans, school based sites and seasonal sites separately from permanent clinics.
- Replace manual downloads and spreadsheet cleanup of a 60 column government file.

### How to use it

1. Open the Actor and set the filters.
2. Click Start. Download results as JSON, CSV or Excel, or read them through the API.
3. Add a Schedule and an Integration (Slack, Google Sheets, webhook) to get fresh records automatically.

### Input

| Field | Description |
|---|---|
| `states` | Two letter state or territory codes, for example `VT`, `CA`, `PR`. Empty means all states. |
| `city` | Only sites in this city (exact match, case insensitive). |
| `keywords` | Keep sites whose site name or health center name contains any of these words. |
| `centerType` | `all`, `fqhc` (grantees) or `lookalike` (FQHC Look-Alikes). |
| `locationType` | `all`, `Permanent`, `Mobile Van` or `Seasonal`. |
| `maxResults` | Hard stop for the run. You are billed per result, so this caps the cost. |
| `proxyConfiguration` | Apify proxy is recommended for larger runs. |

Example input:

```json
{ "states": ["VT"], "centerType": "all", "maxResults": 50 }
```

### Output

Every record has the same shape (trimmed example):

```json
{
  "id": "BPS-H80-000197",
  "siteName": "EAST CORINTH",
  "healthCenterName": "LITTLE RIVERS HEALTH CARE",
  "address": "720 Village Rd",
  "city": "East Corinth",
  "state": "VT",
  "zip": "05040-9783",
  "phone": "802-439-5321",
  "website": "https://www.littlerivers.org",
  "centerType": "Federally Qualified Health Center (FQHC)",
  "locationType": "Permanent",
  "operatingHoursPerWeek": 45,
  "npi": "1972751279",
  "latitude": 44.06441705,
  "longitude": -72.22171971,
  "isLookAlike": false,
  "medicareBillingNumber": "471824",
  "healthCenterNumber": "H80CS06658",
  "addedToScopeDate": "2006-06-01",
  "county": "Orange County",
  "congressionalDistrict": "Vermont At Large",
  "scrapedAt": "2026-10-06T08:32:16.842Z"
}
```

| Field | Meaning |
|---|---|
| `id` | HRSA site number (BPHC assigned number). Stable, safe for deduplication between runs. |
| `siteName` / `healthCenterName` | The clinic site and the parent organization that operates it. |
| `address`, `city`, `state`, `zip` | Site location. |
| `phone`, `website` | Site contact details as published by HRSA. |
| `centerType`, `isLookAlike` | FQHC grantee or FQHC Look-Alike. |
| `locationType` | Permanent, Mobile Van or Seasonal. |
| `operatingHoursPerWeek` | Hours the site is open per week. |
| `npi`, `medicareBillingNumber` | Site NPI and Medicare billing number when HRSA lists them. |
| `latitude`, `longitude` | Geocoded site coordinates. |
| `organizationAddress` and related | Parent organization address. |

### Pricing

Pay per event: a small fee when a run starts, then a fixed price per result returned. You only pay for records that pass your filters. Set `maxResults` to cap any run.

### Limitations

- Only active sites are in the HRSA file. Closed sites are not listed.
- Contact data is business information only. Email addresses and named contacts are not published in this file.
- NPI, Medicare billing number and website are empty for many sites because HRSA does not have them.
- Fields reflect HRSA's file as of its last daily refresh.

### FAQ

**Is this legal?** The Actor reads a public government dataset that HRSA publishes for any visitor without a login and stores only business information published for that purpose. You are responsible for how you use the data.

**Something is missing or broken?** Open an issue in the Issues tab; response time is usually under a day.

# Actor input Schema

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

Two letter state or territory codes, for example VT, CA, PR. Leave empty for all states.

## `city` (type: `string`):

Only sites in this city (exact match, case insensitive). Optional.

## `keywords` (type: `array`):

Keep sites whose site name or health center name contains any of these words, for example community, migrant, dental.

## `centerType` (type: `string`):

FQHC grantees, FQHC Look-Alikes, or both.

## `locationType` (type: `string`):

Permanent sites, mobile vans, or seasonal sites.

## `maxResults` (type: `integer`):

Hard stop for the run. You are billed per result, so this caps the cost.

## `proxyConfiguration` (type: `object`):

Apify proxy is recommended for larger runs.

## Actor input object example

```json
{
  "states": [
    "VT"
  ],
  "keywords": [],
  "centerType": "all",
  "locationType": "all",
  "maxResults": 50,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# 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": [
        "VT"
    ],
    "proxyConfiguration": {
        "useApifyProxy": false
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("talcoe/hrsa-health-centers").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": ["VT"],
    "proxyConfiguration": { "useApifyProxy": False },
}

# Run the Actor and wait for it to finish
run = client.actor("talcoe/hrsa-health-centers").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": [
    "VT"
  ],
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}' |
apify call talcoe/hrsa-health-centers --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,talcoe/hrsa-health-centers"
        }
    }
}
```

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/FhQZocq6BB9AAueyn/builds/CRXHQ9QnN1Mg9NNZx/openapi.json