Fetch a user submitted file (image or audio) for a given Task Run

Fetch an individual Task Run file. This endpoint retrieves files associated with a task run, such as: - Input images or audio files submitted for processing - Output images, audio, PDFs, or CSV files generated by the task The file is served with appropriate content type headers for inline viewing or download based on the `inline` parameter. `file_name` is the `stored_filename` from the run's `files` array, not the name the caller uploaded. Each entry there also carries a ready-made `download_url` for this endpoint. The response carries the stored file's own content type — a `.txt` attachment comes back as `text/plain`, not as an opaque byte stream — and a `Content-Disposition` header naming the stored file.

Authentication

AuthorizationBearer

API key or access token, sent as Authorization: Bearer <token>. The simplest option: create an API key in your dashboard under Settings, then paste it here.

OR
AuthorizationBearer

API key or access token, sent as Authorization: Bearer <token>. The simplest option: create an API key in your dashboard under Settings, then paste it here.

Path parameters

org_idstringRequiredformat: "uuid"
The unique identifier of the organization.
project_idstringRequiredformat: "uuid"
The unique identifier of the project.
task_idstringRequiredformat: "uuid"
The specific Task to reference.
task_run_idstringRequiredformat: "uuid"
The specific Task Run to reference.
file_namestringRequired
The stored file name to fetch.

Query parameters

inlinebooleanOptionalDefaults to false
If true, serve file inline instead of as attachment

Response headers

Content-DispositionstringOptional

attachment; filename="<stored_filename>", or inline; filename="<stored_filename>" when inline=true.

Content-TypestringOptional
The stored file's own media type.

Response

File content returned successfully

Errors

400
Bad Request Error
403
Forbidden Error
404
Not Found Error
422
Unprocessable Entity Error