Skip to content
In force

Tranche 2 started 1 July — AML/CTF obligations now extend beyond financial services.

See who is coveredarrow_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
WatchEye · Adhoc ID Checks

Download an adhoc ID check certificate as PDF

Download an adhoc ID check certificate returns a verification certificate PDF for a completed quick identity check, produced from the check already on record. It is not billed. A check whose outcome is still pending returns 409 until it is final, and an IDPass-backed check has no WatchEye certificate.

  • A certificate PDF for any adhoc ID check with a final outcome of pass or fail
  • Generated from the on-record check at no charge
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
  • Status codes and timeouts
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

Evidence of the verification, for the customer file

A one-off verification still needs a record of what was verified and what the source answered. This endpoint turns a completed adhoc ID check into that document without re-running anything.

A certificate for a completed check

The PDF is returned once the outcome is pass or fail. A check still pending returns 409; poll Show an adhoc ID check until the outcome is set, then retry.

A file ready to store

The response is a binary PDF. Write the body straight to a file against the customer record.

A clear answer when there is no certificate

A 404 means either the check does not exist on the calling account or its id type is idpass, which does not produce a downloadable certificate.

How a check runs

Where certificates sit in the WatchEye model

An adhoc ID check is a synchronous verification with no program or entity. The certificate is a rendering of that check, produced on request from the data already held.

The IDPass certificate for an IDPass-backed check comes from the IDPass PDF endpoint instead.

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

Show an adhoc ID check returns the same check as JSON. List adhoc ID checks finds the check to download. Download an ID check certificate as PDF does the same for an entity-bound check.

Questions

Questions we get asked about the adhoc certificate

Do we need a developer to implement this?
Yes. The endpoint returns a binary PDF rather than JSON, so a developer handles the response as a file and stores it where your records live. 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. Nothing else.
What comes back?
A binary PDF certificate on 200. A 409 while the outcome is still pending. A 404 when the check does not exist on the account or its id type is idpass.
Is it billed?
No. The certificate is generated from the check data already on record.
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.
How many calls can we make?
The default rate limit is 600 requests per minute, enforced in a 60-second fixed window. Requests over the limit receive a 429 response, so pace requests evenly and back off before retrying. A higher limit can be arranged on a case-by-case basis.
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