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

Show the calling account

Show the calling account returns the account an API key belongs to: its environment of live or sandbox, the products it can use, and the balance, credit limit and available credit that billable calls draw on. It is the recommended first call for a new integration, because it confirms the credentials work and point at the environment you expect.

  • The authoritative answer to which environment a key is in
  • The products the account is entitled to call, so an integration can check before it launches
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 sub accounts
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

Confirming the account before the first billable call

An integration should know three things before it screens anything: that the key works, that it is pointed at sandbox or live as intended, and that the products it will call are enabled. One read answers all three and shows how much credit is available.

Which environment you are in

The environment is live, where calls bill against the balance and return real screening data, or sandbox, where calls do not bill and return test data. This field is the authoritative answer.

What the account can call

The products array lists every product the account is entitled to call billable endpoints against. For a sub account it is the intersection of the parent's products and the sub account's own entitlements.

How much can be spent

The balance and credit limit are decimal strings, and available credit is their sum: the amount available for billable calls. Once the sum drops below the cost of a call, billable endpoints return 402. For a sub account these figures come from the parent, which is the account charged.

Related checks

Others in WatchEye Account

List users reads the portal users on the account. List audit entries reads what has been done with it. Every launch endpoint bills against the balance this call reports.

Questions

Questions we get asked about the account endpoint

What does our system need to send?
Nothing beyond the API key. The account returned is the one the key belongs to.
What comes back?
The account UUID, account and company names, environment, whether it is a reseller and its parent account UUID if it is a sub account, any expiry date, the account-level data retention in days, the balance, credit limit and available credit, the products it can use, and timestamps.
What happens when the account expires?
After the expiry date the API rejects calls with 401 Account Expired. The expires at field is null when no expiry is set.
How do sandbox and live differ?
They are separate accounts with their own keys. Sandbox calls are not charged and return test data in the same shapes as live; the base URL is the same and the account behind the key decides the environment. Sandbox accounts are provisioned by your Global Data account manager.
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