Skip to main content
The Logs API returns individual tool execution events, one record per tool call. Use it to debug failures, inspect request/response payloads, and trace specific user activity. For aggregated counts (how many tool calls happened), use the Usage API instead. All endpoints in this section require a project API key (x-api-key) or a valid session cookie.

List logs

The response contains a page of log entries and a next_cursor:
Pass next_cursor back as cursor on the next request to paginate. When next_cursor is null, you’ve reached the end.

Filter fields

Pass one or more filters in the filters array. Filters are AND-combined.

Operators

Parameters

Get a single log

Fetch one log by ID to get the full payload, including request/response bodies, timing breakdowns, and source metadata:
The detail response includes everything from the list shape plus:
  • timings: start_time and end_time in epoch ms
  • context: session_id, trace_id, request_id
  • source: host (e.g. mcp, sdk, api), framework, language
  • data: the full request payload and response body
This is the endpoint to call when you need to reconstruct exactly what happened, for example when debugging a 500 from a user report.

Recipes

Find failed Gmail tool calls in the last hour

Get failures for a specific user

Fetch a single log’s full request/response