Add the subject at intake
Name plus city, state, or birth year, with your case reference. Do it before anyone is scheduled for the field.
Check subjects against 17,565+ funeral-home and newspaper obituary sources. Each match comes with the obituary link for your case file, the family it names for your next step, and ongoing watches for files that stay open.
{
"client_ref": "CASE-3391",
"result": "found",
"confidence_band": "high",
"match": {
"full_name": "Raymond L. Petrakis",
"death_date": "2026-08-14",
"location": "Toledo, OH",
"source_url": "https://example.com/obituaries/raymond-petrakis"
}
}Most start with the obituary. A published obituary usually appears within days, states where the person lived, and names the surviving family, which is enough to tie it to your subject and decide the next step. ObituaryMonitor checks a subject's name plus a location or birth year against funeral-home and newspaper obituaries and returns found, possible_match, or not_found with a confidence band and the source link. It supports your review; it is not a death certificate.
| Input | First and last name plus city, county, state, or birth year, and your case reference |
|---|---|
| Output | found / possible_match / not_found, confidence band, obituary source link |
| Sources | 17,565+ funeral-home and newspaper obituary sources |
| Next steps | Family Extraction: relatives named in the obituary, with relationship and location where stated |
| Not included | Phone numbers, emails, addresses, or other skip-trace contact data |
Surveillance hours, mileage, and database pulls spent locating someone whose obituary was already online. The client still gets a bill and no usable result.
Attempting service or an interview at a house in the middle of a funeral week is the kind of contact that turns into a complaint and costs you the referral.
When a case pauses for budget or goes cold, nobody is re-checking. A regional obituary posted months later sits unread until the client asks why the file never moved.
Run the subject before surveillance, a field visit, or an attempt at service. A found result with a high confidence band lets you stop or redirect the file before the hours are spent.
Every match carries the obituary link, so you can show the client exactly why the subject was marked deceased instead of reporting that they could not be located.
Family Extraction lists the relatives named in a matched obituary, with relationship and location where stated. On estate, heir, and asset files, that is often the next set of people to research.
Register a subject once and we notify your system by signed webhook if a matching obituary appears later, whether the file is active, paused, or waiting on a client.
Batch up to 50 subjects per call, or send async jobs up to 5,000 rows. Your case reference rides along with each row so results land back on the right file.
Results with a confidence band and possible_match status tell you which hits to accept and which need a closer look at location, age, and family before you act.
Send a name and a location or birth year with your case reference. Get found, possible_match, or not_found with a confidence band and the obituary link. Batch 50, or async jobs up to 5,000 rows.
Register a subject once. If a matching obituary is published later, we notify your system by signed webhook, so dormant and paused cases still surface news.
Through sales: the relatives named in a matching obituary, with relationship and location where stated. A starting point for your next step, not contact data or legal heir findings.
Name plus city, state, or birth year, with your case reference. Do it before anyone is scheduled for the field.
Funeral-home websites and newspaper obituary sections, matched on name, location, and birth year where given.
Read the obituary at its source. Confirm location, age, and named family against what is in your file.
Close or reassign the file, note the source in your report, or move to the relatives named in the obituary. Leave a watch on anything still open.
Clients and attorneys rarely accept "we could not find them" on its own. A defensible file shows what was checked, when, and what was found. When a subject has died, the strongest working evidence short of a certified record is a published obituary that matches on name, location, and age and names family you can tie back to the subject.
Government death files are useful but are not built for active casework. Access is restricted, there is no source document to show a client, and recent deaths can take time to appear. Obituaries are often published within days, link to a page anyone can read, and name the people closest to the subject. Many investigators use both.
Keep the limits straight in the report. A not_found means no matching obituary was found in our sources; it is not proof the subject is alive, since some deaths never get an obituary. Relatives named in an obituary are starting points for further research, not a legal determination of heirs. Where a court or agency requires a death certificate, obtain one from the vital records office.
For a one-time file, such as an inherited caseload or an estate heir list, a Screening Report returns results with source links as CSV plus a PDF report, an audit log, and Negative Search Certificates documenting names where no matching obituary was found.
Call the API at intake and write the result, confidence band, and obituary link to the subject record. Your client_ref keeps every result tied to the right case.
Watches post to your endpoint by signed webhook when a match appears, so an investigator or supervisor can review it the same day instead of on the next manual sweep.
Attach the obituary link and the check date to the file. For one-time lists, Screening Reports add a PDF report and audit log you can hand to the client.
You can document strong evidence of it. A matching obituary with the subject's location, age, and named family is what most investigators use to close or redirect a file. It is not a death certificate; if a court or agency needs one, request it from vital records.
Yes. Family Extraction, available through sales, lists the relatives named in a matched obituary with relationship and location where stated. They are a starting point for your next step, not a legal determination of heirs or next of kin.
No. We return obituary evidence and the people it names. We do not supply phone numbers, emails, addresses, or other skip-trace contact data; use your existing locate tools for that step.
Save the check date, the inputs you sent, the result, and the obituary source link with the file. For a one-time list, a Screening Report adds a PDF report, an audit log, and Negative Search Certificates for names with no matching obituary.
Send a location or birth year with the name. Each result has a confidence band, and uncertain hits come back as possible_match so you can compare location, age, and named family before acting.
Then the result is not_found, which means no matching obituary in our sources. It is not proof the subject is alive. Some deaths never get an obituary, so keep a watch on open files and check other records where the case requires it.
Yes. Register a subject once and we notify your system by signed webhook if a matching obituary appears later. The watch keeps running while the file is inactive.
No. ObituaryMonitor is not a consumer reporting agency, and results must not be used for FCRA-regulated decisions such as eligibility for credit, insurance, employment, or housing.