Verify Deceased Individuals Using Obituary Data
Death Verification API
Verify whether an individual is deceased using obituary and funeral home data sources.
ObituaryMonitor's Death Verification API helps businesses identify and verify deceased individuals using obituary records, funeral home websites, memorial sites, and related public death-notice sources.
Built for probate, estate administration, insurance, compliance, skip tracing, legal, and investigative workflows.
Built on one of the largest actively monitored funeral-home coverage networks in the United States
ObituaryMonitor continuously monitors thousands of funeral home and obituary sources—giving the Death Verification API access to obituary and death-notice data that manual searches and generic databases often miss.
Thousands of monitored sources
Daily source refreshes
Source-attributed results
Business API access
How It Works
Submit identifying information about an individual. The API searches available obituary and death-notice sources and returns the strongest available match.
Supported inputs
- First name
- Last name
- Date of birth month/year, when available
- City
- State
- Address, optional
Sample API Workflow
How teams typically integrate death verification into an existing CRM or case system.
Your system submits identifiers; the API returns structured results your team can route into review queues, case files, or compliance workflows.
Example API Response
Responses include verification status, confidence scoring, and source attribution from available obituary and death-notice matches—in a format your team can review or parse.
Visual result
- Name
- John Smith
- Confidence
- 98%
- Date of Death
- March 17, 2025
- City
- Dallas, TX
- Source
- Funeral Home Obituary
- Evidence
- View obituary
Example match — actual results vary by identifiers and source coverage.
API payload
{
"status": "verified_deceased",
"confidence": 0.98,
"full_name": "John Smith",
"date_of_death": "2025-03-17",
"city": "Dallas",
"state": "TX",
"obituary_url": "https://example.com/obituaries/john-smith",
"funeral_home": "Example Funeral Home",
"source_type": "funeral_home_obituary"
}Structured JSON for CRM, case management, and compliance system integration.
See full API documentation at /docs/api.
What We Return
Depending on available source data:
Use Cases
Programmatic death verification for teams that need obituary-based checks inside internal systems and workflows.
Probate & estate administration
Confirm decedent status before creditor notices, asset transfers, and estate administration workflows.
Debt collection & asset recovery
Verify debtor deaths using obituary sources before account handling, recovery, and compliance review.
Insurance & benefits
Support claims and beneficiary workflows with obituary-based verification and source attribution.
Skip tracing
Identify deceased subjects in skip trace and locate workflows using available obituary and death-notice sources.
Legal and investigative workflows
Integrate death verification into case management, diligence, and investigative review processes.
Genealogy and research
Support research teams with programmatic obituary lookup where historical source coverage is available.
Common Death Verification Use Cases
Businesses use a death verification API when they need to confirm whether someone has died inside an existing workflow—not as a one-off web search. Probate and estate administration teams often verify decedent status before creditor notices, beneficiary outreach, or asset transfers. An obituary-based API searches available funeral home websites, memorial pages, and related death-notice sources, then returns a match with confidence scoring and a source URL teams can reference in diligence files.
Probate, estate administration, and legal workflows
Estate attorneys and trust administrators frequently need to verify deaths across a portfolio of names tied to cases, trusts, or dormant accounts. Manual obituary searches do not scale when matter volume grows or when subjects are spread across states. A death verification API lets firms submit identifiers—name, date of birth, city, state, and optional address—and receive structured results they can route into case management, compliance review, or internal audit systems. Results are based on available obituary sources; a not-found response means no matching obituary was found in the searched sources, not proof the person is alive.
Insurance claims, skip tracing, and compliance
Insurance and benefits teams use obituary verification to support claims handling and beneficiary workflows without relying on incomplete or delayed official records alone. Skip tracing and debt collection operations use the same capability to identify deceased subjects before further contact attempts, reducing compliance risk and wasted field effort. Compliance and investigations groups benefit from source attribution: each API response can include the obituary URL, funeral home name, and supporting evidence snippet so reviewers understand where a match came from and how strongly identifiers aligned.
ObituaryMonitor's Death Verification API is designed for these operational use cases— programmatic lookup with confidence scoring, not consumer obituary alerts. Teams evaluating API access can also request a demo to review sample results, discuss volume and pricing, and walk through integration options before credentials are issued.
API Pricing & Volume
Plans are available for low-volume and enterprise verification workloads. Pricing depends on monthly verification volume, search depth, and integration requirements—not a one-size-fits-all enterprise minimum.
API access is not self-service checkout today. Submit a request or schedule a demo and our team will share options aligned to your use case and expected volume.
Why ObituaryMonitor
Built for business teams that need obituary-based verification with transparent source attribution—not a consumer alert product.
- Obituary-based verification with source attribution
- Actively monitored funeral home and obituary sources
- API access for internal business workflows
- Historical obituary search where available
- Confidence scoring based on available identifiers
Matching Confidence
Each response includes a confidence score based on identifying information such as name similarity, DOB alignment, geography, address alignment, and source quality.
A not-found result means no matching obituary was found in the searched sources. It is not proof the person is alive.
Request API Access
Tell us about your workflow and expected verification volume. Our team will follow up with API access options and onboarding details.
- Response within one business day
- Business and API access only—no self-service checkout yet
- Prefer email? sales@obituarymonitor.com
Not ready for API credentials? Request a demo to review sample results, discuss your use case, and learn about pricing before committing.