History log
Last updated
Last updated
Use the History Log to: debug failing calls, monitor key usage frequency, audit API activity for a period, and investigate throttling events.
Column
What it tells you?
API Key
Which key made the call
Method
POST / PUT / GET
Endpoint
Which KMS operation was called
Status
200 OK / 429 Too many request / 403 / ...
Latency
How long the call took (ms)
Time
When it happened
Request and response content are never stored — only metadata is logged. KMS never logs the data being encrypted or decrypted.
Workspace Admins can click each history log entry to view more detailed information. KMS also lets users export these logs for specific purposes.