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_alertScreen & Monitor7 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 & screening5 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
WatchEye · Adhoc ID Checks

Show an adhoc ID check

Show an adhoc ID check returns one quick identity check by its UUID, with who launched it, the outcome, the consent attestation, the verification details and the typed details block from the source. Document numbers and other sensitive inputs are never returned.

  • The completed check as it was returned at launch, readable again at any time
  • Attribution to the portal user or API key that launched it
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
  • Per-type details schemas
Go to the API docs

New accounts begin with sandbox access.

ISO 27001 certified Handled under Australian privacy law Every API call written to the audit log
What the check gives you

Reading a one-off identity check back when you need it

The launch returned the completed check inline. This call returns the same record later: to write it to a file, to answer an audit, or to follow an IDPass that was still pending when it was launched.

Whether the document verified

The outcome is pass or fail, or pending while an IDPass is still with the individual. The outcome summary and data summary state the result and the subject in a sentence each.

What the source said

The typed details block carries the source's own result for the type. The verification details list each verified field and its value, and the consent block records the attestation made at launch.

Who ran it

The created by block names the portal user or the API key that launched the check. For an IDPass-backed check, the IDPass shell carries its status, verification status and hosted link, with the path to the full IDPass record.

Reading the result

What each answer means for the record in front of you

ID checks run synchronously, so the outcome in the response is final. The one exception is a check completed through an IDPass, which stays pending until the individual finishes the hosted link.

Pass

The identity was verified

The supplied details were verified by the upstream source. The outcome summary states the result in a sentence, the verification details list what was checked, and the typed details block carries the source's own result, such as a DVS verification result code of Y.

Fail

The details did not verify

The upstream source did not verify the supplied details. For a DVS check the details block carries the result code and any additional information the issuer returned. The check is complete and can be downloaded as a certificate.

Pending

An IDPass is still with the individual

Only an ID check satisfied by an IDPass reports pending. The response embeds the IDPass shell with its status and hosted link; follow the IDPass path and poll it until the status is terminal.

What it costs

Charged per check, after the upstream verification call

Each ID check launch is charged to your WatchEye account at run time, after a successful call to the upstream verification source. The rate for each check type is set for your account and communicated by your Global Data account manager. Statements with a breakdown of API calls and their costs are available in the WatchEye portal.

  • Billed per check
  • Consent asserted on every launch
How billing works
Credits drawn down against your account balance
  • A launch is charged after the upstream verification call succeeds.
  • An entitlement the account lacks returns 403 and nothing is charged.
  • A 402 response means the account has reached its credit or call limit. Nothing is run and nothing is charged.
  • Reads, lists, PDF certificates and images are not billed.
Talk to us about rates
Related checks

Others in WatchEye Adhoc ID Checks

Launch an adhoc ID check creates the check this call reads. List adhoc ID checks finds it. Download an adhoc ID check certificate as PDF produces the certificate. Delete an adhoc ID check removes it.

Questions

Questions we get asked about reading an adhoc ID check

Do we need a developer to implement this?
Yes. This is a REST read by UUID, and the details block differs by type, so a developer maps the shapes your system needs. A sandbox account is available for development at no charge. It is a separate account with its own API keys, it returns test data in the same response shapes as live, and the same base URL serves both environments.
What does our system need to send?
The adhoc ID check UUID in the path, as returned by the launch or the list. Nothing else.
What comes back?
The check with its UUID, check number, id type and check type with display names, outcome, outcome summary, data summary, checked at time, who created it, consent, verification details and the typed details block. When the id type is idpass, an IDPass shell and its path are included.
Is reading a check billed?
No. The charge is made at launch. Reading, listing and downloading the certificate are not billed.
What if the check has been deleted?
Soft-deleted records return 404 from this endpoint and are no longer returned by the list. They remain in the database for compliance and audit purposes and can be restored in the portal within 30 days by a user with the account manager role.
What happens to the personal information in the response?
Personal information stored in WatchEye is covered by Global Data's security policies for the platform. Once your integration copies it into your own applications, databases, logs or backups, protecting it becomes your responsibility. Retrieve only the fields you need and treat any logs that capture API payloads as sensitive.
Getting started

The first step to access is a conversation

Sandbox accounts are provisioned by your Global Data account manager. API keys are created and managed in the WatchEye portal, and the same endpoints serve sandbox and live; the account behind the key decides which environment you are in.

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

ISO 27001 certified
Handled under Australian privacy law
Every API call written to the audit log