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

Delete a monitor

Deleting a monitor is a soft delete. It stops appearing in list and show responses but remains in the database for compliance and audit purposes, and a user with the account manager role can restore it in the portal within 30 days. To stop a monitor while keeping its configuration and history visible, pause it instead; monitors have no separate archive state.

  • Soft delete: hidden, not destroyed, within the recovery window
  • Pausing is the documented way to stop a monitor you want to keep
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
  • Soft-deletion policy
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

Retiring a screening job

A monitor that will not run again, or one being replaced by a monitor with a different operation, is deleted in one call. WatchEye preserves the record, so its history stays available for audit and the deletion can be reversed within the recovery window.

That the monitor is gone from the working views

After deletion the monitor is no longer returned by the list and its show endpoint returns 404.

What was deleted

The response returns the deleted monitor once as confirmation. A subsequent show or list call returns 404.

That it can be recovered

Soft-deleted records can be restored within 30 days by a user with the account manager role from the portal's Show deleted filter. There is no API restore. After 30 days the record may be permanently removed.

How a check runs

The lifecycle a monitor moves through

A monitor is created active, can be paused and resumed, and is soft-deleted rather than destroyed. It has no archive state.

To keep a monitor visible but stop it running, pause it with Update a monitor instead.

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

Update a monitor pauses a monitor you want to keep. Show a monitor reads it before you delete it. Create a monitor replaces one whose operation must change.

Questions

Questions we get asked about deleting a monitor

Do we need a developer to implement this?
Yes. This is a single REST call by UUID, so a developer wires it to whatever retires a screening job in your system. 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?
A 200 with the deleted monitor record, returned once as confirmation. Subsequent calls for the same UUID return 404.
Is the data destroyed?
No. Every delete endpoint in the API is a soft delete. The monitor stays in the database for compliance and audit purposes, hidden from the API and the portal, and the show endpoint returns 404.
Can it be undone?
Within 30 days, in the portal: a user with the account manager role applies the Show deleted filter, opens the record and chooses Restore. There is no API equivalent. After the window the record is eligible for permanent removal and its UUID cannot be recovered.
Should we delete or pause?
Pause when the configuration and run history should stay visible: the monitor stops running and everything remains readable. Delete when it should leave the working views altogether.
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