Super.ai task-outputs API
Task output operations for storing and retrieving task execution results.Task outputs store the results produced by task executions in a structured, queryable format. While task executions track the full lifecycle (input, output, error, status), task outputs focus specifically on the final output data formatted for display, analysis, and downstream consumption.**Key characteristics:**- **Summary Field**: Structured output data ready for consumption- **Historical Record**: Permanent storage of task results- **Queryable**: Filter and search outputs by task, execution, or flow- **Linked**: Connected to parent flow execution and task execution**Use these endpoints to:**- Store task results after successful execution- Retrieve outputs for specific tasks or entire executions- Query historical outputs for analysis and reporting- Access formatted results for display in dashboards- Feed outputs to downstream tasks or external systemsTask outputs provide the data foundation for workflow analytics, debugging, and result visualization.
Super.ai task-outputs 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-outputs. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, and authentication docs.
This API exposes 3 operations across 2 paths, and defines 8 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-outputs 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 3
Across 2 paths, the API surfaces 3 operations — 2 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.
Task output operations for storing and retrieving task execution results. Task outputs store the results produced by task executions in a structured, queryable format. While task…
Schemas 8
The contract defines 8 schemas that model the data the API accepts and returns. The most detailed are TaskOutputAPI (15 properties), TaskOutput (14 properties), ErrorDetail (3 properties), ErrorResponse (2 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-outputs 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.