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

Authorizations

X-API-Key
string
header
required

API key authentication. Include your API key in the X-API-Key header as: X-API-Key YOUR_API_KEY

Example:

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 execution status. Can specify multiple values. Valid values: 'queued', 'running', 'in_progress', 'completed', 'failed', 'stale'. Returns executions containing tasks with ANY of the specified statuses. Example: ?status=failed&status=running

tags
string[] | null

Filter by task tags. Can specify multiple values. Returns executions containing tasks with ANY of the specified tags. Tags use key:value format. Example: ?tags=priority:high&tags=env:prod

include_run_number
boolean
default:false

Calculate sequential run number for each execution. Run numbers start at 1 and increment based on creation time. Warning: Adds performance overhead (~150ms per 100 executions). Recommended only for UI display purposes.

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.

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
string
required

Current execution status. Possible values: 'queued', 'running', 'in_progress', 'completed', 'failed', 'deleted', 'stale'. Status transitions: queued → running → in_progress → completed/failed. Use 'completed' to indicate success, 'failed' for errors.

Example:

"running"

updated_at
string<date-time>
required
run_number
integer | null

Sequential run number for this execution within its flow. Starts at 1 for the first execution and increments by creation time. Includes deleted executions in count, so visible numbers may have gaps. Only populated when include_run_number=true query parameter is set. Null when not requested to avoid performance overhead.

Required range: x >= 1
Example:

42