Workflows
List a debug attempt's tool calls
Read the tool calls a debug attempt made.
GET
List a debug attempt's tool calls
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/workflows/listDebugToolCalls
Returns the attempt’s tool calls, newest first, a page at a time, with their input and output summaries and governance outcome; an error is cut to 500 characters. Never the calling agent.
Authentication
Personal key, External App credential or platform API key. Requires permissionworkflows:use, and the credential’s scopes must also reach workflows:read (a 403 naming it otherwise). Both are decided at the workflow’s home org unit. A debug attempt is personal, as in the Console: you debug drafts you created and read attempts you started. With a Personal key that is its owner; an External App or a platform key is its own creator (externalApp:<id>, apiKey:<id>). When draft debugging (workflow_debug_execution) is off for you (a Personal key’s owner) or for the deployment (an app or platform key), the route answers 409 conflict.
Query parameters
Responses
200 with data.toolCalls. While meta.hasMore is true, pass meta.nextCursor as cursor with the same other parameters for the next page. A page may hold fewer tool calls than limit while more remain; the list never answers meta.partial.
Errors
Example
Authorizations
Path Parameters
Query Parameters
Response
The attempt's tool calls

