List audit logs
List your Runpod audit trail to see who acted on each resource, with filters for actor, action, time range, and text, newest first.
Authorizations
Runpod API key authentication. Generate an API key in the Runpod console and send it in the Authorization header as Bearer <api_key>. Keys are scoped to the permissions granted when created; requests may return 403 when a valid key lacks access to the requested resource or action.
Console sessions (Clerk JWTs) act for the signed-in user. To act for a team instead, also send X-Team-Id: <team_id>; it applies only when the user owns or belongs to that team, otherwise the request runs against the user's own account. API keys created inside a team already act for that team and do not need the header.
Query Parameters
Only return entries performed by these users. Comma-separated user IDs. Available to organization accounts only; a personal or team account is answered 400.
Only return entries whose action is one of these names, matched exactly as recorded. Comma-separated.
Earliest instant to include, inclusive (RFC 3339). The account's audit log retention window still applies: entries that have aged out are not returned even when this reaches further back.
Latest instant to include, inclusive (RFC 3339). Must be after startTime when both are given; 400 otherwise.
Case-insensitive substring match against email, resourceType, resourceId, action and value; actorId is not searched. Surrounding whitespace is ignored.
1Opaque resume cursor — pass the previous response's pagination.nextCursor through verbatim; omit for the first page. A cursor is only valid for the operation and parameters that issued it; a malformed or foreign cursor is rejected with 422.
1Page size, 1–200. Defaults to 200 when omitted.
1 <= x <= 200