How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Super.ai flow-executions API

Flow execution operations for running and monitoring workflows.Flow executions represent runtime instances of flows. When you execute a flow, a new flow execution is created with its own unique ID, status, and execution context. Each execution is independent and maintains its own state, input data, and results.**Key concepts:**- **Execution Status**: Tracks the lifecycle (running, completed, failed, cancelled)- **Run Number**: Sequential identifier for executions of the same flow- **Execution Context**: Contains input parameters, user information, and metadata- **Task Results**: Stores outputs from each task within the execution**Use these endpoints to:**- Start new flow executions with custom input parameters- Monitor execution progress and status in real-time- Retrieve execution history and detailed results- Filter and search executions by status, date, or flow- Cancel running executions when needed- Access task-level execution details and outputsFlow executions transform flow definitions into actual work and deliverable results.

Super.ai flow-executions API is one of 19 APIs that Super.ai publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include flow-executions. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, and authentication docs.

This API exposes 8 operations across 6 paths, and defines 12 schemas. It is described by OpenAPI 3.2.0, at version 0.1.0.

Requests are made against a single base URL, https://flows.super.ai/api.

8 operations 6 paths 12 schemas 1 DELETE2 GET1 PATCH4 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
0.1.0
Base URL
https://flows.super.ai/api
Authentication
HTTP Bearer, API Key
Resource Areas
1

Authentication & Security 2

Super.ai flow-executions API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT) (BearerAuth). An API key is passed in the header as X-API-Key (APIKeyAuth).

  • BearerAuth — JWT Bearer token authentication. Include your access token in the Authorization header as: Bearer YOURACCESSTOKEN Example: Authorization: Bearer eyJhbGciOiJIUz…
  • APIKeyAuth — API key authentication. Include your API key in the X-API-Key header as: X-API-Key YOURAPIKEY Example: X-API-Key: saf1234567890

Paths & Operations 8

Across 6 paths, the API surfaces 8 operations — 1 DELETE, 2 GET, 1 PATCH, 4 POST. Each is listed below with its method, path, parameters, and response codes.

flow-executions 8

Flow execution operations for running and monitoring workflows. Flow executions represent runtime instances of flows. When you execute a flow, a new flow execution is created with…

POST
/api/flow-executions
Create and start a flow execution
create_flow_execution_api_flow_executions_post body → 201400403401402404500422
GET
/api/flow-executions
List flow executions with filtering and pagination
list_flow_executions_api_flow_executions_get 15 params → 200400403404422500
DELETE
/api/flow-executions/{flow_execution_id}
Soft delete a flow execution
delete_flow_execution_api_flow_executions__flow_execution_id__delete 1 param → 204403404500422
GET
/api/flow-executions/{flow_execution_id}
Retrieve a specific flow execution
get_flow_execution_api_flow_executions__flow_execution_id__get 3 params → 200400403404500422
POST
/api/flow-executions/{flow_execution_id}/cancel
Cancel a flow execution
cancel_flow_execution_api_flow_executions__flow_execution_id__cancel_post 1 param → 204404500422
POST
/api/flow-executions/{flow_execution_id}/execute
Re-execute a flow execution
execute_flow_api_flow_executions__flow_execution_id__execute_post 2 params → 204403409404500422
POST
/api/flow-executions/{flow_execution_id}/task-status
Add task status updates (Internal API)
add_flow_task_statuses_api_flow_executions__flow_execution_id__task_status_post 1 param body → 200400403404500422
PATCH
/api/flow-executions/{flow_execution_id}/status
Patch Flow Execution Status
patch_flow_execution_status_api_flow_executions__flow_execution_id__status_patch 2 params → 200422

Schemas 12

The contract defines 12 schemas that model the data the API accepts and returns. The most detailed are FlowExecutionResponseWithRunNumber (13 properties), FlowExecutionResponse (12 properties), FlowTaskStatusAPI (6 properties), ErrorDetail (3 properties). Each schema is shown below with its type and property counts.

FlowExecutionResponse
object
Response model for flow execution operations. Represents a single flow execution instance with its current state and metadata. Flow executions are runtime inst…
12 properties 9 required
AddTaskStatusRequestItem
object
Single task status update in a batch request. Represents one task's status change within a flow execution. Used by system workers to report task execution prog…
2 properties 1 required
ErrorDetail
object
Standard error detail structure. This model matches the error format returned by the centralized exception handlers in app/api/errors/handlers.py.
3 properties 1 required
ExecutionStatus
string
Valid status values for flow execution lifecycle. Status Transitions: queued → running → completed → failed running/awaitinginput → cancelrequested → cancelled…
FlowTaskStatusAPI
object
API model for FlowTaskStatus.
6 properties 5 required
ErrorResponse
object
Standard API error response structure. All error responses from the API follow this format, ensuring consistent error handling for API consumers. Example: { "e…
2 properties 1 required
FlowExecutionResponseWithRunNumber
object
Flow execution response with optional sequential run number. Extends FlowExecutionResponse to include an optional runnumber field that indicates the sequential…
13 properties 9 required
ProcessingStatus
string
Valid status values for task processing lifecycle. Used by taskexecution and taskoutput tables to track where a task is in its processing pipeline, independent…
ValidationError
object
3 properties 3 required
HTTPValidationError
object
1 property
FlowExecutionCreateRequest
object
Request payload for creating a new flow execution. This model defines the required data to start a new flow execution. The input schema must match the flow def…
3 properties 2 required
AddTaskStatusRequest
object
Batch request to add multiple task status updates. Allows system workers to report status changes for multiple tasks in a single API call for improved performa…
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

superai-flow-executions-api-openapi.yml Raw ↑

Other APIs Super.ai publishes across the network.

Super.ai auth API
Super.ai files API
Super.ai flows API
Super.ai human-review-tasks API
Super.ai integrations API
Super.ai models API
Super.ai organizations API
Super.ai plugins API
Super.ai profile API
Super.ai service-accounts API
Super.ai sso API
Super.ai task-data API
Where this information came from

This is an independent, third-party profile of Super.ai flow-executions API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.