Funeralocity APIfuneralocity.com ↗
Access funeral home listings, GPL itemized pricing, ratings, and contact info for US locations via the Funeralocity API. Search by city and state.
What is the Funeralocity API?
The Funeralocity API provides access to funeral home data across the United States through 3 endpoints, covering state and city discovery through to detailed funeral home profiles. The search_homes endpoint returns contact information, ratings, and itemized General Price List (GPL) fees for every home found within a 25-mile radius of the searched city, making it practical for cost comparison tools, end-of-life planning apps, and directory services.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/335ba392-7c8f-42e4-af1c-5bb40e6f267d/get_states' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace funeralocity-com-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
from parse_apis.funeralocity_api import Funeralocity, State, City, FuneralHome, Pricing, StateCode
client = Funeralocity()
# List all US states
for state in client.states.list():
print(state.code, state.name)
# Construct a state and list its cities
il = client.state(code=StateCode.IL)
for city in il.cities.list():
print(city.name, city.search_url)
# Search funeral homes in Chicago, IL
for home in il.search(city="Chicago"):
print(home.name, home.address, home.city, home.zip, home.phone, home.rating)
print(home.summary_pricing.direct_cremation, home.summary_pricing.benchmark_burial)
print(home.detailed_pricing.basic_services_price, home.detailed_pricing.embalming_price)
List all supported US states and their two-letter codes. Returns a static list of 51 entries (50 states plus DC). No parameters required. Each entry provides a two-letter abbreviation and the full state name.
No input parameters required.
{
"type": "object",
"fields": {
"items": "array of state objects, each with 'code' (two-letter abbreviation) and 'name' (full state name)"
},
"sample": {
"data": {
"items": [
{
"code": "IL",
"name": "Illinois"
},
{
"code": "CA",
"name": "California"
},
{
"code": "NY",
"name": "New York"
}
]
},
"status": "success"
}
}About the Funeralocity API
Endpoints Overview
The API is structured around a three-step discovery flow. get_states returns a static list of 51 entries — all 50 US states plus Washington DC — each with a code (two-letter abbreviation) and a name. get_cities accepts a required state parameter (uppercase two-letter code) and returns up to 20 major cities for that state, each with a Name and a SearchUrl slug that maps to the source site's city search page.
Funeral Home Search
search_homes is the primary endpoint. It requires a city string and a state code, and accepts an optional limit integer to cap the result count. The response object includes city, state, total_count, and a homes array. Each home in the array carries an id, contact details, ratings, and detailed GPL pricing data — the itemized fee schedule that US funeral homes are federally required to publish. This makes it possible to compare line-item costs such as basic services fees, embalming, cremation, and casket prices across multiple providers in a given area.
Coverage and Data Shape
Search results cover funeral homes within a 25-mile radius of the specified city center, so smaller cities will surface homes from surrounding towns. The get_cities endpoint covers major cities per state rather than a full municipal database, so less-populated localities may need to be searched via the nearest major city. The total_count field in search_homes responses tells you how many homes matched before any limit is applied, which is useful for building pagination logic on the client side.
The Funeralocity API is a managed, monitored endpoint for funeralocity.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when funeralocity.com changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official funeralocity.com API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Build a funeral home cost comparison tool using GPL itemized pricing from
search_homes - Populate a state-and-city selector in an end-of-life planning app using
get_statesandget_cities - Aggregate funeral home ratings across a metro area for a consumer review dashboard
- Generate city-level reports on average funeral service fees using
total_countand pricing fields - Build a funeral home directory with contact information sourced from
search_homesresults - Alert families to lower-cost cremation or burial options within a 25-mile radius of a given city
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Funeralocity have an official developer API?+
What pricing data does `search_homes` return for each funeral home?+
homes array includes summary pricing alongside detailed GPL (General Price List) data — the federally mandated itemized fee schedule. This covers individual service line items rather than just a single aggregate price, letting you compare costs at a granular level.Does `get_cities` cover every city in a state, or only major ones?+
get_cities, using the nearest major city with search_homes will still surface homes within 25 miles. You can fork this API on Parse and revise it to add a broader city lookup endpoint if your use case requires finer geographic resolution.Can I retrieve funeral home data by ZIP code or coordinates instead of city name?+
search_homes. You can fork it on Parse and revise to add a ZIP-code or coordinate-based search endpoint.Does the API expose funeral home reviews or review text beyond aggregate ratings?+
search_homes response includes ratings but does not currently expose individual review text or reviewer details. Summary ratings per home are available. You can fork this API on Parse and revise it to add a review-text endpoint if that data is accessible on the source site.