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

List IDPasses

List IDPasses returns the remote identity verifications on the calling account as a paginated list. Each record carries where the individual is in the hosted flow and, once terminal, the verification status. Filters narrow the list by status, verification status, source, entity, program and creation date.

  • Every IDPass on the account, 30 per page by default and up to 500, newest first
  • Filter by status, verification status, entity-bound or adhoc source, entity, program and date range
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
  • Filters, sort fields and pagination
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

Finding the verifications that are waiting on a person

Remote verifications finish when the individual finishes. The list is how a queue, a reminder job or a reviewer finds the ones still open, the ones flagged for review, and the ones done.

Where each one is

Each record carries the status, the completed flag and, once terminal, the verification status of passed, review or failed, alongside the configuration and delivery details.

Where it belongs

The source says whether the IDPass is bound to an entity or was launched adhoc, and the originating ID check is linked.

Only the records you asked for

Filters cover status, verification status, source, entity, program, created after and created before. Sort by created at or status, ascending or descending.

How a check runs

Where IDPasses sit in the WatchEye model

An IDPass is an asynchronous identity verification that the individual completes through a hosted link. It belongs to an ID check, entity-bound or adhoc, and every call that touches it is written to the audit log.

A record still new, opened or in progress carries a null verification status until the individual finishes or the link expires.

What it costs

Charged at creation, by the number of document steps configured

Each IDPass launch is charged to your WatchEye account when it is created. The product billed depends on how many document verification steps are configured, from one to three. If the link is never used and expires, the launch charge is refunded. Rates are set for your account and communicated by your Global Data account manager.

  • Billed at creation
  • Refunded if the link expires unused
How billing works
Credits drawn down against your account balance
  • A launch is charged when the IDPass is created.
  • The product billed follows the number of document steps: one, two or three.
  • A link that lapses unused moves the IDPass to expired and the launch charge is refunded.
  • A 402 response means the account has reached its credit or call limit. Nothing is run and nothing is charged.
Talk to us about rates
Related checks

Others in WatchEye IDPass

Show an IDPass reads one record in full. Launch an IDPass against an entity and Launch an adhoc IDPass create them. Download an IDPass certificate as PDF produces the certificate once a record is terminal.

Questions

Questions we get asked about listing IDPasses

Do we need a developer to implement this?
Yes. This is a paginated REST list with query-string filters, so a developer connects it to whatever queue or reporting job needs it. 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?
Nothing is required. Optional query parameters are page, per page, the filters for status, verification status, source, entity UUID, program UUID, created after and created before, and a sort field.
What comes back?
A data array of IDPass records, a meta object with the current page, per page, total and last page, and an API reference for the call.
How is the list ordered and paged?
Newest first by default. Sort by created at or status, with a leading minus for descending. Pages hold 30 records by default and up to 500.
Is listing billed?
No. Reads are not charged; the charge is made when an IDPass is launched.
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