WatchEye · Adhoc ID Checks

List adhoc ID checks

Q: How do I filter and page through the results?

Filters use the filter[key]=value syntax, and unknown keys are ignored, not rejected. Sorting uses the sort parameter, with a leading - for descending order. One behaviour worth designing around: a filter targeting a UUID that is unknown, or that belongs to a different account, returns an empty page (data: [], meta.total: 0) instead of a 404. That is the same response as a filter which legitimately matches nothing, so an empty result does not on its own tell you the UUID was valid.

GET

/adhoc-id-checks

LIVE

Returns quick (adhoc) identification checks for the calling account. These are one-off
checks not tied to a program or entity record.
Actor attribution is via the created_by discriminator (user for a portal launch or
api_key for an API launch). Filter by created_by, created_by_user_uuid or
created_by_api_key_uuid to narrow results.

Request a Demo Contact Sales

List adhoc ID checks

Example Request

GET

request.http

key Auth: BearerAuth

GET /adhoc-id-checks
Authorization: Bearer <your-api-key>
Accept: application/json

Request Schema

page

Optional

integer · query

per_page

Optional

integer · query

filter[id_type]

Optional

string · query

filter[check_type]

Optional

string · query

filter[outcome]

Optional

enum · query, pass | fail | pending

filter[created_by]

Optional

enum · query, user | api_key

filter[created_by_user_uuid]

Optional

uuid · query

filter[created_by_api_key_uuid]

Optional

uuid · query

filter[checked_after]

Optional

date · query, ISO 8601 date-time

filter[checked_before]

Optional

date · query, ISO 8601 date-time

sort

Optional

string · query

Available Response Data

14 Data Points

inventory_2 What You Receive

fingerprint

uuid uuid

tag

check_number string

data_object

id_type string

person

id_type_name string

data_object

check_type string

person

check_type_name string

monitor_heart

outcome enum

pass, fail, pending

monitor_heart

outcome_summary string

data_object

data_summary string

schedule

checked_at timestamp

data_object

created_by object

Identifies who launched the adhoc ID check

data_object

idpass object

A lightweight view of an IDPass embedded in an ID check response

data_object

meta object

pagination: current_page, per_page, total, last_page

fingerprint

api_reference uuid

unique request identifier for log tracing and audit

lock Full API documentation provided after vetting from our compliance team. Request sample response arrow_forward

By The Numbers

API Data Scale & Coverage tag

Unmatched data depth to power your compliance and verification workflows.

50M+

Phone & Email Records

40M+

Adverse Court Records

2BN+

Australian Universe Records

18M+

Real Estate Records

7M+

Deceased Records

980M+

Social Media & Employment Records

science

Sandbox Environment

Build and test against a sandbox account. Sandbox is a separate account with its own UUID and its own API keys, and the environment is fixed at the account level, so you cannot switch an existing key between live and sandbox with a parameter or header. Both share the same base URL, so the account behind your key is what determines which environment you are in. GET /v1/account returns an environment field of live or sandbox, and that is the authoritative answer.

Calls on a sandbox key are not billed. Every endpoint, response shape, error envelope, idempotency and rate-limit behaviour mirrors live, so the only change when you move to production should be the credentials. Sandbox accounts are provisioned by your Global Data account manager.

Identity verification works end to end in sandbox using the same endpoints and response shapes as live. No real SMS is sent for an IDPass delivered by SMS on a sandbox account; the message is recorded instead of delivered.

Practical Applications

Technical Use Cases tag

format_list_bulleted

Reconciliation against your own system

Page through every adhoc ID check on the account and compare it with your own records, so the two stay aligned without anyone exporting a spreadsheet. Filters use the filter[key]=value syntax and results are paginated.

sync

Scheduled sync jobs

Sort by -created_at or -updated_at and pull only what has changed since the last run, which keeps a nightly sync proportional to the delta, not the whole book.

dashboard

Operational dashboards

Drive an internal dashboard from live counts. meta.total gives the size of the filtered set without fetching every page.

Trust & Assurance

Compliance & Security tag

Enterprise-grade infrastructure audited against the standards your regulators require.

verified_user

ISO 27001 Certified

enhanced_encryption

AES-256 Encryption

public

Australian Data Sovereignty

Integration & Support

Common Questions tag

Everything you need to know about implementation details and compliance infrastructure.

Filter by topic

help

Compliance Team

Global Data Support

Need help planning your custom integration or understanding our compliance coverage? Our team is here to assist.

rocket_launch Implementation

How do I filter and page through the results?

add

Filters use the filter[key]=value syntax, and unknown keys are ignored, not rejected. Sorting uses the sort parameter, with a leading - for descending order.

One behaviour worth designing around: a filter targeting a UUID that is unknown, or that belongs to a different account, returns an empty page (data: [], meta.total: 0) instead of a 404. That is the same response as a filter which legitimately matches nothing, so an empty result does not on its own tell you the UUID was valid.

rocket_launch Implementation

What are the rate limits?

add

600 requests per minute by default, enforced with a 60-second fixed window. Every response carries X-RateLimit-Limit and X-RateLimit-Remaining.

Exceeding the limit returns 429 Too Many Requests with a Retry-After header giving the number of seconds to wait, and X-RateLimit-Reset giving the reset timestamp. Schedule retries from Retry-After instead of a fixed sleep, and slow down before you hit zero, not after.

Higher limits can be arranged case by case through WatchEye support.

Enquire now

Ready to integrate List adhoc ID checks?

Talk to our team about credentials, sandbox access and the right combination of endpoints for your workflow.

Call 03 9948 4089 · sales@globaldata.net.au

Request a Demo Contact Sales