Show an audit entry
/audits/{audit_uuid}
Returns a single audit entry by its UUID, including the full properties object for the
action.
The shape of the properties object varies by action. Treat it as an action-specific
bag of contextual data rather than a fixed schema; new keys may be added over time as
new features are added.
Example Request
GETRequest Schema
audit_uuid
The audit entry UUID
Available Response Data
11 Data Pointsuuid uuid
The audit entry's UUID
action string (Machine-readable action key (see Audit.action))
action_label string
Human-readable label for the action
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 (Originating IP address (null for actions performed by the system))
agent object
Who performed the action - see Audit.agent
subject object
The resource the action was performed on - see Audit.subject
properties object
Action-specific properties recorded at the time of the action
created_at timestamp
ISO 8601 timestamp at which the audited action occurred
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
Detail view in your own UI
Fetch the full audit record record by UUID to render a detail screen inside your own application, so staff never need a second system open.
Evidence for a decision record
Retrieve the stored audit record at the point a decision is made and attach it to your case file, with the api_reference value recorded for log tracing.
Support and reconciliation
Resolve a single UUID when investigating a discrepancy, without paging a list endpoint to find it.
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
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 Show an audit entry?
Talk to our team about credentials, sandbox access and the right combination of endpoints for your workflow.