ObituaryMonitorObituaryMonitor
Business API access

Obituary Data API for Business Workflows

Access daily obituary feeds by county or enrich existing records with verified obituary intelligence. Monitor new deaths, match existing names, and integrate structured obituary data directly into your workflow.

View API Docs

Two Ways to Use ObituaryMonitor

Push-based daily feeds for county monitoring, or pull-based matching when you already have records to enrich.

Monitor New Deaths by County

Select the counties or regions you care about and receive structured obituary data as new notices are discovered. Ideal for teams that need a daily feed of new deaths without starting from an existing record list.

  • County and region-based monitoring
  • Daily obituary feed delivery
  • Name, location, dates, source URL, and funeral home data
  • API delivery or scheduled reports
  • Useful for lead generation, estate workflows, claims, and professional research

“Send us every new obituary found in Jefferson County each morning.”

Enrich Existing Records

Submit names, death records, case lists, or research files and match them against obituary sources. Ideal for teams that already have names, counties, dates of death, or other identifiers and need source-attributed obituary evidence.

  • Batch uploads or API lookups
  • Match using name, county, state, date of death, DOB, city, aliases, or other identifiers
  • Confidence-scored results
  • Source attribution and obituary URLs
  • Optional batch survivor extraction

“Check these 10,000 records and return matching obituaries.”

Broad obituary source coverage with a continuously updated database

Funeral home listings, newspaper indexes, and stored obituary inventory — refreshed daily. Source-attributed results for feeds and enrichment; extended search available when enriching older records.

Daily county feed delivery

Record matching & enrichment

Source-attributed results

Extended search for older records

Death Data Coverage by State

Explore continuously updated death and obituary data across published states. Each page shows recent activity, geographic coverage, monitored sources, available record fields, and API delivery options.

County feed workflow

Daily County Obituary Feeds

For customers who need ongoing county-level monitoring, ObituaryMonitor can provide a daily feed of newly discovered obituary notices. Customers can select target counties or regions and receive structured data through API delivery or scheduled reports.

  • Useful when the customer does not already have records
  • Supports county-based prospecting and monitoring
  • Best for recent deaths and daily discovery
  • Can be combined with survivor extraction or downstream enrichment where appropriate
Select counties
Monitor sources daily
Receive new notices
Route to your workflow
County feed API request
GET https://api.obituarymonitor.com/api/v1/county-feed/notices
Authorization: Bearer om_live_YOUR_KEY
County feed response (sample)
{
  "data": [
    {
      "id": "fh-88421",
      "full_name": "Margaret Ann Henderson",
      "first_name": "Margaret",
      "middle_name": "Ann",
      "last_name": "Henderson",
      "date_of_death": "2026-05-12",
      "county": "Jefferson",
      "state": "AL",
      "city": "Birmingham",
      "obituary_url": "https://example.com/obit/margaret-henderson",
      "funeral_home_name": "Example Funeral Home",
      "source_type": "funeral_home",
      "indexed_at": "2026-05-13T08:22:00.000Z",
      "text_snippet": "Margaret Ann Henderson, 84, of Birmingham, passed away on May 12, 2026. She is survived by her son James Henderson and daughter Sarah Henderson.",
      "survivors_text": "her son James Henderson and daughter Sarah Henderson",
      "survivors": [
        { "name": "James Henderson", "relationship": "son", "degree_of_kinship": "1st", "location": null },
        { "name": "Sarah Henderson", "relationship": "daughter", "degree_of_kinship": "1st", "location": null }
      ],
      "survivors_status": "ok",
      "survivors_source": "snippet",
      "property_intelligence": {
        "product": "estate_property_intelligence",
        "property": {
          "address": "100 Example Ave, Birmingham, AL 35203",
          "parcel_id": "01-23-45-678"
        }
      },
      "property_match": true,
      "property_address": "100 Example Ave, Birmingham, AL 35203",
      "property_parcel_id": "01-23-45-678"
    }
  ],
  "pagination": {
    "limit": 500,
    "has_more": false,
    "next_since": "2026-05-13T08:22:00.000Z",
    "next_cursor": "v1.eyJrIjoibGl2ZSIsInQiOiIyMDI2LTA1LTEzVDA4OjIyOjAwLjAwMFoiLCJpZCI6ImZoLTg4NDIxIn0"
  },
  "counties": [
    { "state": "AL", "county_slug": "jefferson-county-al", "county_name": "Jefferson" }
  ]
}
Enrich existing records

Built for Batch Research Workflows

Already have county death records, case lists, or names to research? Upload or submit batches of names with available identifiers such as county, state, date of death, date of birth, city, or known aliases. Our system searches our obituary database first, then uses extended search when needed for older or harder-to-find records.

Record enrichment uses a separate product — POST /api/v1/verify (Death Verification API). If you only need daily county obituary notices, see Daily County Obituary Feeds above. Full verify schema: /docs/api/verify

Submit names or death records
Match obituary sources
Confidence-scored results
Review source attribution
Survivor extraction (optional)

Recent vs. Historical Coverage

Our strongest coverage is recent and newly published obituary data from the sources we monitor daily. Daily feed monitoring is optimized for current discovery. For older lookbacks, including 10+ year searches, historical coverage may be less complete. When enriching existing records, the system can perform extended search when a match is not found in our database — best-effort historical discovery, not guaranteed coverage for every record.

Beta · separate batch workflow

Optional Batch Survivor Extraction

After obituary matches are identified, ObituaryMonitor can process matched obituaries in a separate batch workflow and extract family members mentioned in the obituary when available. Survivor extraction is separate from the real-time API — it runs after matches are confirmed and surfaces survivor information as potential heir research leads.

Because obituary formats vary by funeral home and publisher, this is a best-effort beta capability and may not return structured family information for every obituary.

Not legal heir identification

Survivor extraction surfaces family members mentioned in obituary text. It does not identify legal heirs, guarantee heir detection, or produce complete family trees.

Batch survivor extraction (beta sample)
{
  "obituary_url": "https://example.com/obit/robert-martinez-austin",
  "client_ref": "case-tx-88421",
  "best_effort": true,
  "survivors_beta": true,
  "survivors": [
    {
      "name": "Maria Martinez",
      "relationship": "spouse",
      "degree_of_kinship": "1st Degree"
    },
    {
      "name": "Daniel Martinez",
      "relationship": "son",
      "degree_of_kinship": "1st Degree"
    }
  ],
  "survivors_status": "ok",
  "survivors_source": "scraped",
  "note": "Potential heir research leads — family members mentioned in the obituary."
}

Sample Record Enrichment API

Typical county-based research record mapped to POST /api/v1/verify. County feeds use GET /api/v1/county-feed/notices — see the Daily County Obituary Feeds section above.

Typical batch / case file record
{
  "first_name": "Robert",
  "last_name": "Martinez",
  "dob": { "month": 8, "year": 1941 },
  "death_date": "2014-08-22",
  "address": { "state": "TX", "county": "Travis", "city": "Austin" },
  "client_ref": "case-tx-88421"
}
Verify API request
POST https://api.obituarymonitor.com/api/v1/verify
Authorization: Bearer om_live_YOUR_KEY
Content-Type: application/json

{
  "first_name": "Robert",
  "last_name": "Martinez",
  "dob": { "month": 8, "year": 1941 },
  "death_date": "2014-08-22",
  "address": { "state": "TX", "county": "Travis", "city": "Austin" },
  "search_depth": "extended",
  "lookback_years": 10,
  "client_ref": "case-tx-88421"
}
Match found
91% confidence
Matched name
Robert J. Martinez
Date of death
August 22, 2014
Location
Austin, Travis County, TX
Source
Funeral home obituary (stored)
found response
{
  "result": "found",
  "confidence": 0.91,
  "confidence_band": "high",
  "review_recommended": false,
  "not_proof_of_life": false,
  "client_ref": "case-tx-88421",
  "interpretation": "A likely obituary match was found.",
  "scoring_reasons": [
    "Stored index candidate",
    "County match: Travis",
    "State match (TX)",
    "Death date corroborated"
  ],
  "match": {
    "matched_name": "Robert J. Martinez",
    "death_date": "2014-08-22",
    "location": "Austin, Travis County, TX",
    "obituary_url": "https://example.com/obit/robert-martinez-austin",
    "source": "Example Funeral Home",
    "source_trust": "stored",
    "evidence": {
      "name_match": "exact",
      "location_match": "county_state",
      "dob_match": "month_year"
    },
    "scoring_reasons": [
      "Stored index candidate",
      "County match: Travis",
      "State match (TX)"
    ]
  }
}
not_found response
{
  "result": "not_found",
  "confidence": 0,
  "confidence_band": "none",
  "not_proof_of_life": true,
  "match": null,
  "interpretation": "No matching obituary was found in the searched sources for the provided identifiers. This is not proof the person is alive.",
  "scoring_reasons": ["no_qualifying_candidates"],
  "client_ref": "case-tx-88421"
}

Important disclaimer

A not_found result is not proof the person is alive. Responses include not_proof_of_life: true.

View API Docs

What We Return

Core obituary feed fields

Daily county feed delivery

Full name
Date of death when available
Age or date of birth when available
City, county, state when available
Funeral home or publisher
Obituary URL
Source attribution
Discovery date

Record matching / enrichment fields

Batch and API lookups

Match status (found, possible_match, not_found)
Confidence score & match reasons
Input identifiers used
Obituary evidence & source URL
Matched name & date of death
Geography when available
Optional survivor extraction results
not_proof_of_life on not_found results

Use Cases

County feed use cases

Push-based daily monitoring

County obituary monitoring

Receive daily notices from selected counties without starting from an existing record list.

Estate planning lead discovery

Surface newly published obituaries in target geographies for outreach and intake workflows.

Funeral home & newspaper intelligence

Track obituary activity across monitored funeral home and newspaper sources by county.

Local claims & benefits monitoring

Watch counties for new deaths relevant to regional claims, benefits, or portfolio review.

Professional research feeds

Ingest county-scoped notice streams into CRM, case systems, or internal research queues.

Record enrichment use cases

Pull-based matching from existing data

Surplus funds & unclaimed property recovery

Match county death records and case lists to obituary sources to prioritize downstream research.

Probate & estate administration

Verify decedent deaths from case files and return source-attributed obituary evidence.

Heir research

Confirm deaths and optionally extract family members mentioned in obituaries as potential heir research leads.

Skip tracing & due diligence

Review confidence-scored matches and document obituary evidence before further action.

Insurance, healthcare & financial workflows

Enrich portfolio or claims records with obituary-based verification where geography is known.

Pricing & Pilot Access

Production pricing depends on workflow type, monthly query volume, number of counties monitored, batch requirements, and whether survivor extraction is enabled.

Pilot programs are available for qualified business workflows:

  • County feed pilots
  • API lookup pilots
  • Batch enrichment pilots

Contact us for a quote based on your counties, lookup pattern, and enrichment needs.

View API Docs

Why ObituaryMonitor

Professional obituary data for B2B workflows — daily county feeds and record enrichment in one platform, not consumer obituary alerts.

  • Daily county obituary feeds for push-based monitoring
  • Record matching and enrichment for teams with existing data
  • Broad obituary source coverage with a continuously updated database
  • Source-attributed results with confidence scoring
  • Optional beta survivor extraction for potential heir research leads

Have a county monitoring workflow?

Request Illinois County Feed Trial

Start a County Feed trial for Illinois. Receive newly detected death and obituary records through the web portal, email digests, API, or CSV — whichever fits your workflow.

Request context: IL · illinois county feed

Business access only. Privacy policy.

Frequently Asked Questions