Skip to main content
GET
List a tool's history
The reference panel describes the current v3 operation. The notes below describe its v2 compatibility API. Follow the v3 request schema for current calls: v3 can move identifiers from the body or query into the URL. Keep the v2 method, path, and payload together when using the compatibility API.

v2 compatibility notes

GET /api/v2/tools/listAuditHistory?id=<toolId>&cursor=&limit= pages a tool’s history, newest first, as the tool detail page’s History tab does.

Authority

You need agents:read at the platform scope. A missing, draft or archived tool answers 404 resource_missing; an unavailable store is a 500, never a 404. A repeated or out-of-range parameter is 400 bad_request.

What it returns

Each event carries its id, event, category, actorType (the kind of actor) and timestamp. Who acted and the event’s detail are never returned. Follow meta.nextCursor while meta.hasMore is true; a malformed cursor is 400 bad_request, never a restart. limit is 1-100 (default 50).

Authorizations

Authorization
string
header
required

An External App: the JWT it obtains from POST /oauth/token with OAuth2 client_credentials. Pass as Authorization: Bearer <jwt>. An app's static companion key also authenticates as the app, but is deprecated and is not protected by Idempotency-Key.

Path Parameters

toolId
string
required

The tool's id or slug.

Minimum string length: 1

Query Parameters

cursor
string
limit
integer
default:50

Events to return, 1-100. Default 50.

Required range: 1 <= x <= 100

Response

List a tool's history

data
object[]
required
meta
object
required

A list page's continuation. While hasMore is true, nextCursor is a string: pass it as cursor for the next page. hasMore: false ends the list; with truncated: true, more exist past what this list reads, and no cursor reaches them.