Deceased Check API

POST
/deceased_check
LIVE

Checks whether a person is recorded as deceased in the Global Data death check service. You can search by name and date of birth, by name and date of death, or by all three. The name-matching rules shift depending on which combination you send. The response is a simple Y or N indicator that drops easily into KYC pipelines and customer maintenance flows.

calendar_today Request a Demo Contact Sales

Example Request

POST
request.json
key Auth: BearerAuth 
{
  "first_name": "John Andrew",
  "last_name": "Doe",
  "birth_date": "1971-01-23",
  "death_date": "2011-11-03"
}

Request Schema

first_name
Required
string

First name and optional middle names. The matching rules depend on whether you send a DOB, DOD, or both. See the FAQs below.

last_name
Required
string

Last name.

birth_date
Optional
string

Date of birth. Triggers DOB-mode matching, which lets you skip middle names.

death_date
Optional
string

Date of death. If sent on its own (no DOB), the first name has to match exactly including any middle names.

Available Response Data

3 Data Points
01
fact_check

deceased_indicator: Y when matched, otherwise N

02
fingerprint

API reference UUID

03
mail

message

always Ok for a processed request, including no-match results

lock Full API documentation provided after vetting from our compliance team.
By The Numbers

API Data Scale & Coverage tag

Unmatched data depth to power your compliance and verification workflows.

50M+
Phone & Email Records
40M+
Adverse Court Records
2BN+
Australian Universe Records
18M+
Real Estate Records
7M+
Deceased Records
980M+
Social Media & Employment Records
Practical Applications

Technical Use Cases tag

verified_user

KYC and onboarding hygiene

Catch fraudulent account openings against a deceased identity at the point of onboarding. A standard inclusion for AUSTRAC reporting entities.

cleaning_services

Customer database cleansing

Periodically scrub long-tenured customer or member databases so you stop sending marketing, billing and service comms to people who have died.

account_balance

Trust and estate processing

Verify a reported death before releasing trust distributions, insurance payouts or estate funds.

Trust & Assurance

Compliance & Security tag

Enterprise-grade infrastructure audited against the standards your regulators require.

verified_user
ISO 27001 Certified
enhanced_encryption
AES-256 Encryption
public
Australian Data Sovereignty
Integration & Support

Common Questions tag

Everything you need to know about implementation details and compliance infrastructure.

rocket_launch Implementation

How does the name match shift between search modes?

add

With a DOB, you can skip middle names. Searching for “John Smith” with a DOB will match “John Andrew Smith”. With only a DOD, the first name has to match exactly including middles, so “John Smith” will not match “John Andrew Smith”. If you send both DOB and DOD, the search uses the DOB rules and the DOD is checked against the matched record afterwards.

gavel Compliance

Is this the same as the ADC?

add

No. This endpoint runs against the Global Data death check service. For checks against the Australian Death Check register, use adc_check or adc_checks.

help_center General

What does a no-match response look like?

add

You get deceased_indicator: "N" and message: "Ok". A no-match is a successful response, not an error.

Try it Live

API Testing Sandbox tag

Test the Deceased Check API directly in your browser with live mock data and see instant results.

rocket_launch Request Sandbox Access

Access to live sandbox environments requires manual approval from our compliance team.

(03) 9948 4089
Request a Demo
BACK TO TOP