Skip to main content
GET
Find the tool call that produced a run's file
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

Returns the completed tool call that produced one of the run’s output files, on the step that output it: the call whose output names the file (a call that stores a file binds it while it runs), else a call that finished no later than the file was bound. It carries toolName, commandId, stepId, status, timing, inputSummary, outputSummary, input, output, error and governanceDisposition; never the call’s trace, agent, session, message or token usage. fileId is a file id GET /api/v2/runs/listArtifacts returns. A file the run did not output, a file carrying a company you cannot read, and a producer outside the run’s 50 newest tool calls (the window the Console searches) answer 404 “Artifact not found”.

Runtime content

Outputs, stdout, errors, tool input and output and validator snapshots are returned as the run recorded them, except that credential-shaped strings (JWTs, Bearer tokens, x-access-token: URLs and GitHub tokens) are replaced by a [REDACTED] marker. A human step’s outputs, and the outputs its validator passes received, never carry completedBy, completedVia or response: who answered, the channel and the person’s free text. No field names who acted, answered, was notified or repaired, and no answer carries a credential or where it is stored, an agent thread, a storage handle or the run’s company list; runtime content is returned as recorded, so it may mention anything the run itself wrote.

Visibility

You need runs:read at the run’s home (its own org unit, else its workflow’s owning org unit) and at every company it carries, the same rule as GET /api/v2/runs/get. Any other run, and a run with neither home, answers 404 “Run not found” like a missing one. A Personal key reads as its owner, cut down to the key’s scopes; an External App reads by its own role grants.

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

runId
string
required

The run id.

Minimum string length: 1
fileId
string
required

The run's output file id.

Minimum string length: 1

Response

The producing tool call

data
object
required
meta
object
required