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

Create a relationship on an entity

Creating a relationship records a directed link from the entity in the path to another entity on the account, which may sit in a different program: a person who is a director of a company, the spouse of another person, a shareholder with a percentage. Ownership percentages on the types that carry them drive ultimate beneficial owner tracing.

  • Fourteen relationship types, each checked against the entity types on either side
  • An ownership percentage and effective dates where the type supports them
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
  • Types, direction and ownership
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

Building the ownership and control picture around a customer

Beneficial ownership is only as good as the relationships recorded. Each call adds one link with its direction, type, ownership percentage and effective dates, and the UBO endpoint walks the result.

What was recorded

The response returns the relationship with its type, a forward label and an inverse label so it reads correctly from either entity, whether the type is symmetric, the from and to entities, the ownership percentage where the type supports one, effective dates, a comment and how it was recorded.

That it is recorded once

A relationship of a given type is stored once between two entities. For a symmetric type such as spouse of, the pair counts as one relationship whichever way it was sent, and a repeat request returns 409.

That a retry will not duplicate it

An optional Idempotency-Key header returns the original response on a retry with the same key and body.

Related checks

Others in WatchEye Relationships

Resolve an entity's ultimate beneficial owners walks the relationships this call records. List an entity's relationships reads them. Delete a relationship removes one.

Questions

Questions we get asked about creating a relationship

What does our system need to send?
The from entity's UUID in the path, and a body with the to entity's UUID and the relationship type. Optionally an ownership percentage from 0 to 100 for the types that support it, effective from and effective to dates in YYYY-MM-DD format, and a comment of up to 255 characters.
Which relationship types are there?
Spouse of, director of, shareholder of, trustee of, beneficiary of, parent of, sibling of, employee of, officer of, partner in, owner of, buyer of, seller of and associated with. Each type permits only certain entity types on each side; a director of relationship links an individual to a business, for example, and a pairing the type does not permit is rejected with 422. Associated with requires a comment.
How is direction set?
The path entity is the from side and the body's entity is the to side. To record the relationship the other way round, send the request to the other entity. Buyer of and seller of are point-in-time types that record a single dated event in effective from; an effective to date on them is stored as null.
What comes back?
A 201 with the relationship, or a 409 when a relationship of that type already exists between the two entities.
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 relationship is not created twice. A successful response is remembered for 24 hours, and the same key with a different body is rejected with 422.
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