Person

Deceased Check API

Deceased Check reports whether an individual is recorded as deceased in the Global Data death check service, from their name and date of birth or date of death. The answer is a single indicator, Y or N, with no record returned.

Search by name and date of birth, by name and date of death, or by both, with the middle name matched exactly only when a date of death is supplied on its own
A single Y or N deceased indicator, suited to batch screening of a customer base before contact

Get API access Talk to us

For developers

After the technical detail?

For the technical detail, go to the API documentation. It holds the request and response schema, the integration guides and the error codes for this endpoint.

Request and response schema
Search modes and sandbox records

View developer documentation

Accounts start in the sandbox. Production keys are issued once the account is approved.

Encrypted in transit and at rest Handled under the Australian Privacy Principles

What the check gives you

Confirming a person is not recorded as deceased before you act on their record

Contacting, paying or onboarding a person who has died is a failure with consequences. Deceased Check takes the name and a date of birth or date of death and reports whether the person appears in the Global Data death check service. Nothing but the indicator comes back, which suits a screening step that needs a yes or no. Where the matched records themselves are needed, ADC Check returns them.

Whether the person is recorded as deceased

The response carries a deceased indicator: Y where the individual was found in the deceased records, N otherwise.

Matching on date of birth

With a name and date of birth, the first name may omit the middle names, so John Smith matches John Andrew Smith. A first and middle name sent together must match in full.

Matching on date of death

With a name and date of death only, the first name must match exactly.

Matching on both dates

With both dates, the search runs on name and date of birth and the date of death is then checked against the results.

Reading the result

What each answer means for the record in front of you

The indicator is the whole answer. The mode you searched in decides how strictly the first name was matched.

Not recorded as deceased

No record matched the name and date supplied in the mode you searched. This is the expected answer for a living customer.

Recorded as deceased

The individual was found in the deceased records. Stop contact and route the record for review.

What it costs

A monthly subscription, drawn down as you run checks

Your subscription is credited to your account each month and each check consumes credits from it. If you go past the included amount, further checks are charged at a per-check rate. The rate depends on the volume you commit to, so the sales team is the fastest way to find where your business lands.

Pay as you go available
No lock-in contract

How billing works

Subscribe monthly, spend it as credits

The monthly subscription arrives as credits on your account.
Each check draws down credits as it runs.
Checks beyond the included credits are billed per check.
Higher monthly volume moves you to a lower rate.

Talk to sales about volume

Related checks

Others in Person

ADC Check returns the matching records themselves, with the state and the ADC reference. Person History runs the death check as part of a wider record.

Banned and Disqualified Person Search API Enhance Record Plus API Marketing Contact Lookup API Person History API Person Report Person Report Result

All Person endpoints

Questions

Questions we get asked about Deceased Check

Do we need a developer to implement this?

Yes. Deceased Check is a REST endpoint that takes a JSON request and returns a JSON indicator, so a developer connects it to your screening or batch process. A sandbox with a deterministic test dataset is provided at no usage cost, so the integration can be built and tested before production keys are issued.

What does our system need to send?

The first name, with optional middle names in the same field, the last name, and the date of birth or the date of death, or both.

What comes back?

A deceased indicator of Y or N, and an API reference for the audit trail. No record is returned.

How is the name matched?

It depends on the dates sent. With a date of birth, middle names may be omitted from the first name field, but a middle name sent must match. With a date of death only, the first name must match exactly.

Where does the data come from?

The Global Data death check service. The reference documentation does not publish a refresh cycle.

Are the names we send stored by Global Data?

Personally identifiable information sent in a request is not stored or retained unless it is needed to process that request. Query data is stripped of PII before it is kept for audit. Data in transit and at rest is encrypted, and retention follows the Australian Privacy Act and the Australian Privacy Principles. Global Data is not a credit bureau and does not create an access footprint on any record.

How many calls can we make?

The API allows 600 requests per minute by default, measured as a rolling average, and returns a 429 response above that rate. A higher limit can be requested through Global Data support with a description of the operational need.

Getting started

The first step to access is a conversation

New accounts begin with sandbox access, and production API keys are issued once the account has been commercially approved.

Get API access Talk to us

Call 03 9948 4089, 9am–5pm AEST Monday to Friday

Encrypted in transit and at rest

Handled under the Australian Privacy Principles

ISO 27001 Certified