Skip to main content
GET
/
runs
/
{run_uid}
/
outputs
Get outputs by Run UUID
curl --request GET \
  --url https://api.edges.run/v1/runs/{run_uid}/outputs \
  --header 'X-API-Key: <api-key>'
[
  {}
]

Documentation Index

Fetch the complete documentation index at: https://docs.edges.run/llms.txt

Use this file to discover all available pages before exploring further.

This endpoint is not available for runs executed in live mode. It only works for runs executed in async or schedule mode. For live mode runs, results are returned directly in the API response.

​
Pagination

This endpoint uses cursor-based pagination by default. Follow the X-Pagination-Next response header to retrieve subsequent pages.
  • limit controls the page size (default: 100, max: 500).
  • The X-Pagination-Next header contains the full URL for the next page, including limit and cursor.
  • When the X-Pagination-Next header is absent, there are no more pages.
# First request
curl -X GET "https://api.edges.run/v1/runs/{run_uid}/outputs?limit=200" \
  -H "Accept: application/json" \
  -H "X-API-Key: <YOUR_API_KEY>"

# Follow X-Pagination-Next header for subsequent pages
curl -X GET "https://api.edges.run/v1/runs/{run_uid}/outputs?limit=200&cursor=<cursor_value>" \
  -H "Accept: application/json" \
  -H "X-API-Key: <YOUR_API_KEY>"
The offset parameter is deprecated. If provided, the system falls back to offset-based pagination and cursor pagination is not used. Prefer following the X-Pagination-Next URL for all new integrations.

​
Rate Limits

​
Run’s Routes Limits

To date, all /runs/xxx routes are subject to the same limit (e.g., 30 requests/minute for TRIAL plans). We are working to refine these quotas per endpoint (status, output, etc.) to better match usage patterns. Plans and limits will be updated in the documentation as soon as these changes take effect.
Plan TierMax Requests/SecondMax Requests/MinuteRationale
Trial< 130Supports 2 concurrent runs @ 10s polling interval
Bronze160Supports 2 concurrent runs with more aggressive polling
Silver / Gold2.5150Supports 5 concurrent runs @ 10s polling interval
Platinum / Diamond5300Supports 10 concurrent runs @ 10s polling interval
Titanium10600Supports 15 concurrent runs @ 10s polling interval
Rate limits for polling run results via /v1/runs/{run_uid}/outputs. These limits support realistic polling patterns for customers who prefer polling over callbacks.
These limits are aligned with concurrent execution limits. For example, with a Silver/Gold plan (5 concurrent runs), you can poll all active runs every 10 seconds with comfortable headroom.

​
Capacity Examples

Plan TierPolling CapacityUse Case
TrialPoll 2 runs every 10sBasic polling during development
BronzePoll 2 runs every 10s with headroomSmall-scale polling
Silver / GoldPoll 5 runs every 10s, or 1 run every 4sTeam polling operations
Platinum / DiamondPoll 10 runs every 10sMulti-workspace polling
TitaniumPoll 15 runs every 10sEnterprise-scale polling
Implementation Details:
  • Rate limit type: Per-workspace, per-minute
  • Error response: Standard 429 with X-RateLimit-Type: /v1/runs/outputs
  • Headers include X-RateLimit-Remaining for visibility

Authorizations

​
X-API-Key
string
header
required

Path Parameters

​
run_uid
string<uuid>
required

Run UUID

Query Parameters

​
limit
integer
default:100

Number of outputs to return

Required range: 1 <= x <= 500
​
offset
integer | null
deprecated

(deprecated) Number of outputs to skip for pagination

Required range: x >= 0
​
cursor
string

(optional) Cursor value obtained from the X-Pagination-Next response header of a previous request, used to continue pagination. If not provided, the first page will be returned.

Response

Returns the run outputs