API Reference · Secrets

Read the secrets audit log

The workspace's secrets audit trail, newest first: `created`, `updated` (detail `v<N>`), `rolled_back` (detail `→ v<N>`), `deleted`, and `read` — the last logged when a workspace agent fetches a granted value through the value endpoint (detail = the agent identity). A pod consuming a secret via `secretEnv` is mounted by the kubelet and never crosses the platform API, so it is deliberately NOT logged. Entries never carry values. Workspace-wide by default; pass `path` for one secret's history, and keyset-paginate with `before`.

GET/v1/tenants/{name}/secrets/audit

Authorization

x-api-keystringrequired

Your per-workspace API key, e.g. llc_AbC123…. Also accepted as Authorization: Bearer <key>. Mint keys on your workspace's API keys page — each key belongs to one workspace.

Path parameters

namestringrequired

Workspace (tenant) name.

Response

200 — Audit entries, newest first.

entriesarray

curl https://api.live-llm.com/v1/tenants/acme/secrets/audit \
  -H "x-api-key: $LIVELLM_KEY"

Try itGEThttps://api.live-llm.com/v1/tenants/{name}/secrets/audit

API keyYour key stays in your browser (saved locally on this device) and is sent only to the API.

name*

Fill required path param: name.

Example response200

{
  "entries": [
    {
      "id": 42,
      "ts": "2026-08-01T10:22:00Z",
      "actor": "agent:dev-box",
      "actorLabel": "dev-box agent",
      "action": "read",
      "path": "/prod/tg-bot-token",
      "detail": "granted via web.secretEnv"
    }
  ]
}