Skip to content
New

Person Report API and New Zealand identity checks are now live.

See what's newarrow_forward
WatchEyeOnboarding & monitoring

Customer onboarding, screening and ongoing monitoring in one system, with real-time KYC and KYB alerts when a customer's risk changes.

Visit WatchEyearrow_forwardcheck_circleIncluded in the Global Data Portal
IDFEX ID CheckIdentity verification

One-to-one identity, document and data checks against the DVS and Australian data sources, run from the Portal or by API.

Visit IDFEX ID Checkarrow_forwardcheck_circleIncluded in the Global Data Portal
ID PassSelf-service verification

Customers verify their own identity and biometrics from a link on their phone. The result comes back to you, and they keep control of their data.

Visit ID Passarrow_forwardcheck_circleIncluded in the Global Data Portal
InsiightData quality

Verifies, corrects and enriches customer records so they stay accurate — one at a time or across your whole database.

Visit Insiightarrow_forwardcheck_circleIncluded in the Global Data Portal
Australian Death CheckDeceased data

The official national death data source. Match your records against it to find and remove deceased individuals.

Visit Australian Death Checkarrow_forwardcheck_circleIncluded in the Global Data Portal
QuesterMarketing lists

Build targeted, privacy-compliant Australian marketing lists with smart filters. Pay only for the records you download.

Visit Questerarrow_forwardcheck_circleIncluded in the Global Data Portal
verified_userVerify identities7 solutions

Confirm a person or business is who they claim to be: government IDs, biometrics, business registries and employment checks against authoritative Australian sources.

All solutionsarrow_forwardcheck_circleAvailable in the Portal and by API
policy_alertStay compliant6 solutions

Meet AUSTRAC obligations and understand customer risk: screening, risk assessment, fraud controls and investigation tools with evidence recorded for each check.

All solutionsarrow_forwardcheck_circleAvailable in the Portal and by API
databaseImprove your data3 solutions

Keep customer records accurate and put them to work: correct and enrich existing data, unify it into a single view, or build compliant marketing lists from opted-in records.

All solutionsarrow_forwardcheck_circleAvailable in the Portal and by API
monitoringWatchEye API14 categories

The WatchEye API gives programmatic access to everything in WatchEye: PEP and sanctions screening, identity checks, IDPass verifications, monitoring programs, events and reports.

View allarrow_forwardcheck_circleSandbox environment for integration testing
policyAML & screening6 use cases

Obligations under the AML/CTF Act, from screening at onboarding through to ongoing monitoring — with the evidence for each check recorded.

All use casesarrow_forwardcheck_circleMapped to the products and data that cover it
how_to_regOnboarding & identity3 use cases

Verifying who a customer, employee or account holder is — at sign-up and during ongoing checks — against authoritative Australian sources.

All use casesarrow_forwardcheck_circleMapped to the products and data that cover it
databaseData & enrichment4 use cases

Keeping customer records accurate, current and complete: validate contact detail, fill the gaps, locate people and remove deceased records.

All use casesarrow_forwardcheck_circleMapped to the products and data that cover it
Global Data
Portalarrow_forward
Productsexpand_more
Solutionsexpand_more
Use casesexpand_more
Dataexpand_more
APIarrow_forwardIndustriesarrow_forwardResourcesarrow_forwardAboutarrow_forwardContactarrow_forward Request a Demo
Talk to the team

9am–5pm AEST, Monday to Friday.

call03 9948 4089
Person

Person History API

Person History returns the historical records held for an individual in the Global Data Universe. Each matched record carries the person's addresses, phone numbers and email addresses with the dates they were first and last seen, and a deceased flag from the Australian Death Check.

  • Every matched record carries the address, phones and emails with first-seen and last-seen dates, so a contact trail can be read in order
  • Each match is checked against the Australian Death Check when the name, date of birth and state are available
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
  • Minimum search requirements and sandbox records
View developer documentation

Endpoints that return personal information require a privacy policy and PII handling processes before access is granted.

Encrypted in transit and at rest Handled under the Australian Privacy Principles
What the check gives you

Seeing where a person has been, and how to reach them, over time

A single current address rarely tells the whole story when a customer needs to be traced, re-contacted or reconciled against an older record. Person History takes a name and one other identifier and returns the records held for that person in the Global Data Universe, each with its dates. The result is a dated trail of addresses and contact details rather than a single snapshot.

The addresses on record, with dates

Each match carries the street address, suburb, state and postcode, with the date the address record was first seen and the date it was last seen.

The phones and emails on record, with dates

Each match carries the phone numbers and email addresses associated with the person, each with its own first-seen and last-seen dates.

Whether the person is recorded as deceased

Each match carries a Y or N from the Australian Death Check, run on the matched name, date of birth and state when those are available.

Who the record is for

Each match carries the first, middle and last name and the date of birth on the record, so the right person can be picked from several.

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.

  • Volume-based pricing
  • 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

Global Data Check returns match outcomes without personal data. Enhance Record Plus adds court and social records. Deceased Check and ADC Check answer the death question on its own.

Questions

Questions we get asked about Person History

Do we need a developer to implement this?
Yes. Person History is a REST endpoint that takes a JSON request and returns a JSON list of records, so a developer connects it to your customer or collections system. 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 and last name, and at least one of a date of birth, a phone number in 0NSN format, or an email address. A request with less than that returns a 400 error.
What comes back?
A list of matches. Each carries the first, middle and last name, the date of birth, the deceased flag, the address with suburb, state and postcode and its first and last seen dates, and the phones and emails with their own dates.
Where does the data come from?
The Global Data Universe, an in-house dataset of person and contact records aggregated from many sources. The reference documentation does not publish a refresh cycle; the dates on each record show when it was last seen. The deceased flag comes from the Australian Death Check service.
What are our obligations when using this endpoint?
This endpoint returns personally identifiable information. Access to endpoints that return PII requires an appropriate privacy policy and PII handling processes, and use is subject to the Global Data privacy policy and terms of service. On Global Data's side, PII sent in a request is not retained, data is encrypted in transit and at rest, and retention follows the Australian Privacy Act and the Australian Privacy Principles.
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

Endpoints that return personal information are opened only to accounts with a privacy policy and PII handling processes in place, and production API keys are issued once the account has been commercially approved.

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