Super.ai task-executions API
Task execution operations for tracking individual task runs within flow executions.Task executions represent individual task runs within a flow execution. Each task in a flow execution has its own task execution record that tracks its lifecycle, inputs, outputs, and status.**What is tracked:**- **Status**: Current state (pending, running, completed, failed, skipped)- **Input/Output**: Data passed to and produced by the task- **Timing**: Start time, end time, and duration- **Errors**: Failure details and error messages- **Tags**: Metadata and categorization**Use these endpoints to:**- Query task execution status for debugging- Retrieve task outputs for analysis- Debug task failures with detailed error information- Track task performance and timing- Monitor task execution progress within flowsTask executions provide granular visibility into workflow execution, essential for debugging and optimization.
Super.ai task-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 Task Executions. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, and authentication docs.
This API exposes 4 operations across 2 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.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 2
Super.ai task-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 4
Across 2 paths, the API surfaces 4 operations — 2 GET, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.
Task execution operations for tracking individual task runs within flow executions. Task executions represent individual task runs within a flow execution. Each task in a flow exe…
Schemas 12
The contract defines 12 schemas that model the data the API accepts and returns. The most detailed are TaskExecutionWithTagsAPI (19 properties), TaskExecutionAPI (18 properties), CreateTaskExecutionRequest (11 properties), FlowTaskTagAPI (11 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Super.ai 12
Other APIs Super.ai publishes across the network.
This is an independent, third-party profile of Super.ai task-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.