- Rate limit changes propagate within 30 seconds across all regions
- Providing
--meta-jsonreplaces all existing metadata; omitting it preserves current metadata - Providing
--ratelimits-jsonreplaces all existing rate limits; omitting it preserves current rate limits
identity.*.update_identity(to update identities in any workspace)
See the API reference for the full HTTP endpoint documentation.
Usage
Flags
The ID of the identity to update. Accepts either the externalId (your system-generated identifier) or the identityId (internal identifier returned by the identity service).
JSON object of metadata to replace existing metadata. Omitting this flag preserves existing metadata, while providing an empty object
'{}' clears all metadata. Avoid storing sensitive data here as it is returned in verification responses. Large metadata objects increase verification latency and should stay under 10KB total size.JSON array of rate limit configurations. Replaces all existing identity rate limits with this complete list. Omitting this flag preserves existing rate limits, while providing an empty array
'[]' removes all rate limits. These limits are shared across all keys belonging to this identity, preventing abuse through multiple keys.Global Flags
| Flag | Type | Description |
|---|---|---|
--root-key | string | Override root key ($UNKEY_ROOT_KEY) |
--api-url | string | Override API base URL (default: https://api.unkey.com) |
--config | string | Path to config file (default: ~/.unkey/config.toml) |
--output | string | Output format — use json for raw JSON |
Examples
Output
Default output shows the request ID with latency, followed by the updated identity:--output=json, the full response envelope is returned:

