Update user
/users/{user_uuid}
Update a single user by UUID.
The update user record is returned in the response.
Example Request
PATCHRequest Schema
user_uuid
The user UUID
enabled
Update the user's enabled status * `true` - The user is enabled * `false` - The user is disabled Note: The API will accept the string 'true' or the number 1 for true and the string 'false' or the number 0 for false as well as the boolean values.
Available Response Data
12 Data Pointsuuid uuid
The user's UUID
username string
The user's username
first_name string
The user's first name
last_name string
The user's last name
email string
The user's email address
phone string
The user's phone number
enabled boolean
Whether the user is enabled
roles array
The user's roles
last_login_at timestamp (The user's last login timestamp (ISO 8601 format))
created_at timestamp (The user's creation timestamp (ISO 8601 format))
updated_at timestamp (The user's last update timestamp (ISO 8601 format))
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
Propagating changes from your system of record
Push corrections and changes of circumstance into WatchEye as they happen, so screening runs against current details, not the details captured at onboarding.
Status and lifecycle management
Change status fields as a matter progresses. A status change is not a deletion, so the record stays fully visible through the API.
Keeping the audit trail intact
Every update is written to the account audit log, so the change history is available without you maintaining a parallel record of 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.
help_center General
Is this call billed?
add
Is this call billed?
Yes. This is a chargeable endpoint, and the fee is billed to your account at the time of the request. Your rates are set per account and confirmed by your Global Data account manager.
If your balance reaches zero or an agreed call limit is reached, further chargeable requests return 402 Payment Required until the account is topped up. Calls made with a key on a sandbox account are never charged.
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 Update user?
Talk to our team about credentials, sandbox access and the right combination of endpoints for your workflow.