> ## Documentation Index
> Fetch the complete documentation index at: https://docs.zeptar.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Request log overview

> Every authenticated API call your workspace makes is recorded automatically. Browse, filter, and export the full history from the dashboard.

The **request log** is a durable, searchable record of every authenticated request that reaches the `/v1` surface of the Zeptar API. You do not need to instrument anything — logging happens at the infrastructure level via a global interceptor that runs after authentication succeeds. Each entry captures the HTTP method, path, response status, latency, the request ID for cross-referencing support tickets, and — when a request was made with an API key — which key was used.

## What gets logged

Every request to `/v1` that passes authentication is recorded. The only exceptions are the request-log endpoints themselves (`GET /v1/request-log`, `GET /v1/request-log/stats`, `GET /v1/request-log/export`) — reading the log does not append to it. Unauthenticated requests that are rejected before auth resolves are not logged.

## Retention

Log entries are kept for **30 days** and then deleted automatically. If you need a permanent record, export the data before it ages out (see [Exporting entries](#exporting-entries) below).

## Endpoints

### List entries — `GET /v1/request-log`

Returns a paginated list of log entries for the active workspace, newest first. Use this to build a custom audit view or to inspect traffic programmatically.

**Query filters**

| Parameter   | Type     | Description                                                              |
| ----------- | -------- | ------------------------------------------------------------------------ |
| `startTime` | ISO 8601 | Include entries at or after this timestamp.                              |
| `endTime`   | ISO 8601 | Include entries before or at this timestamp.                             |
| `status`    | integer  | Filter to a specific HTTP status code (e.g. `200`, `401`, `429`).        |
| `method`    | string   | Filter to a specific HTTP method: `GET`, `POST`, `PATCH`, `DELETE`, etc. |
| `apiKeyId`  | string   | Filter to requests made with a particular API key ID.                    |
| `search`    | string   | Full-text filter across the path field.                                  |
| `offset`    | integer  | Number of entries to skip. Defaults to `0`.                              |
| `limit`     | integer  | Page size. Maximum `1000`. Defaults to `50`.                             |

### Summary statistics — `GET /v1/request-log/stats`

Returns aggregated counts and a time-series breakdown for the filtered window. Useful for rendering a traffic graph or a quick health summary on the dashboard. Accepts the same filter parameters as the list endpoint.

### Export — `GET /v1/request-log/export`

Streams the filtered result set as a CSV file (`Content-Disposition: attachment; filename="request-log.csv"`). Columns are: Time, Method, Path, Status, Latency (ms), API key, Request ID. Use this to pull data into a spreadsheet, SIEM, or external analytics pipeline. Accepts the same filter parameters as the list endpoint.

## Session-only access

All three request-log endpoints require an active browser session. **They cannot be called with an API key.** Attempts to access the log via a Bearer token return `403 session_required`. This is intentional — the request log includes metadata about every key in the workspace, so reading it is scoped to interactive dashboard users who have already authenticated as organization members.

## Related

* [API keys overview](/api-reference/api-keys/overview) — understand which key generated which traffic.
* [Authentication](/api-reference/authentication) — session cookies, Bearer tokens, and error shapes.
* [GET /v1/request-log](/api-reference/request-log) — list entries.
* [GET /v1/request-log/stats](/api-reference/request-log) — time-series stats.
* [GET /v1/request-log/export](/api-reference/request-log) — download as CSV.