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 · Monitors

Show a monitor

Show a monitor returns one monitor by its UUID with its operation, status, in-flight process status and any comment on it, schedule, configuration, when it last ran and whether it has run before. It is the endpoint to poll after Run a monitor on demand until the process status leaves pending and processing.

  • Status and process status side by side: what you set, and what is happening now
  • The configuration in force, so your system can confirm what a run will screen with
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
  • Response fields and process status values
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

Knowing what a monitor will do, and whether it is doing it now

Before a run, a system checks the configuration and schedule. During a run, it polls the process status. After a run, it reads when the monitor last ran and whether the run failed or paused. One read answers all three.

What it screens for and how

The check type with its display name and the per-operation configuration in force. The portal's monitor screens render the same fields.

Whether it runs, and whether it is running

Status is active or paused. Process status is pending, processing, failed or paused while a run is in flight or has just ended badly, and null when the monitor is idle, with a comment carrying any failure message.

When it ran

The schedule with its display name, the last run time or null if it has never run, and whether it has processed at least one entity, which the new run type uses to know where to resume.

How a check runs

A run in progress, read from this endpoint

Run a monitor on demand returns 202 once the run is scheduled. Your system polls this endpoint until the process status is no longer pending or processing, then reads the new events.

A run across thousands of entities can take several minutes. Poll every 2 to 5 seconds for the first 30 seconds, then every 15 to 30 seconds.

What it costs

Charged when screening runs, not when records are managed

Charges arise when screening runs against the entities in a program: each check type launched against an entity is charged at launch, and a monitor run is charged for each entity eligible for its operation. Rates are set for your account and communicated by your Global Data account manager, and statements with a per-call breakdown are in the WatchEye portal.

  • Billed per screening operation
  • Refunded if the provider fails
How billing works
Credits drawn down against your account balance
  • A screening check is charged per check type when it is launched, and refunded if the provider fails.
  • A monitor run bills only for the entities eligible for its operation; a UK check skips businesses outside the UK, for example.
  • A run that would exceed the account's credit is refused with 402 and a billing breakdown, before anything is queued.
  • Reads, lists and PDF downloads are not billed.
Talk to us about rates
Related checks

Others in WatchEye Monitors

Run a monitor on demand starts the run this call reports on. Update a monitor changes what it reads. List monitors in a program finds it. List events shows what a run raised.

Questions

Questions we get asked about reading a monitor

Do we need a developer to implement this?
Yes. This is a REST read by UUID that your system polls after a run, so a developer connects it to whatever waits on the result. 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 monitor UUID in the path. Nothing else.
What comes back?
The monitor with its UUID, monitor number, name, check type and display name, status, process status and comment, schedule and display name, configuration, last run time, whether it has run before, the program UUID and timestamps.
What is the difference between status and process status?
Status is the lifecycle setting you control: active runs on its schedule and can be triggered manually, paused does neither. Process status is the in-flight state of a run: pending, processing, failed when the most recent run failed, paused when a run stopped mid-flight for example on credit, or null when the monitor is idle.
How do we know a run has finished?
Poll until the process status leaves pending and processing. Null means the monitor is idle again and the run completed; failed means the most recent run failed and is cleared on the next successful run; paused means the run stopped mid-flight, for example on insufficient credit.
What if the monitor 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