Send policy records
Name of the insured or beneficiary plus city, state, or birth year. Pass your policy number as client_ref.
Check insureds and beneficiaries against 17,565+ funeral-home and newspaper obituary sources. Each match comes with the source obituary, so claims and policy admin can open a file, contact the beneficiary, and document the search.
{
"items": [
{ "first_name": "Harold", "last_name": "Vance",
"birth_year": 1938, "address": { "state": "OH" },
"client_ref": "POL-20418:insured" },
{ "first_name": "Joyce", "last_name": "Vance",
"birth_year": 1941,
"address": { "city": "Dayton", "state": "OH" },
"client_ref": "POL-20418:beneficiary" }
]
}Most insurers learn of a death when a beneficiary files a claim, or later through a periodic Death Master File match. ObituaryMonitor adds a third signal: it checks insureds against published obituaries, which are often posted within days of a death, and returns found, possible_match, or not_found with a confidence band and a link to the source obituary. Teams use it alongside the DMF, not instead of it.
| Who you can check | Insureds, annuitants, and named beneficiaries |
|---|---|
| What you send | First and last name plus city, county, state, or birth year |
| What you get | found / possible_match / not_found, confidence band, source obituary link |
| Volume | Batch of 50 per call, async jobs up to 5,000 rows, Screening Reports for larger files |
| Sources | 17,565+ funeral-home and newspaper sources; no SSDI or death registries |
| Pricing | Custom, by volume; Screening Reports quoted per list |
If no one files, the policy looks in force or quietly lapses. The beneficiary never hears from you, and the proceeds can end up reported as unclaimed property and escheated to the state.
Death Master File access is restricted and its lag varies. A death that is not in your last file, or not in the file at all, stays invisible until the next cycle or a phone call.
An unclaimed property exam or market conduct review wants to see that you looked. A search that left no record of what was checked, when, and against which sources is hard to defend.
A found result with a high confidence band gives your team the date of death, location, and source obituary, so a claim can be opened and beneficiary outreach can start before anyone calls in.
Obituaries often name the surviving family. Family Extraction, through sales, returns the relatives named in a matched obituary with relationship and location where stated, a starting point when contact details on file are stale.
Register aged, paid-up, and non-responsive policies once. If a matching obituary is published months or years later, a signed webhook tells your system, with the policy reference attached.
Send an in-force, lapsed, or acquired block as a CSV and get a Screening Report back: a per-row result with source links, a PDF report, and an audit log. No integration needed.
Screening Reports can include Negative Search Certificates for names with no matching obituary, and API results carry a timestamp and search scope, so your file shows what was checked and when.
found, possible_match, and not_found map to clear queues. Send high-confidence matches straight to claims setup and hold possible matches for an examiner to confirm against the obituary.
Verify an insured or beneficiary when a policy is flagged, a premium stops, or mail comes back. Batch 50 per call, or async jobs up to 5,000 rows.
Register insureds once. We notify your claims or policy admin system by signed webhook if a matching obituary appears later.
Send a policy file once. Get CSV and PDF results with source links, an audit log, and Negative Search Certificates. Quoted per list.
Name of the insured or beneficiary plus city, state, or birth year. Pass your policy number as client_ref.
Funeral-home websites and newspaper obituary sections across 17,565+ sources.
Each match has a confidence band, the matched name, date of death, location, and the source obituary to read.
Open the claim, start beneficiary outreach, or keep the policy on watch. Record the result against the policy.
A life insurance benefit goes unclaimed when the insured dies and no one files. Beneficiaries may not know the policy exists, may have moved, or may assume it lapsed. From the insurer’s side the policy simply goes quiet: premiums stop, mail is returned, and nothing tells the claims team a death has occurred.
Many states expect insurers to search for deceased policyholders on a regular schedule, often using the Social Security Death Master File, and to make a good-faith effort to find beneficiaries before reporting proceeds as unclaimed property. The DMF has known gaps and delays, particularly for recent deaths, so a DMF-only process will miss some insureds and find others late.
Published obituaries fill part of that gap. They are often posted within days of a death, they usually name the surviving family, and they come with a source your examiner can read. Some deaths never get a published obituary, so obituary checks work best as a second signal next to the DMF and your own policy data, not as a replacement for either.
Watches post to your endpoint by signed webhook when a matching obituary appears. The client_ref you sent, such as the policy number, comes back so the event attaches to the right claim or policy.
Async batch jobs up to 5,000 rows finish with a CSV export you can load back against policy records. Idempotency keys make retries on batch calls safe.
Screening Reports return CSV plus a PDF report, an audit log, and Negative Search Certificates you can keep with unclaimed property and exam documentation.
The DMF is built from government death reports, access is restricted, and its lag varies. ObituaryMonitor uses published obituaries from funeral-home websites and newspapers, which are often posted within days and come with a source link. Many insurers run both: the DMF match their process requires, then an obituary check on insureds the DMF did not match.
Yes. Send the beneficiary as a separate row with its own client_ref, such as the policy number plus a role. A deceased primary beneficiary tells you to look to the contingent beneficiary or the estate before you start outreach.
Screen them once with a Screening Report, then register the ones with no match as ongoing watches. If a matching obituary is published later, we notify your system by signed webhook.
Yes. Request a quote, then send the file as a CSV through the secure upload link we send you, with name plus city, county, state, or birth year per row. Do not include Social Security numbers. Screening Reports are quoted per list, based on list size and look-back period.
Each match includes a confidence band, the matched name, date of death, location, and a link to the source obituary. Route found results with a high band to claims setup and have an examiner read the obituary on possible_match results before acting. Strict birth-date matching is available when you send a birth year.
Then we return not_found, which means no matching obituary in our sources. It is not proof of life. Keep the policy on watch, and keep the search record or Negative Search Certificate in the file to show the check was made.
No. ObituaryMonitor is not a consumer reporting agency. Results must not be used to determine eligibility for insurance or any other FCRA-regulated purpose. Use them as evidence for your team to review alongside your own records.
Custom pricing based on your volume and lookup pattern. Screening Reports are quoted per list. Test keys are available on request through sales so you can try the endpoints before a quote.