Echovita Obituary & Funeral Home Scraper: $5.00 per 1,000 Results

Each obituary record delivers up to 31 fields covering full names, death dates, biography texts, and service logistics across the US, Canada, Australia, and New Zealand at $5.00 per 1,000 results on the free plan. The extractor queries records via seven browse and search modes without requiring account logins or session authentications. The free tier includes monthly usage covering up to 1,000 results. This setup serves genealogists, demographic researchers, and local reporters tracking regional notices. It is not suitable for researchers needing verified deceased portrait photos, as image fields return automated social share cards rather than verified photographs.

Try it: open Echovita Obituary & Funeral Home Scraper on Apify, sign in on the free plan and run the prefilled example.

Can you try Echovita Obituary & Funeral Home Scraper before paying?

Yes. Apify's free plan includes $5.00 of prepaid usage every month and asks for no credit card. At $0.005 per result, that covers up to 1,000 results of Echovita Obituary & Funeral Home Scraper a month, before run-start charges and platform usage.

Echovita Obituary & Funeral Home Scraper was last updated on 2026-07-13. It is one of 1,725 Actors CrawlerBros publishes on Apify, which together have 680,173 lifetime public runs and an average rating of 4.63 out of 5 across 416 reviews.

What does it cost to run Echovita Obituary & Funeral Home Scraper?

Each result costs $0.005 on Apify's free plan, which is $5.00 per 1,000 results. Starting a run is charged separately at $0.005 per GB of Actor memory. Apify also bills the platform usage each run consumes, at the rates of your Apify plan, on top of these charges.

The maxItems setting is your primary cost lever because result fees scale directly with total dataset items written. Start validation runs with maxItems capped low to inspect data formats before scaling up your crawl. Combining regional filters like city or state with narrow rangeTime windows keeps overall output counts focused and predictable.

How do you run Echovita Obituary & Funeral Home Scraper from the API?

The schema marks 1 of its 18 controls as required: mode. The payload below uses the schema's own prefilled values, so it runs as written once you substitute your API token.

Call the synchronous endpoint to start a run and receive dataset items in one request:

curl -X POST "https://api.apify.com/v2/acts/crawlerbros~echovita-scraper/run-sync-get-dataset-items?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"mode":"search","state":"ca","caProvince":"on","auState":"nsw","nzRegion":"ni","city":"los-angeles","deathDate":"2026-07-10","funeralHomeUrl":"https://www.echovita.com/us/funeral-homes/mi/charlotte/pray-funeral-home-inc-2383"}'

The same run from Python, using the official client:

from apify_client import ApifyClient

client = ApifyClient("<YOUR_APIFY_TOKEN>")

run_input = {
  "mode": "search",
  "state": "ca",
  "caProvince": "on",
  "auState": "nsw",
  "nzRegion": "ni",
  "city": "los-angeles",
  "deathDate": "2026-07-10",
  "funeralHomeUrl": "https://www.echovita.com/us/funeral-homes/mi/charlotte/pray-funeral-home-inc-2383"
}

run = client.actor("crawlerbros~echovita-scraper").call(run_input=run_input)

for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

And from Node.js:

import { ApifyClient } from 'apify-client'

const client = new ApifyClient({ token: '<YOUR_APIFY_TOKEN>' })

const input = {
  "mode": "search",
  "state": "ca",
  "caProvince": "on",
  "auState": "nsw",
  "nzRegion": "ni",
  "city": "los-angeles",
  "deathDate": "2026-07-10",
  "funeralHomeUrl": "https://www.echovita.com/us/funeral-homes/mi/charlotte/pray-funeral-home-inc-2383"
}

const run = await client.actor('crawlerbros~echovita-scraper').call(input)
const { items } = await client.dataset(run.defaultDatasetId).listItems()
console.log(items)

The synchronous endpoint holds the connection open until the run finishes, which is convenient for small batches and wrong for large ones. For anything long running, start the run asynchronously and poll, or attach a webhook, so a dropped connection does not cost you the results.

Which Echovita Obituary & Funeral Home Scraper inputs matter, and which can you skip?

The mode parameter dictates the entire run and decides whether you harvest obituaries by name, browse regions, or collect funeral home directories. For regional crawls, pair mode with the matching territory parameter, such as state or caProvince, while leaving proxyConfiguration on its default. Keep rangeTime and birth or death year boundaries unconfigured until you establish whether broad sweeps return acceptable volume.

• mode (string): What to fetch. Default: "search".
• state (string): Required for byState / byCity when country=us. Optional location filter for funeralHomes.
• caProvince (string): Required for byState / byCity when country=ca. Optional location filter for funeralHomes.
• auState (string): Required for byState / byCity when country=au. Optional location filter for funeralHomes.
• nzRegion (string): Required for byState / byCity when country=nz. Optional location filter for funeralHomes. Echovita groups New Zealand obituaries by island rather than by region/district.
• city (string): City name, required for byCity (used together with the state/province/region field for the selected country). Optional location filter for funeralHomes.
• deathDate (string): Date in YYYY-MM-DD format. Returns obituaries of people who died on this date, in the selected country.
• funeralHomeUrl (string): Direct echovita.com funeral home detail URL. Returns the obituaries that funeral home has published.
• nameQuery (string): Full or partial name to search obituaries for. Default: "Smith".
• country (string): Which Echovita market to browse. Determines which of state / caProvince / auState / nzRegion applies to byState/byCity/funeralHomes. Default: "us".
• obituaryUrls (array): Direct echovita.com obituary detail URLs to fetch (any supported country). Default: [].
• rangeTime (string): Limit search / byState / byCity / funeralHomes / byFuneralHome to obituaries published within this window (Echovita's own recency filter). Not used by byDate, byUrls. Default: "4".

The other 6 controls, with their defaults, are listed in the input schema on Echovita Obituary & Funeral Home Scraper on Apify.

Fixed-choice controls: mode accepts search (Search obituaries by name), byState (Browse obituaries by state/province/region), byCity (Browse obituaries by city), byDate (Browse obituaries by date of death), byUrls (Lookup specific obituaries by URL), funeralHomes (Browse funeral home directory), byFuneralHome (Browse obituaries handled by a specific funeral home); country accepts us (United States), ca (Canada), au (Australia), nz (New Zealand); state accepts 51 values, including ca (California), al (Alabama), ak (Alaska), az (Arizona); caProvince accepts 13 values, including on (Ontario), ab (Alberta), bc (British Columbia), mb (Manitoba); auState accepts act (Australian Capital Territory), nsw (New South Wales), nt (Northern Territory), qld (Queensland), sa (South Australia), tas (Tasmania), vic (Victoria), wa (Western Australia); nzRegion accepts ni (North Island), si (South Island); rangeTime accepts 0 (Last 7 days), 1 (Last month), 2 (Last 6 months), 3 (Last year), 4 (All time).

What does Echovita Obituary & Funeral Home Scraper return?

The scraper outputs clean obituary profiles with biography copy, death dates, ages, and memorial locations, or funeral home directory listings with addresses and service offerings. Empty fields are entirely omitted from output objects rather than returned as null values. The records do not contain official civil death certificates, surviving kin contact details, or certified portrait photography.

Output per obituary

• obituaryId
• fullName, givenName, familyName
• birthDate, deathDate - ISO dates, when disclosed
• birthYear, deathYear, ageAtDeath
• city, state, stateCode - state, province, or region (e.g. Ontario / on, New South Wales / nsw, North Island / ni)
• country, countryCode - United States/us, Canada/ca, Australia/au, or New Zealand/nz
• latitude, longitude
• biography - full obituary text
• headline - page headline (e.g. Jane Doe Obituary (1942-2026) | City, ST)
• datePublished, dateModified
• funeralHomeName, funeralHomeUrl - when the obituary lists a funeral home
• serviceName, serviceStartDate, serviceLocationName, serviceAddress, serviceOrganizer - when a funeral/memorial service is scheduled
• socialImageUrl - the page's social-share image (usually an auto-generated card with the name/dates overlaid, not necessarily a real photo of the deceased)
• sourceUrl
• recordType: "obituary", scrapedAt

Output per funeral home (mode=funeralHomes / obituaries browsed via mode=byFuneralHome)

• name, phone, address, website
• city, state, stateCode
• country, countryCode
• logoUrl - the funeral home's uploaded logo, when set; otherwise Echovita's generic placeholder icon
• servicesOffered[] - e.g. traditional service, cremation, pre-arrangements
• latitude, longitude
• sourceUrl
• recordType: "funeralHome", scrapedAt

These are the documented fields. Optional ones can be empty on a given record, so measure how often each field your deliverable depends on is populated across a real sample before automating the handoff.

How do you build the workflow end to end?

Open Echovita Obituary & Funeral Home Scraper and work through these in order. Each step ends with something to check, so a bad configuration surfaces on a small run rather than a scheduled one.

1. Select mode search, set nameQuery to a specific family name, and set maxItems to 5 to execute a minimal discovery run.
2. Verify the output records carry expected identity keys such as obituaryId, fullName, and sourceUrl before scheduling larger runs.
3. Switch mode to byState or byCity and provide the appropriate regional parameter, such as state for country us or caProvince for ca.
4. Configure rangeTime to limit collection windows, choosing 0 for seven-day monitoring or 4 for full historical coverage.
5. Apply minBirthYear, maxBirthYear, minDeathYear, or maxDeathYear filters to narrow candidate windows and avoid paying for out-of-scope records.
6. For funeral vendor analysis, set mode to funeralHomes, populate state or city, and inspect returned telephone and address fields.
7. Target specific provider listings by passing the discovered Echovita vendor link into funeralHomeUrl under mode byFuneralHome.
8. Direct raw links directly into the obituaryUrls string list under mode byUrls to re-scrape or refresh individual records.

How do you apply it? Three worked playbooks

These are Echovita Obituary & Funeral Home Scraper's own documented use cases, each worked through as an operating pattern rather than a description.

Use case 1: Genealogy research

Outcome: Bulk-collect obituary records for family history projects

Configure: Set mode to search, country to us, nameQuery to the target surname, minDeathYear to 1990, maxDeathYear to 2020, and maxItems to 100.

Working method: Execute an initial surname run with a strict birth or death range. Review the output biography and familyName values to confirm branch relevance before widening date filters.

Deliverable: A deduplicated CSV or JSON export of obituary entries containing biography texts, birth and death dates, and family relationships.

Stop condition: Stop if extracted records begin returning irrelevant lineages or if birthYear values fall completely outside the researched generation.

Use case 2: Local news / media monitoring

Outcome: Track recent obituaries for a city, region, or country

Configure: Set mode to byCity, country to us, state to mi, city to olivet, rangeTime to 0, and maxItems to 50.

Working method: Run on an automated recurring schedule targeting the local municipality. Filter ingested payloads against previously seen obituaryId values to isolate fresh notices.

Deliverable: A rolling delta feed of local death notices including deceased full names, ageAtDeath, and scheduled service times.

Stop condition: Abort the run if the city parameter fails to resolve or returns empty results over multiple scheduled intervals.

Use case 3: Funeral industry market research

Outcome: Build a directory of funeral homes by state/province or city, or pull the full publication history of one funeral home

Configure: Set mode to funeralHomes, country to us, state to ny, and maxItems to 200.

Working method: Extract regional funeral home entities first to assemble addresses and phone numbers. Next, pass selected funeralHomeUrl links into mode byFuneralHome to audit publication volume.

Deliverable: A structured market directory detailing competitor funeral home locations, phone numbers, offered services, and historical listing counts.

Stop condition: Halt execution if funeralHome listings arrive without complete address or servicesOffered details.

What breaks, and how do you design around it?

When targeting cities via mode byCity, always check that the city parameter matches Echovita slug conventions to prevent empty result sets. Because Echovita omits blank keys instead of returning null values, your parsing pipeline must handle variable schema shapes across records. If an obituary lacks memorial details or funeral provider data, plan fallbacks instead of assuming every deceased record links to an established funeral home.

When should you not use Echovita Obituary & Funeral Home Scraper?

Do not use this Actor if your target area falls outside the US, Canada, Australia, or New Zealand. Echovita only monitors listings within these four markets, so investigations in the UK or other European territories will yield zero records. If you specifically need UK funeral director intelligence, use UK Funeral Director Directory Scraper (FuneralGuide) instead. Furthermore, if your investigation requires legacy guestbook comments, condolence messages, or extensive newspaper syndicated obituaries, use Legacy.com Obituary Scraper, which covers the primary US newspaper syndicate archive directly.

What should you check before trusting the output?

• Halt downstream ingestion if recordType is not obituary or funeralHome.
• Flag records where sourceUrl is absent, as this breaks lineage tracing to Echovita.com.
• Verify whether birthDate or deathDate conform to expected ISO-8601 formatting when present.
• Discard socialImageUrl if your application strictly requires genuine verified portrait photography rather than share cards.
• Alert if mode byCity returns zero items consistently, which indicates an invalid or unrecognized city slug.

None of this proves a record is correct. It gives a scheduled Echovita Obituary & Funeral Home Scraper run defined points where it should stop instead of quietly passing bad data downstream.

Frequently asked questions

What is the unit cost of extracting records on the free tier?

Each result costs $0.005, which equals $5.00 per 1,000 results on the free plan. Apify's free plan includes $5.00 of monthly usage with no credit card, covering up to 1,000 results of this Actor before run-start fees and standard platform compute charges.

Does the socialImageUrl field contain a real photograph of the deceased?

Usually not. Echovita auto-generates a social-share card image with the person's name and dates overlaid on a generic template. The field provides a working URL to this share card, but it should not be treated as a verified personal portrait.

Why do some extracted obituary items lack service or funeral home data?

Not every published obituary specifies an organizing funeral home or scheduled memorial service. Echovita omits missing values entirely, meaning records never contain empty strings or null keys when those details were never published on the source listing.

Can I query records from Canadian provinces or Australian states?

Yes. Set the country parameter to ca, au, or nz, and provide the matching regional parameter such as caProvince, auState, or nzRegion instead of the US state field. The underlying query logic functions identically across all four supported regions.

How does the rangeTime filter help control scrape volume?

The rangeTime setting applies server-side date boundaries directly on Echovita. Setting it to 0 limits results to the last 7 days, while 1 covers the last month, allowing recurring runs to isolate new obituaries without paying for older archive records.

Where to go next

When you are ready to run it, open Echovita Obituary & Funeral Home Scraper on Apify; the free plan covers up to 1,000 results a month.

Other Actors we maintain for related data:

• Legacy.com Obituary Scraper: Scrape obituaries from Legacy.com - the largest online obituary archive in the US.
• UK Funeral Director Directory Scraper (FuneralGuide): Scrape funeralguide.co.uk - the UK's largest funeral director directory.
• RoverPass RV Park & Campground Scraper: Scrape RoverPass - a large RV park and campground marketplace covering the US, Canada, Mexico, Australia, New Zealand and the UK.
• Snupit Scraper - South Africa Home Services Directory: Scrape Snupit, South Africa's home-services and business quote directory.
• KOA Campgrounds Scraper: Scrape the KOA campground directory (koa.com) - 500+ Kampgrounds of America parks across the USA and Canada.
• OnTheSnow Scraper: Scrape live ski resort conditions from OnTheSnow - lifts open/total, runs open/total, snowfall, base depth, forecast, and resort status for 300+ resorts across the US, Canada, Australia, New Zealand, Japan, Argentina, and Chile.
• Fyple Scraper - Local Business Directory: Scrape Fyple, a local business directory covering the US, UK, Canada, South Africa, New Zealand, Australia, and Ireland.
• MHVillage Manufactured & Mobile Home Scraper: Scrape MHVillage.com - the largest US manufactured/mobile home marketplace.

Related guides:

• United Real Estate Homes for Sale Scraper: 3 Practical Use Cases
• Expertise.com Local Pro Directory Scraper: 3 Practical Use Cases
• iScrap App Scraper: $0.005 Per Scrap Metal Record (2026)
• Vietnam Business Directory Scraper: 3 Practical Use Cases

Resources

• Actor documentation, input schema, and pricing: verified against the published Actor on 2026-09-26.

• Actor last updated by its maintainers on 2026-07-13.

• Run outcome figures cover the 30 day public window ending 2026-09-26.

• Echovita Obituary & Funeral Home Scraper on Apify