Developers

A clean REST API for deceased verification

Verify a single identity in real time or submit large batches. Predictable JSON, clear status codes and a confidence score on every match. Get running in an afternoon.

Request API access View pricing

Real time

Single verification returns in milliseconds so you can screen inside an application flow.

Batch ready

Submit up to 1,000 records per request or upload a file for very large jobs.

Confidence scored

Every match includes a confidence score so you can set your own decision thresholds.

Endpoints

Core API endpoints

POST	`/v1/verify`	Verify a single identity in real time.
POST	`/v1/verify/batch`	Verify up to 1,000 identities per request.
GET	`/v1/jobs/{id}`	Check the status of an uploaded batch job.
GET	`/v1/results/{id}`	Download the results of a completed job.

Authentication

Authenticate with a bearer token

Every request uses your secret API key as a bearer token. Keys are issued per environment so you can keep test and production traffic separate. Never expose a secret key in client side code.

Authorization header

Authorization: Bearer YOUR_API_KEY

Verify a single identity

Request and response

Request

curl -X POST https://api.verifydeceased.com/v1/verify \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "first_name": "Jane",
    "last_name": "Doe",
    "date_of_birth": "1948-03-12",
    "ssn": "123-45-6789",
    "address": "123 Main St, Alta Loma, CA 91701"
  }'

Response

{
  "status": "match",
  "confidence": 0.98,
  "record": {
    "first_name": "Jane",
    "last_name": "Doe",
    "date_of_death": "2024-11-03",
    "age_at_death": 76,
    "last_known_address": "123 Main St, Alta Loma, CA 91701",
    "state": "CA"
  },
  "request_id": "req_9f2c1a7b"
}

Request fields

What to send

Name is required. The more identifiers you send, the higher the match confidence.

Field	Type	Requirement	Note
`first_name`	string	Required	Legal first name
`last_name`	string	Required	Legal last name
`date_of_birth`	string	Recommended	Format YYYY-MM-DD
`ssn`	string	Optional	Improves match confidence
`address`	string	Optional	Last known address

Response status

Three possible outcomes

Use the status and confidence score together to decide whether to accept, decline or route a record to manual review.

matchA confirmed deceased record was found.
no_matchNo deceased record was found for this identity.
reviewA partial match was found and needs manual review.

Batch request

curl -X POST https://api.verifydeceased.com/v1/verify/batch \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "records": [
      { "first_name": "Jane", "last_name": "Doe", "date_of_birth": "1948-03-12" },
      { "first_name": "John", "last_name": "Smith", "date_of_birth": "1952-07-22" }
    ]
  }'

Rate limits

Generous default limits with room to grow. Enterprise plans get dedicated throughput.

Idempotency

Send an idempotency key to safely retry requests without creating duplicate charges.

Webhooks

Get notified when a large batch job finishes instead of polling for the result.

Ready to integrate?

Request an API key and start verifying against fresh death data today.

Request API access See how it works