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

Create a program

Creating a program sets up the container that holds the entities you monitor and the monitors that screen them. Only a name is required; status, data retention, event grouping, report emails and the default risk level all have defaults. The call returns 201 with the created program, ready to receive entities.

  • One required field, the program name; every other setting has a documented default
  • Retention from no retention to 84 months, event grouping per entity, and up to five report email addresses
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
  • Fields, defaults and idempotency
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

A container for the people, businesses and vessels you monitor

Programs are how WatchEye separates one monitoring purpose from another: a program for onboarding, another for ongoing customer screening, another for suppliers. Each carries its own entities, its own monitors and its own settings for how long data is kept and how events are grouped.

A program with sensible defaults

Left unset, a new program is active, keeps entity data for 12 months, raises separate events capped at 10 per entity, sends no report emails and pre-fills new entities with low risk.

How events are raised

With separate grouping each match becomes its own event, up to the maximum you set between 5 and 100 per entity. With grouped, matches for an entity are merged into a single event.

Who hears about events

Up to five email addresses receive event report notifications for the program.

That a retry will not create a second program

An optional Idempotency-Key header returns the original response on a retry with the same key and body. A key reused with a different body is rejected with 422, and a key still being processed with 409.

How a check runs

Where programs sit in the WatchEye model

A program holds entities and monitors. Screening runs against an entity, matches become events in the triage queue, and every call is written to the audit log.

A program can be paused, which stops its monitors running while its entities and checks remain accessible, and set back to active later.

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 Programs

Show a program reads it back. Update a program changes its settings or pauses it. List programs finds every program on the account. Create an entity in a program adds the records to monitor.

Questions

Questions we get asked about creating a program

Do we need a developer to implement this?
Yes. This is a single REST call that returns the created program, so a developer wires it to whatever sets up a new monitoring purpose 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?
A program name of 2 to 255 characters. Optionally a status, report emails, data retention months, event grouping with a maximum of separate events, and a default risk level. Anything omitted takes its default.
What can a program be configured with?
A name of 2 to 255 characters; a status of active or paused; up to five report email addresses that receive event report notifications; data retention in months, one of 0, 1, 3, 6, 12, 24, 36, 48, 60, 72 or 84; event grouping of separate, capped by a maximum of 5 to 100 separate events per entity, or grouped into one event per entity; and a default risk level of low, medium or high that new entities are pre-filled with, or null to leave it unassigned.
What comes back?
A 201 with the program: its UUID, a short program number, the name, status, report emails, retention, event grouping and maximum separate events, default risk level, and the created and updated timestamps.
What does it cost?
Charges arise when screening runs in the program: checks launched against its entities and monitor runs. Rates are set for your account.
What if the connection drops after we send the request?
Send an Idempotency-Key header, typically a fresh UUID per logical request. A retry with the same key and body returns the original response verbatim, marked with an Idempotent-Replay header, and the program is not created twice. A successful response is remembered for 24 hours, and the same key with a different body is rejected with 422.
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