List Api Events
Cursor-paginated activity log for the caller’s team.
Role-scoped identically to GET /v1/usage: admins/owners see every
row in the team, members see only rows attributable to their own API
keys plus their own MCP-origin rows. Sort is (timestamp DESC, id DESC); iterate next_cursor until null to drain.
Authorizations
API key from Settings > Developer > REST API
Headers
Calendar-dated API version pin. New integrations should pin 2026-05-01 to opt into the newest response shapes. For back-compat the server also accepts requests with no header and resolves them to the current default (today: 2026-04-12); that default advances on each sunset date. Any unsupported value returns 400 unsupported_version.
2026-04-12, 2026-05-01 "2026-05-01"
Query Parameters
Optional API-key UUID filter.
Optional exact-match filter on the event's OpenAPI operationId.
Restrict to api or mcp origin rows.
api, mcp succeeded → 200-399; failed → status >= 400.
succeeded, failed ISO8601 UTC lower bound (inclusive). Defaults to to - 7d.
ISO8601 UTC upper bound (exclusive). Defaults to now.
Max rows per page (cap: 200).
1 <= x <= 200Opaque cursor from the previous page's next_cursor.
Response
Successful Response
Items in this page, in the endpoint's declared sort order.
Opaque cursor to pass as ?cursor= on the next request. null means you've reached the end of the collection.
Number of items in this page (always len(data); derived server-side).
true when more items exist beyond this page — keep requesting with next_cursor until this is false. Never trust len(data) < limit alone.
The effective page-size limit this response was computed with.
True total number of items in the collection (after filters), when the endpoint can count cheaply. null on log/search lanes — use has_more there.