ADC Check API

POST
/adc_check
LIVE

Searches an individual against the Australian Death Check (ADC), the official death register data. You get any matching records back, including the exact date of death where available (or a date range where it's not), the state the death was registered in, and the ADC reference number. Use this when your compliance posture wants verification against the official register rather than a proprietary dataset.

Example Request

POST
request.json
key Auth: BearerAuth
{
  "first_name": "John",
  "middle_name": "Andrew",
  "last_name": "Smith",
  "birth_date": "1998-03-21"
}

Request Schema

first_name
Required
string

First name. Has to match exactly.

middle_name
Optional
string

Optional. Middle names can match partially.

last_name
Required
string

Last name. Has to match exactly.

birth_date
Required
string

Date of birth in YYYY-MM-DD.

Available Response Data

8 Data Points
01
fact_check

Matched first name including any middle names

02
fact_check

Matched last name

03
schedule

Date of birth from the record

04
schedule

Date of death where available

05
schedule

Date of death range where only an approximate window is recorded

06
monitor_heart

State of registration

ACT, NSW, NT, QLD, SA, TAS, VIC or WA

07
fingerprint

ADC reference number

08
fact_check

name_match: either exact or partial

partial means the last name is the same but the first or middle names differ

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

account_balance

Register checks for high-risk decisions

Where the regulator or your auditor wants verification against the official Australian Death Check rather than a proprietary dataset. Common for life insurance payouts, super releases and large estate transfers.

payments

Welfare and benefits fraud

Check recipients of pensions, allowances and beneficiary disbursements against the ADC to stop payments going to a stolen identity.

enhanced_encryption

Enhanced due diligence step

An ADC check sits well as part of EDD on higher-risk products like remittance, gambling or correspondent banking.

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 forgiving is the name match?

add

First and last names have to match exactly. Middle names can match partially. So for an ADC record stored as “John Henry Smith”, a search for “John Henry Smith”, “John Henry Peter Smith”, “John Peter Smith” or just “John Smith” will all return a match. The name_match field tells you whether it was exact or partial.

gavel Compliance

What's the difference between this and deceased_check?

add

deceased_check runs against the GlobalData proprietary service. This one runs against the official Australian Death Check register. A lot of high-risk workflows want both checks done.

help_center General

What if the exact date of death isn't known?

add

Sometimes the ADC has a date range rather than an exact date. In that case date_of_death will be null and date_of_death_range will hold a free-text description, for example “Between 31/12/2018 and 2/2/2019”.

Try it Live

API Testing Sandbox tag

Test the ADC 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.