Runs
List references to the files a run produced
List references to the files a run produced. Requires permission runs:read.
GET
List references to the files a run produced
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
References, not content
Each item names one file a run you may read produced:fileId, filename, mimeType, and, when recorded, sizeBytes, the producing nodeId, the output fieldName and version. No URL or storage reference is returned. Fetch the bytes with GET /api/v2/files/content?id=<fileId>, which needs files:read and applies its own rule, so you may see a reference you cannot download.
A file is listed when you also hold runs:read at every company on it. The list pages at the database, oldest first: limit is 1 to 100 (default 100), and while meta.hasMore is true you pass meta.nextCursor as cursor. A page may hold fewer references than limit while more follow, because a file you may not read is left out. Every reference is listed, with no read cap, so meta.partial is always false. A run you cannot read answers 404 like a missing one.Authorizations
Query Parameters
Response
The run's file references

