Skip to main content
GET
List flow executions with filtering and pagination

Authorizations

Authorization
string
header
required

JWT Bearer token authentication. Include your access token in the Authorization header as: Bearer YOUR_ACCESS_TOKEN

Example:

Query Parameters

flow_id
string<uuid>
required

UUID of the flow to list executions for. Required parameter.

sort_field
string | null

Field to sort results by. Valid values: 'created_at', 'updated_at'. Defaults to 'created_at' for most recently modified first.

Pattern: ^(created_at|updated_at)$
sort_direction
string | null

Sort order direction. Valid values: 'asc' (ascending), 'desc' (descending). Defaults to 'desc' for newest first.

Pattern: ^(asc|desc)$
status
string[] | null

Filter by flow execution status. Can specify multiple values. Valid values: 'queued', 'running', 'completed', 'failed', 'stale', 'awaiting_input', 'cancel_requested', 'cancelled', 'edited', 'pending_payment'. Returns executions whose overall status matches ANY of the specified values. Example: ?status=failed&status=running

status_exclude
string[] | null

Exclude flow executions whose status matches any of these values. Mirrors tags/tags_exclude. Combines with status using AND. Example: ?status_exclude=queued hides queued runs from the result and total count.

tags
string[] | null

Filter by task tags. Can specify multiple values, connected by tags_mode. Tags use key:value format. Example: ?tags=priority:high&tags=env:prod

Maximum array length: 50
tags_mode
enum<string>
default:any

Connector between the tags values. 'any' (default) returns executions carrying at least one of them; 'all' returns executions carrying every tag, matched at run level so the tags may sit on different tasks. Example: ?tags=doc:invoice&tags=error:amount&tags_mode=all

Available options:
any,
all
page
integer
default:1

Page number for pagination (1-indexed). Minimum: 1, Maximum: 10,000. Works with page_size to implement offset-based pagination.

Required range: 1 <= x <= 10000
page_size
integer
default:10

Number of results to return per page. Minimum: 1, Maximum: 1000. Larger values increase response time. Recommended: 10-100.

Required range: 1 <= x <= 1000
start_from_execution_id
string<uuid> | null

Start listing after this execution ID. Provides cursor-like pagination. When combined with sort parameters, returns results after the specified execution. Useful for infinite scroll or keyset pagination patterns.

created_after
string<date-time> | null

Return executions created at or after this timestamp (inclusive). Accepts ISO 8601 (e.g. '2026-06-18T08:00:00Z'). Combined with other filters using AND.

created_before
string<date-time> | null

Return executions created at or before this timestamp (inclusive). Accepts ISO 8601 (e.g. '2026-06-18T10:00:00Z'). Combined with other filters using AND.

updated_after
string<date-time> | null

Return executions last updated at or after this timestamp (inclusive). Accepts ISO 8601. Combined with other filters using AND.

updated_before
string<date-time> | null

Return executions last updated at or before this timestamp (inclusive). Accepts ISO 8601. Combined with other filters using AND.

include_credits
boolean
default:false

Include total credits consumed by each execution in the response. When false (default), total_credits is null and the usage table is not queried. Adds a single bulk usage-table lookup for the page when enabled.

Response

List of flow executions successfully retrieved

created_at
string<date-time>
required
flow_id
string<uuid>
required

UUID of the flow definition being executed. References the parent flow that defines the workflow structure.

Example:

"550e8400-e29b-41d4-a716-446655440000"

flow_version
integer
required

Version number of the flow definition used for this execution. Execution continues on the same version even if flow is updated. Ensures consistency throughout execution lifecycle.

Required range: x >= 1
Example:

3

id
string<uuid>
required
input
Input · object
required

Input data provided when execution was created. Schema is defined by the flow definition. Commonly includes: file_key, document_url, or custom parameters. Structure varies by flow type.

Example:
modified_by
string
required
organization_id
string<uuid>
required

UUID of the organization that owns this execution. Used for access control and data isolation. All executions are scoped to an organization.

Example:

"660e8400-e29b-41d4-a716-446655440001"

status
enum<string>
required

Current execution status. Possible values: 'queued', 'running', 'completed', 'failed', 'deleted', 'stale', 'edited', 'awaiting_input', 'cancel_requested', 'cancelled', 'pending_payment'. Status transitions: queued → running → completed/failed. 'pending_payment' means the execution is held until the organization's credits are restored, then released back to 'queued' automatically.

Available options:
queued,
running,
completed,
failed,
deleted,
stale,
edited,
awaiting_input,
cancel_requested,
cancelled,
pending_payment
Example:

"running"

updated_at
string<date-time>
required
idempotency_key
string | null

Idempotency key this execution was created with: the Idempotency-Key request header when the caller sent one, otherwise a ULID generated by super.AI. Sending a create request for the same flow with this key again returns this execution with 201, in its current state, instead of creating or starting a new one. Null only for executions created before idempotency keys existed.

Example:

"01ARZ3NDEKTSV4RRFFQ69G5FAV"

pricing_config_id
string<uuid> | null

UUID of the pricing config active when this execution was created or re-executed. References the default config if no org-specific config existed at that time. None for executions created before pricing config tracking was introduced.

status_data
AwaitingInputStatusData · object

status_data of a flow execution whose status is awaiting_input.

Example:
total_credits
integer | null

Total credits consumed by this flow execution across all tasks. None when no usage records exist yet.

Example:

42

triggered_task_executor_name
string | null

Executor name of the trigger that fired this execution (e.g., 'receive_file'). Set for multi-input flows; None for single-input-task flows.