County Feed API

County Feed remembers where you left off. Each pull returns only new notices for counties you enroll in the developer portal. This is a feed of recent deaths — not a person lookup or death-registry API. An empty result means nothing new has arrived.

Endpoint

GET /api/v1/county-feed/notices

Production URL: https://api.obituarymonitor.com/api/v1/county-feed/notices

Authenticate with Authorization: Bearer om_live_YOUR_KEY. Counties and delivery options are configured in the developer dashboard.

How it works

Call GET /api/v1/county-feed/notices with your API key. County Feed remembers your position automatically. Poll once or twice daily; if data is empty, your feed is up to date.

Optional limit (1–1000, default 500). Date-range and position parameters are under Advanced below — most customers never need them.

Example request

curl -sS \
  -H "Authorization: Bearer om_live_YOUR_KEY" \
  "https://api.obituarymonitor.com/api/v1/county-feed/notices"

GET https://api.obituarymonitor.com/api/v1/county-feed/notices
Authorization: Bearer om_live_YOUR_KEY

Example response

{
  "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" }
  ]
}

Extract heirs (portal)

After each successful pull, open the developer County Feed dashboard. Under Recent pulls (24h), re-download the JSON or click Extract heirs (when enabled). Progress and CSV download appear on the same row. Pulls larger than 100 notices extract the first 100 only.

Advanced: include_survivors

For automations only. Admin must enable the feature. Pass include_survivors=true (limit ≤ 100). Notices return immediately; poll the job or download the enriched CSV when complete. Prefer the portal Extract heirs flow for interactive use.

GET https://api.obituarymonitor.com/api/v1/county-feed/notices?limit=25
Authorization: Bearer om_live_YOUR_KEY

{
  "data": [
    {
      "id": "fh-88421",
      "full_name": "Margaret Ann Henderson",
      "survivors": [
        { "name": "James Henderson", "relationship": "son", "degree_of_kinship": "1st", "location": null }
      ],
      "survivors_status": "ok",
      "survivors_source": "snippet"
    }
  ],
  "pagination": {
    "limit": 25,
    "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" }
  ]
}

Retrieve notices by date

Optional from and to (ISO-8601), or lookback=24h, return notices in a past window. This does not change where your normal feed left off.

Advanced: feed position

Responses may include pagination.next_cursor and pagination.next_since. You do not need these for the default bare GET. Pass cursor= only if you manage position yourself (does not move the server-managed feed position). Legacy since= remains supported for existing integrations. When has_more is true, continue with cursor=next_cursor (or legacy since=next_since) until the page is drained.

Response fields

Field	Description
id	Stable notice identifier
full_name	Display name from the source
first_name	Parsed first name when available
middle_name	Parsed middle name or initial when available
last_name	Parsed last name when available
date_of_death	YYYY-MM-DD when available
county	County name
state	Two-letter state code
city	City when available
obituary_url	Link to the obituary listing
funeral_home_name	Funeral home or newspaper publisher
source_type	funeral_home or newspaper
indexed_at	ISO timestamp when we first captured the notice
text_snippet	Short obituary excerpt when available
survivors_text	Best-effort survivors/family excerpt when available
survivors_job	Present only when include_survivors=true (advanced automation) — async enrichment job metadata

Coverage rules

Notices must pass recency filters:

Date of death within the last 30 days
Date of death within 14 days of first capture (excludes historical backfill)

Absence from the feed is not proof of life. Sources include funeral homes and newspapers we monitor daily in enrolled counties.

Delivery alternatives

API pull — poll on your schedule (this endpoint).

Email digest — daily or weekly summary to configured recipients.

CSV archive — daily file of the previous calendar day (America/Chicago), downloadable from the dashboard for 30 days. Estate Property Match accounts also get property address and related listing/map URL columns.

Error codes

Code	HTTP	Meaning
unauthorized	401	Missing, invalid, or revoked API key.
key_expired	401	The API key has passed its expiration date.
county_feed_access_required	403	County feed is not enabled on this account.
delivery_mode_email_only	403	API pull is disabled — account is configured for email digest delivery only.
survivors_not_enabled	403	Structured survivors enrichment is not enabled for this account.
survivors_limit_exceeded	400	include_survivors=true requires limit <= 100.
internal_error	500	Unexpected server error.

Errors return { "error": { "code", "message" } }. An empty data array with HTTP 200 is not an error.