> For the complete documentation index, see [llms.txt](https://oten.gitbook.io/kms-support/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://oten.gitbook.io/kms-support/user-guide/publish-your-docs-1/api-platform/history-log.md).

# History log

Use the History Log to: **debug** failing calls, **monitor** key usage frequency, **audit** API activity for a period, and **investigate** throttling events.

### Overview list

<div align="left" data-with-frame="true"><figure><img src="/files/QnRQWRxOfyi6522YwGtx" alt=""><figcaption></figcaption></figure></div>

| 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                          |

### Details

<div align="left" data-with-frame="true"><figure><img src="/files/eVAuiwSeXIUnIKuDkT5J" alt="" width="375"><figcaption></figcaption></figure></div>

* Workspace Admins can click each history log entry to view more detailed information. KMS also lets users **export** these logs for specific purposes.

### **Security note:**

Request and response content are never stored — only metadata is logged. KMS never logs the data being encrypted or decrypted.