Death Verification API
Make your first API call
Send POST /api/v1/verify from your code: required fields, an example, response fields, and limits.
Last updated October 8, 2026
Plan: Death Verification API · For: Developers · Time: 5 min read
Before you start
Send a request
- Send a
POSTtohttps://api.obituarymonitor.com/api/v1/verify. - Put your key in the header:
Authorization: Bearer om_live_... - Send a JSON body with
first_name,last_name, and at least one of these:address.state(2-letter code)address.citywithaddress.stateaddress.countywithaddress.statedob.year, ordob.monthwithdob.year
POST https://api.obituarymonitor.com/api/v1/verify
Authorization: Bearer om_live_...
Content-Type: application/json
{
"first_name": "Jordan",
"last_name": "Ellis",
"middle_name": "Lee",
"dob": { "year": 1947 },
"address": { "city": "Dayton", "state": "OH" },
"client_ref": "your-record-123"
}Without a disambiguator, you get 400 invalid_request.
Useful optional fields
| Field | What it does |
|---|---|
middle_name | Identity anchor |
death_date | Helps when you already have a death record |
client_ref | Your own ID, returned in the response |
search_depth | recent, standard, or extended. Leave it out to let the API choose |
lookback_years | How far back to look. Only with extended; capped by your agreement |
require_match | Fields the obituary must confirm |
dob_policy | strict or reject_conflicts |
include_survivors | Include family members named in the obituary. See Batch verification and family extraction |
Read the response
Every successful response includes result, confidence, confidence_band, review_recommended, scoring_reasons, client_ref, search_scope, checked_at, match, and candidates. See Understand results and scores.
Limits and timeouts
- Responses include
X-RateLimit-*andX-Quota-*headers. Slow down when you get close, and retry after a pause onrate_limited. - Deeper searches take longer. With
extendeddepth, a birth year, or family members, a response can take several minutes. Set your HTTP timeout to at least 180 seconds for those calls.
Full field list: the API Reference in the portal, or the public API docs.
Related
Was this article helpful?