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

List adhoc ID checks

List adhoc ID checks returns the one-off identity checks on the calling account as a paginated list. Each record is a compact envelope with the type, the outcome and who launched it: a portal user or an API key. Filters narrow the list by id type, check type, outcome, creator and date.

  • Every adhoc ID check on the account, 30 per page by default and up to 500, newest first
  • Filter by who launched the check, whether a portal user or an API key, as well as type, outcome and date
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
  • Filters, sort fields and pagination
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

Finding the one-off verifications that ran outside your programs

Adhoc ID checks accumulate from quick checks in the portal and from integrations verifying on demand. The list is how a reviewer or a reconciliation job finds them and sees who ran them.

What ran and what it found

Each record carries the id type and the underlying check type with display names, the outcome of pass, fail or pending, and a one-line outcome summary and data summary.

Who launched it

The created by block names the portal user or the API key. Filter by creator kind, by user UUID or by API key UUID to isolate one source of checks.

Only the checks you asked for

Filters cover id type, check type, outcome, creator, checked after and checked before, with a sort field and a leading minus for descending order.

How a check runs

Where adhoc ID checks sit in the WatchEye model

An adhoc ID check is a synchronous verification with no program or entity. Every call that touches it is written to the audit log.

Pending appears only on a check satisfied by an IDPass that the individual has not yet completed.

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 reads one record in full. Launch an adhoc ID check creates them. List ID checks covers the checks that ran against entities in your programs.

Questions

Questions we get asked about listing adhoc ID checks

Do we need a developer to implement this?
Yes. This is a paginated REST list with query-string filters, so a developer connects it to whatever reporting or review job needs it. 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?
Nothing is required. Optional query parameters are page, per page, the filters for id type, check type, outcome, created by, created by user UUID, created by API key UUID, checked after and checked before, and a sort field.
What comes back?
A data array of adhoc ID check envelopes, a meta object with the current page, per page, total and last page, and an API reference for the call.
How is the list ordered and paged?
Newest first by default, with a leading minus on the sort field for descending order. Pages hold 30 records by default and up to 500.
Is listing billed?
No. Reads are not charged; the charge is made when a check is launched.
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