List audit entries
/audits
Returns audit log entries for the calling account. Results are paginated.
The audit log records significant activity on your account: who did what, when, from
which IP, and against which resource. Use it to feed external SIEM / compliance systems,
to reconstruct an entity's history, or to surface activity in your own UI.
Example Request
GETRequest Schema
page
per_page
The number of audit entries per page (defaults to 30, max 500)
filter[action]
Exact action key
filter[action_type]
filter[user_uuid]
filter[api_key_uuid]
filter[entity_uuid]
filter[created_at_from]
filter[created_at_to]
sort
Field to sort by; prefix with `-` for descending order
Available Response Data
11 Data Pointsuuid uuid
The audit entry's UUID
action string
Machine-readable action key
action_label string
Human-readable label for the action, suitable for display in UIs
action_type string
Optional sub-type qualifying the action
description string
Human-readable description recorded at the time the audit was created
client_ip_address string
The IP address the action originated from, where one was captured
agent object
Who performed the action
subject object
The resource the action was performed on
created_at timestamp
ISO 8601 timestamp at which the audited action occurred
meta object
pagination: current_page, per_page, total, last_page
api_reference uuid
unique request identifier for log tracing and audit
API Data Scale & Coverage tag
Unmatched data depth to power your compliance and verification workflows.
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.
Technical Use Cases tag
Reconciliation against your own system
Page through every audit record 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.
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.
Operational dashboards
Drive an internal dashboard from live counts. meta.total gives the size of the filtered set without fetching every page.
Compliance & Security tag
Enterprise-grade infrastructure audited against the standards your regulators require.
Common Questions tag
Everything you need to know about implementation details and compliance infrastructure.
rocket_launch Implementation
How do I filter and page through the results?
add
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.
rocket_launch Implementation
What are the rate limits?
add
What are the rate limits?
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.
Ready to integrate List audit entries?
Talk to our team about credentials, sandbox access and the right combination of endpoints for your workflow.