List executions
Retrieve execution history for the authenticated API key’s organization
with optional filters.
Model prediction terminal statuses include success, error, and cancelled;
workflow executions can surface running, completed, failed, or cancelled
depending on the originating backend. The status filter accepts the
four tokens listed on the parameter; unrecognized tokens return 400.
Results cover every API key in the organization that owns the authenticated key.
Pagination: computing an exact total over a large execution history is
expensive, so total_count is capped. When the response sets
total_capped: true, total_count is a lower bound, not the exact
total. To retrieve every matching execution, keep requesting pages
(increasing offset by limit) until a page returns fewer than
limit rows — do not stop paging when offset reaches total_count.
When from is omitted, the window defaults to the 90 days ending at
to (or now).
Authorizations
API key passed as an Authorization Bearer token: Authorization: Bearer YOUR_API_KEY
Query Parameters
Maximum number of executions to return
1 <= x <= 100Number of executions to skip for pagination
x >= 0Filter executions by model slug
Comma-separated status filter. Each token must be one of created,
starting, success, or error (lowercase); any other token
returns 400 naming the allowed set. An empty or absent parameter
applies no status filter.
Filter by workflow ID
Filter by workflow execution ID
Comma-separated canonical error classification filter. Restricts results to terminal error executions whose classification is in the set; an unrecognized value returns 400. Each value must be one of the listed enum members.
content_moderation, execution_timeout, invalid_user_input, invalid_model_config, provider_auth, provider_error, provider_rate_limit, provider_unavailable, internal_error, unknown Start of creation time window, as RFC 3339. When omitted, defaults to 90 days before to (or before now when to is also omitted).
End of creation time window, as RFC 3339
Response
List of executions
Number of matching executions. When total_capped is true this is a lower bound, not the exact total — do not use it as a pagination stop condition; keep increasing offset until a page returns fewer than limit rows. On the last page that returns rows, the exact total is reported and total_capped becomes false.
123
true when the server did not compute the exact count (the count is capped, or its time budget elapsed) and total_count is a lower bound — more matching executions may exist beyond it.
false
Applied offset
0
Applied limit
20