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
Liveness Check

Retrieve a Liveness Check Result API

Retrieve a Liveness Check Result returns the current status or the final result of a liveness check from its token. It can be polled safely until the check is complete, and returns whether the face was live, the confidence score, the threshold applied and, while they are held, the captured images.

  • A passed flag with the confidence score and the threshold applied, so the decision and its evidence are returned together
  • A 202 while the check is pending or in progress, a 200 once complete, and a 410 once the link has expired without a result
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.

  • Response schema and status codes
  • Polling guidance and security notes
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

Collecting the liveness result once the person has completed the capture

A liveness check runs in the person's browser, so your system waits for it. Retrieve a Liveness Check Result is the call that collects the outcome. It reports whether the check is still pending or in progress, returns the result once it is complete, and says when the link expired without one.

Whether the face was live

The result carries a passed flag, the confidence score from the liveness provider, the threshold applied and the time the result was finalised.

Why it did not pass

On a failed or expired check the result carries an error code, failed or expired.

The images, while they last

The probe image and any audit frames requested at creation are returned as data URIs with bounding box metadata while they are held, around 30 minutes. After that the same result is returned without images.

Where the check is

A 202 response with a message says whether the check is pending, not yet claimed, or in progress. The documentation recommends polling every 2 to 3 seconds with back-off.

How a check runs

Created with a link; this call carries the result

Create a Liveness Check returns a token and a link straight away. Once the person has completed the capture, this call returns the result for that token. While the capture is pending or in progress it returns 202, so your system asks again.

The recommended polling interval is 2 to 3 seconds, with exponential backoff. Fetch the result under your own authenticated server context rather than trusting the token from a redirect on its own.

Reading the result

What each answer means for the record in front of you

The status code says whether there is a result. The passed flag says what it is.

Passed

The face was live

A 200 response with passed true. The confidence score reached the threshold. Store the result and, if needed, the images before they expire from the cache.

Not passed

The face was not deemed live

A 200 response with passed false and the error code failed. Ask for a new capture before declining.

In progress

No result yet

A 202 response. The check is pending or the person is still capturing. Poll again in 2 to 3 seconds.

Expired

The link ran out

A 410 response. The validity period elapsed without completion. Create a new liveness check.

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 Liveness Check

Create a Liveness Check issues the token this call takes.

Questions

Questions we get asked about Retrieve a Liveness Check Result

Do we need a developer to implement this?
Yes. The result call is a REST endpoint that must be repeated until a 200 or 410 is returned, so a developer builds the polling into your system alongside the create call. 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 token returned by Create a Liveness Check, as a query parameter. An unknown token returns a 400, and a token belonging to another account is refused.
What comes back?
A 200 with the result object once complete: passed, confidence, threshold, the time checked, an error code on failure, and the probe and audit images while they are held. A 202 with a status message while pending or in progress. A 410 once the check has expired.
How often should we poll?
Every 2 to 3 seconds, with exponential back-off encouraged. Stop when a 200 is returned, or when your own rules say the check should be abandoned.
Why must this be called from our server?
The token on the return-URL redirect can be tampered with. Fetching the result here with your API key validates that the token belongs to your account, and a 403 or 400 protects you if it does not.
Are the images captured 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.
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.

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