---
title: "List secret audit history"
description: "Returns the newest secret-set audit events, never values."
canonical: "https://www.cool.computer/docs/api-reference/secrets/list-secret-audit-history"
---
# List secret audit history

> Returns the newest secret-set audit events, never values.

```http
GET https://api.cool.computer/api/secrets/audit
```

Returns the newest secret-set audit events, never values.

## Authorization

- A Cool Computers API key, user access token, or claimed agent access token in the Authorization header. Follow https://www.cool.computer/auth.md for agent registration and https://www.cool.computer/authentication.md for direct user credentials.

## Parameters

- `tail` (query, integer, 1 to 200): Maximum number of newest entries.
- `since` (query, string, date-time): Return only entries at or after this RFC 3339 time.

## Responses

- `200`: Secret audit events, newest first.
  - `application/json` (object)
    - `retention` (string, required)
    - `events` (array of object, required)
      - `secret_set` (string, required)
      - `action` (string, required)
      - `keys` (array of string, required)
      - `actor` (object, required)
        - `type` ("member" or "organization_api_key" or "computer", required)
        - `id` (string, required)
      - `timestamp` (string, date-time, required)
- `400`: Bad Request.
- `401`: Unauthorized.
- `429`: Too Many Requests. If the problem code is api_request_rate_exceeded, wait for Retry-After seconds; other problem codes describe a separate limit.
- `500`: Internal Server Error.
- `default`: A machine-readable API error with a stable code and recovery instruction.

An error is an `application/problem+json` document with a stable `code`; [API errors](/docs/api-reference/errors) says how to handle one.

## Example

```sh
curl "https://api.cool.computer/api/secrets/audit" \
  -H "authorization: Bearer $TOKEN"
```
