Skip to main content
GET
/
flows
/
runs
/
{flow_run_uid}
/
outputs
Get outputs by Flow Run UUID
curl --request GET \
  --url https://api.edges.run/v1/flows/runs/{flow_run_uid}/outputs \
  --header 'X-API-Key: <api-key>'
[
  {}
]
Retrieve the outputs (results) produced by a flow run. This endpoint allows you to access the actual data extracted or enriched by the flow, with support for pagination and filtering by step. Use Cases:
  • Retrieve results from a completed flow run
  • Access data as it’s being generated (for long-running flows)
  • Filter outputs by specific steps in the workflow
  • Paginate through large result sets
Examples: 
# First 100 results
curl --request GET \
  --url 'https://api.edges.run/v1/flows/runs/550e8400-e29b-41d4-a716-446655440000/outputs?limit=100&offset=0' \
  --header 'X-API-Key: <your-api-key>'

# Next 100 results
curl --request GET \
  --url 'https://api.edges.run/v1/flows/runs/550e8400-e29b-41d4-a716-446655440000/outputs?limit=100&offset=100' \
  --header 'X-API-Key: <your-api-key>'
If you want to retrieve only outputs from a specific step (e.g., only enrichment results):
curl --request GET \
  --url 'https://api.edges.run/v1/flows/runs/550e8400-e29b-41d4-a716-446655440000/outputs?step_uid=660e8400-e29b-41d4-a716-446655440001' \
  --header 'X-API-Key: <your-api-key>'
For better performance with large result sets, use webhooks (callback URLs) when creating flow runs. This way, results are automatically sent to your endpoint as they’re generated, eliminating the need to poll.

Authorizations

​
X-API-Key
string
header
required

Path Parameters

​
flow_run_uid
string<uuid>
required

Flow Run UUID

Query Parameters

​
limit
integer
default:100
Required range: 1 <= x <= 1000
​
offset
integer
default:0
Required range: x >= 0
​
step_uid
string | null

Output Step UID to filter outputs

Response

Returns the flow run outputs