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

​
Output access model

​
Result endpoints

NeedEndpointUse it when…
Inspect availabilityGET /api/v1/executions/:id/resultsYou want metadata before downloading
Download CSVGET /api/v1/executions/:id/results/downloadYou want a flat file export
Export JSON or CSVGET /api/v1/executions/:id/results/exportYou want explicit export control
Inspect datasetsGET /api/v1/executions/:id/datasetsYou 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 behaviorBenefit
Media is uploaded through a commit flowAvoids raw object-store coupling
Result payloads contain stable Titan URLsMakes result payloads durable
Downloads are resolved through Titan endpointsEnforces 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
  1. Poll until the execution is completed
  2. Fetch result metadata
  3. Export JSON or CSV for structured data
  4. Resolve media only in the application layer that needs it
This approach keeps storage concerns out of your main data pipeline.

​
Troubleshooting

ProblemCheck first
Result endpoint returns nothing usefulEnsure the execution is fully completed
CSV or JSON export failsConfirm you are using a result endpoint, not an execution endpoint
Media URL does not display in a browserUse the platform download path or the correct export mode
Datasets are missingCheck whether the task or execution produced dataset outputs

​
Next steps