Download results and access media

Once an execution reaches a terminal success state, switch from execution monitoring to these output-oriented APIs.

Output access model

Result endpoints

Need	Endpoint	Use it when…
Inspect availability	`GET /api/v1/executions/:id/results`	You want metadata before downloading
Download CSV	`GET /api/v1/executions/:id/results/download`	You want a flat file export
Export JSON or CSV	`GET /api/v1/executions/:id/results/export`	You want explicit export control
Inspect datasets	`GET /api/v1/executions/:id/datasets`	You want dataset-level output metadata

Read result metadata

Start with:

curl "$TITAN_API_URL/api/v1/executions/$EXECUTION_ID/results" \
  -H "Authorization: Bearer $TITAN_TOKEN"

This is useful for:

Confirming output exists
Checking format and timing metadata
Deciding whether to export or inspect datasets next

Export JSON

curl "$TITAN_API_URL/api/v1/executions/$EXECUTION_ID/results/export" \
  -H "Authorization: Bearer $TITAN_TOKEN"

Download CSV

curl "$TITAN_API_URL/api/v1/executions/$EXECUTION_ID/results/download" \
  -H "Authorization: Bearer $TITAN_TOKEN" \
  -o results.csv

Access datasets

Datasets are especially useful for recurring tasks and multi-run analysis:

# Datasets for an execution
curl "$TITAN_API_URL/api/v1/executions/$EXECUTION_ID/datasets" \
  -H "Authorization: Bearer $TITAN_TOKEN"

# Datasets for a task (across all executions)
curl "$TITAN_API_URL/api/v1/tasks/$TASK_ID/datasets" \
  -H "Authorization: Bearer $TITAN_TOKEN"

Media-aware outputs

When an output schema includes media fields, Titan stores media through ingestion and exposes stable platform URLs in the result data.

Why Titan uses stable media URLs

Platform behavior	Benefit
Media is uploaded through a commit flow	Avoids raw object-store coupling
Result payloads contain stable Titan URLs	Makes result payloads durable
Downloads are resolved through Titan endpoints	Enforces access control and ownership

Download media directly

curl "$TITAN_API_URL/api/v1/executions/$EXECUTION_ID/media/$MEDIA_ID/download" \
  -H "Authorization: Bearer $TITAN_TOKEN" \
  -o media-file.png

Recommended consumption pattern

Poll until the execution is completed
Fetch result metadata
Export JSON or CSV for structured data
Resolve media only in the application layer that needs it

This approach keeps storage concerns out of your main data pipeline.

Troubleshooting

Problem	Check first
Result endpoint returns nothing useful	Ensure the execution is fully completed
CSV or JSON export fails	Confirm you are using a result endpoint, not an execution endpoint
Media URL does not display in a browser	Use the platform download path or the correct export mode
Datasets are missing	Check whether the task or execution produced dataset outputs

Get started

Use cases

Action types

About the platform

Use the platform

Dashboard and operations

Worker guides

Output access model

Result endpoints

Read result metadata

Export JSON

Download CSV

Access datasets

Media-aware outputs

Why Titan uses stable media URLs

Download media directly

Recommended consumption pattern

Troubleshooting

Next steps

​Output access model

​Result endpoints

​Read result metadata

​Export JSON

​Download CSV

​Access datasets

​Media-aware outputs

​Why Titan uses stable media URLs

​Download media directly

​Recommended consumption pattern

​Troubleshooting

​Next steps

Output access model

Result endpoints

Read result metadata

Export JSON

Download CSV

Access datasets

Media-aware outputs

Why Titan uses stable media URLs

Download media directly

Recommended consumption pattern

Troubleshooting

Next steps