# Funeral Director & Home License Verification Data (`kempdata/us-funeral-industry-licenses`) Actor

Verify funeral director, embalmer, funeral home and crematory licenses in bulk across 5 states (IL, DE, TX, CT, CO). 8,228 credentials from official state registries. License expiration dates, renewal windows and disciplinary actions. For consolidators, supply vendors and preneed insurers.

- **URL**: https://apify.com/kempdata/us-funeral-industry-licenses.md
- **Developed by:** [Mark Kemp](https://apify.com/kempdata) (community)
- **Categories:**
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.50 / 1,000 funeral industry license records

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?

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 Funeral Industry Licenses — Homes, Directors & Crematories

**The funeral industry's official license rolls, in one clean feed.** Funeral homes, funeral directors, embalmers, crematories, cemetery licensees, and prepaid-funeral sellers — pulled straight from state government registries and normalized into one format, with lead flags computed for you. **States included:** **Illinois (funeral and cemetery boards), Delaware, and Texas preneed sellers**. Every state that publishes its full license roster through an official data feed gets added as we find it - no request needed.

### Who this is for

- **Suppliers to the death-care industry** — caskets, urns, vaults, embalming supplies, management software, preneed insurance. The *new licenses* filter hands you every newly licensed director and newly opened establishment: prospects nobody else has called yet.
- **Funeral home acquirers & consolidators** — a complete establishment roster by state, county, and city for mapping markets and finding targets.
- **Recruiters & staffing** — every licensed director and embalmer in a state, with license status and disciplinary history flags.
- **Continuing-education and renewal-services providers** — the *expiring soon* filter shows exactly when renewal season hits. (Illinois renews every funeral license in the state on the same date — over 3,000 licensees needing CE hours in the same window.)
- **Preneed & insurance compliance teams** — Texas's official registry of licensed prepaid funeral contract sellers, with addresses and phone numbers.

### What you get

One normalized record per license:

```json
{
    "state": "IL",
    "record_type": "individual",
    "license_type": "FUNERAL AND EMBALMER — LICENSED FUNERAL DIRECTOR AND EMBALMER",
    "license_number": "034017507",
    "name": "KENNEDY JACOBS",
    "city": "DOWNERS GROVE",
    "status": "ACTIVE",
    "issue_date": "2019-06-12",
    "expiration_date": "2027-05-31",
    "expires_in_days": 277,
    "is_expiring_soon": true,
    "is_new_license": false,
    "ever_disciplined": false,
    "lead_reasons": ["License expires in 277 days"],
    "source": "Illinois IDFPR Professional Licensing roster"
}
```

Business records (funeral homes, crematories, establishments) carry the business name; Texas preneed records include street address and phone. Export to Excel, CSV, or JSON in one click, or pull on a schedule via API.

### How to use it

1. Pick your **states** (or leave empty for all).
2. Pick a **record filter**: all records, licenses expiring soon (set the window), or recently issued licenses (set the window).
3. Choose **businesses, individuals, or both**, and whether to include lapsed licenses.
4. Set **maximum records** — you're only charged for what's delivered.

### One schema across every state

Every licence roster in this catalogue delivers **the same columns, in the same
order, meaning the same thing** — whichever state or profession the records came
from. Stack this dataset on top of any other KempData roster and the columns
line up.

That takes real work. Illinois writes a lapsed licensee as `NOT RENEWED` in
block capitals; Delaware writes the identical situation as `Delinquent`. Both
arrive here as `status: "lapsed"`. Names arrive SHOUTING and glued together;
they leave as `full_name`, `first_name`, `middle_name`, `last_name` in proper
case. Dates are **MM/DD/YYYY**, with an `_iso` twin for spreadsheets and imports.

**The state's own word is never thrown away.** Every translated value ships
beside a `*_raw` twin — `status_raw`, `credential_raw`, `name_raw` — holding the
source's exact string, so you can always check our work or apply your own rules.
`status_basis` tells you whether the standing is the state's published fact or
computed from the expiration date.

**`lapsed` is worth knowing about.** It is the recall pool: people who held the
licence, let it run out, and can renew. When you need experienced people in a
hurry, that is the list to call.

Full column reference: `docs/SCHEMA.md` in the source repository.

### Data source & fair use

Every record comes from an official state open-data API: the Illinois IDFPR professional-licensing roster, the Delaware Division of Professional Regulation roster, and the Texas Department of Banking's prepaid funeral seller registry. These are public records the states publish for exactly this kind of use — no scraping, no bot games. The Actor reads politely (paged requests, rate-limit handling) and republishes only what the state itself makes public.

### Want another state?

State funeral boards publish their rosters in wildly different ways, and they're being added to this Actor in the order people request them. Open an issue and name your state — it moves to the front of the line.

### Support

Questions and issues answered fast — usually within hours.

# Actor input Schema

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

Which state registries to pull: IL (Illinois), DE (Delaware), TX (Texas), CT (Connecticut), CO (Colorado). Leave empty for every state this product covers.

## `recordFilter` (type: `string`):

"Expiring soon" = licenses coming up for renewal (renewal-season leads). "New licenses" = recently issued (new firms & fresh professionals — prime prospects for suppliers). Texas preneed sellers have no dates published, so they appear only under "All records".

## `expiringWithinMonths` (type: `integer`):

For the expiring-soon filter: include licenses that expire within this many months.

## `newWithinMonths` (type: `integer`):

For the new-licenses filter: include licenses first issued within this many months.

## `includeBusinesses` (type: `boolean`):

Include business/establishment records in the results.

## `includeIndividuals` (type: `boolean`):

Include individual professional licenses in the results.

## `onlyActive` (type: `boolean`):

Skip expired, lapsed, and revoked licenses.

## `maxRecords` (type: `integer`):

Stop after this many results. You are only charged for records actually returned.

## `socrataAppToken` (type: `string`):

Optional app token for the state open-data APIs. Not required for normal use.

## Actor input object example

```json
{
  "states": [],
  "recordFilter": "all",
  "expiringWithinMonths": 6,
  "newWithinMonths": 6,
  "includeBusinesses": true,
  "includeIndividuals": true,
  "onlyActive": true,
  "maxRecords": 1000
}
```

# Actor output Schema

## `records` (type: `string`):

Dataset of normalized funeral-industry license records with expiring-license and new-license lead flags.

# 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("kempdata/us-funeral-industry-licenses").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 = {}

# Run the Actor and wait for it to finish
run = client.actor("kempdata/us-funeral-industry-licenses").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 '{}' |
apify call kempdata/us-funeral-industry-licenses --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,kempdata/us-funeral-industry-licenses"
        }
    }
}

```

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/9Uk9qdhXupCZ5zJFU/builds/iuY8ThasR06OTYjjS/openapi.json