Get task output by ID

curl --request GET \
  --url https://flows.super.ai/api/task-outputs/{task_output_id} \
  --header 'Authorization: Bearer <token>' \
  --header 'X-API-Key: <api-key>'

import requests

url = "https://flows.super.ai/api/task-outputs/{task_output_id}"

headers = {
    "X-API-Key": "<api-key>",
    "Authorization": "Bearer <token>"
}

response = requests.get(url, headers=headers)

print(response.text)

const options = {
  method: 'GET',
  headers: {'X-API-Key': '<api-key>', Authorization: 'Bearer <token>'}
};

fetch('https://flows.super.ai/api/task-outputs/{task_output_id}', options)
  .then(res => res.json())
  .then(res => console.log(res))
  .catch(err => console.error(err));

<?php

$curl = curl_init();

curl_setopt_array($curl, [
  CURLOPT_URL => "https://flows.super.ai/api/task-outputs/{task_output_id}",
  CURLOPT_RETURNTRANSFER => true,
  CURLOPT_ENCODING => "",
  CURLOPT_MAXREDIRS => 10,
  CURLOPT_TIMEOUT => 30,
  CURLOPT_HTTP_VERSION => CURL_HTTP_VERSION_1_1,
  CURLOPT_CUSTOMREQUEST => "GET",
  CURLOPT_HTTPHEADER => [
    "Authorization: Bearer <token>",
    "X-API-Key: <api-key>"
  ],
]);

$response = curl_exec($curl);
$err = curl_error($curl);

curl_close($curl);

if ($err) {
  echo "cURL Error #:" . $err;
} else {
  echo $response;
}

package main

import (
	"fmt"
	"net/http"
	"io"
)

func main() {

	url := "https://flows.super.ai/api/task-outputs/{task_output_id}"

	req, _ := http.NewRequest("GET", url, nil)

	req.Header.Add("X-API-Key", "<api-key>")
	req.Header.Add("Authorization", "Bearer <token>")

	res, _ := http.DefaultClient.Do(req)

	defer res.Body.Close()
	body, _ := io.ReadAll(res.Body)

	fmt.Println(string(body))

}

HttpResponse<String> response = Unirest.get("https://flows.super.ai/api/task-outputs/{task_output_id}")
  .header("X-API-Key", "<api-key>")
  .header("Authorization", "Bearer <token>")
  .asString();

require 'uri'
require 'net/http'

url = URI("https://flows.super.ai/api/task-outputs/{task_output_id}")

http = Net::HTTP.new(url.host, url.port)
http.use_ssl = true

request = Net::HTTP::Get.new(url)
request["X-API-Key"] = '<api-key>'
request["Authorization"] = 'Bearer <token>'

response = http.request(request)
puts response.read_body

{
  "flow_execution_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "organization_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "status": "<string>",
  "summary": "<unknown>",
  "task_name": "<string>",
  "created_at": "2025-01-24T10:30:00Z",
  "flow_version": 1,
  "modified_by": "system",
  "output": {
    "extracted_text": "Long document content...",
    "metadata": {
      "author": "John"
    }
  },
  "tags": [
    "priority:high",
    "customer:acme",
    "reviewed"
  ],
  "updated_at": "2025-01-24T10:35:00Z"
}

task-outputs

Get task output by ID

Retrieve a specific task output by its unique identifier.

Fetch a single task output record with complete output data, summary, tags, and metadata. Used for inspecting individual task results, debugging, and retrieving output for downstream processing.

Resource Identification

Task outputs are uniquely identified by UUID (id field). To find task outputs by other criteria (flow execution, task name), use GET /flow-executions/{id} or GET /task-outputs (list all).

What You’ll Get

summary: Structured task output summary for display
output: Full output data produced by task
tags: Associated metadata tags
status: Task execution state when output was created
Timestamps: created_at, updated_at for audit trail
Organization context: organization_id for multi-tenant isolation

Common Use Cases

Inspect task output for debugging or validation
Retrieve output data for manual review or corrections
Audit task execution history
Display detailed task results in UI

Related Endpoints

GET /task-outputs - List all task outputs
GET /flow-executions/{id} - View parent flow execution with all outputs
GET /task-executions/{id} - View full task execution details

GET

api

task-outputs

{task_output_id}

Get task output by ID

curl --request GET \
  --url https://flows.super.ai/api/task-outputs/{task_output_id} \
  --header 'Authorization: Bearer <token>' \
  --header 'X-API-Key: <api-key>'

import requests

url = "https://flows.super.ai/api/task-outputs/{task_output_id}"

headers = {
    "X-API-Key": "<api-key>",
    "Authorization": "Bearer <token>"
}

response = requests.get(url, headers=headers)

print(response.text)

const options = {
  method: 'GET',
  headers: {'X-API-Key': '<api-key>', Authorization: 'Bearer <token>'}
};

fetch('https://flows.super.ai/api/task-outputs/{task_output_id}', options)
  .then(res => res.json())
  .then(res => console.log(res))
  .catch(err => console.error(err));

<?php

$curl = curl_init();

curl_setopt_array($curl, [
  CURLOPT_URL => "https://flows.super.ai/api/task-outputs/{task_output_id}",
  CURLOPT_RETURNTRANSFER => true,
  CURLOPT_ENCODING => "",
  CURLOPT_MAXREDIRS => 10,
  CURLOPT_TIMEOUT => 30,
  CURLOPT_HTTP_VERSION => CURL_HTTP_VERSION_1_1,
  CURLOPT_CUSTOMREQUEST => "GET",
  CURLOPT_HTTPHEADER => [
    "Authorization: Bearer <token>",
    "X-API-Key: <api-key>"
  ],
]);

$response = curl_exec($curl);
$err = curl_error($curl);

curl_close($curl);

if ($err) {
  echo "cURL Error #:" . $err;
} else {
  echo $response;
}

package main

import (
	"fmt"
	"net/http"
	"io"
)

func main() {

	url := "https://flows.super.ai/api/task-outputs/{task_output_id}"

	req, _ := http.NewRequest("GET", url, nil)

	req.Header.Add("X-API-Key", "<api-key>")
	req.Header.Add("Authorization", "Bearer <token>")

	res, _ := http.DefaultClient.Do(req)

	defer res.Body.Close()
	body, _ := io.ReadAll(res.Body)

	fmt.Println(string(body))

}

HttpResponse<String> response = Unirest.get("https://flows.super.ai/api/task-outputs/{task_output_id}")
  .header("X-API-Key", "<api-key>")
  .header("Authorization", "Bearer <token>")
  .asString();

require 'uri'
require 'net/http'

url = URI("https://flows.super.ai/api/task-outputs/{task_output_id}")

http = Net::HTTP.new(url.host, url.port)
http.use_ssl = true

request = Net::HTTP::Get.new(url)
request["X-API-Key"] = '<api-key>'
request["Authorization"] = 'Bearer <token>'

response = http.request(request)
puts response.read_body

{
  "flow_execution_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "organization_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "status": "<string>",
  "summary": "<unknown>",
  "task_name": "<string>",
  "created_at": "2025-01-24T10:30:00Z",
  "flow_version": 1,
  "modified_by": "system",
  "output": {
    "extracted_text": "Long document content...",
    "metadata": {
      "author": "John"
    }
  },
  "tags": [
    "priority:high",
    "customer:acme",
    "reviewed"
  ],
  "updated_at": "2025-01-24T10:35:00Z"
}

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:

X-API-Key: saf_1234567890

Authorization

string

header

required

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

Example:

Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...

Path Parameters

task_output_id

string<uuid>

required

Unique identifier of the task output to retrieve. UUID assigned when task output was created. Task outputs are scoped to organization; attempting to access another organization's output returns 404.

Example:

"123e4567-e89b-12d3-a456-426614174000"

Response

Task output successfully retrieved

API model representing a task's output data.

Task outputs store the summarized, structured results of task executions. Unlike task executions which track the full lifecycle (input, output, error), task outputs focus on the final output data formatted for display, downstream consumption, and workflow decision logic.

Key Differences from Task Execution: - Task Execution: Full execution record with input, output, error, retries - Task Output: Summarized result optimized for querying and display - One task execution typically produces one task output upon completion

Resource Hierarchy: Organization → Flow → Flow Execution → Task Output

flow_execution_id

string<uuid>

required

ID of the parent flow execution containing this task. Establishes the execution hierarchy and organization scope.

Example:

"223e4567-e89b-12d3-a456-426614174000"

string<uuid>

required

Unique identifier for this task output. Auto-generated UUID assigned at creation time. Used for direct resource access via GET /task-outputs/{id}.

Example:

"123e4567-e89b-12d3-a456-426614174000"

organization_id

string<uuid>

required

ID of the organization owning this task output. Inherited from parent flow execution. Used for Row-Level Security (RLS) and multi-tenant isolation.

Example:

"323e4567-e89b-12d3-a456-426614174000"

status

string

required

Execution status when output was created. Valid values: 'queued', 'running', 'completed', 'failed', 'deleted', 'stale'. Typically 'completed' for successful task outputs.

Status meanings:

queued: Task scheduled but not started
running: Task actively executing
completed: Task finished successfully
failed: Task encountered error (may have partial output)
deleted: Soft-deleted, excluded from queries (preserves audit trail)
stale: Output data is outdated (needs refresh)

Examples:

"queued"

"running"

"completed"

"failed"

"deleted"

"stale"

summary

any

required

Structured summary of task output for UI display and querying. Typically a dictionary with standardized keys for rendering.

Common patterns:

Document processing: {'pages': 10, 'word_count': 5000}
API calls: {'status_code': 200, 'response_time_ms': 450}
Data validation: {'valid_rows': 950, 'invalid_rows': 50}

Examples:

{
  "duration_seconds": 12.5,
  "records_processed": 150,
  "status": "success"
}

{
  "email_sent": true,
  "recipient": "user@example.com"
}

task_name

string

required

Name of the task that produced this output. Case-sensitive identifier matching flow definition YAML. Used to associate output with specific workflow task.

Required string length: 1 - 200

Examples:

"extract_data"

"send_email"

"validate_document"

created_at

string<date-time> | null

ISO 8601 timestamp when task output was created (UTC). Represents when the output was recorded in the system. NULL for legacy records created before timestamp tracking.

Example:

"2025-01-24T10:30:00Z"

flow_version

integer | null

Version number of the flow definition used for execution. Matches flow_version from parent flow execution. NULL for outputs created before version tracking. Useful for tracking output changes across flow versions.

Required range: x >= 1

Example:

1

modified_by

string

default:system

Identifier of the actor who last modified this task output. Tracks who made the last change for auditing purposes. Defaults to 'system' for worker-initiated changes.

Values:

'system': System-automated changes (workers, background jobs)
User ID: UUID string of the user who made the change (e.g., '123e4567-e89b-12d3-a456-426614174000')
Integration type: For service accounts/integrations (e.g., 'integration', 'service-account')

Examples:

"system"

"123e4567-e89b-12d3-a456-426614174000"

"integration"

output

any | null

Full output data produced by the task. May be large or complex; use summary field for UI display. Can be dict, list, or primitive types. NULL if task produces no output data. Available for downstream task consumption in workflows.

Example:

{
  "extracted_text": "Long document content...",
  "metadata": { "author": "John" }
}