# Workbench request log

Use `GET /v1/requests` with `workbench:read` on the [management API](/reference/api/management/). Results belong to the caller's environment and are newest first. Pagination uses `limit` (default 20, maximum 100) and either `after` or `before`.

| Filter         | Accepted value                                                                       |
| -------------- | ------------------------------------------------------------------------------------ |
| `api_key`      | API key object ID, never its secret                                                  |
| `organization` | Organization ID                                                                      |
| `path`         | Exact route template such as `/v1/organizations/{org}`, not a concrete resource path |
| `status`       | HTTP status such as `404`, or class such as `4xx`                                    |
| `request_id`   | The 32-character lowercase hexadecimal `Request-Id` response header                  |

Rows contain method, route template, status, duration, timestamp, request ID and applicable API key/organization IDs. Bodies, headers, query values, tokens, IP addresses and emails are not stored. An organization ID is recorded only for a successful route naming that organization, so this filter does not cover every call that mentions it in a body.

Recording runs after authorization for an environment principal. Unauthenticated and dashboard-only calls are absent. A dashboard session calling an authorized management route can be recorded, but it has no API key ID.

## Retention and completeness

Current retention is three days on Free, thirty on Pro and ninety on Business and Enterprise. Per-account Enterprise overrides are not implemented. Cleanup runs through the worker.

This log is best effort: a bounded queue drops entries when full, and failed database writes are counted without retry. Logging never blocks or fails the API request. An absent row is not proof a request never happened; this is not the durable audit trail. Use [sign-in history and timelines](/sso/sign-in-history/) for broker sign-in diagnostics.
