Skip to main content
GET
/
r
/
tasks
List tasks
curl --request GET \
  --url https://core.cyberun.cloud/api/v1/r/tasks \
  --header 'Authorization: Bearer <token>'
{
  "task_list": [
    {
      "id": "019abc12-9012-7890-abcd-ef1234567896",
      "workflow_id": "019abc12-8901-7890-abcd-ef1234567895",
      "created_at": "2025-02-10T14:00:00Z",
      "retry_count": 0,
      "started_at": "2025-02-10T14:00:05Z",
      "completed_at": "2025-02-10T14:01:30Z",
      "agent_id": "agent-gpu-01",
      "agent_labels": [
        "gpu",
        "a100"
      ],
      "gateway_id": "gw-a1b2c3d4",
      "gpu_type": "<string>",
      "dispatch_target": "agent",
      "target_pool": "team",
      "tool_type": "comfyui"
    }
  ],
  "page_meta": {
    "current_page": 1,
    "per_page": 20,
    "total_count": 42
  }
}

Documentation Index

Fetch the complete documentation index at: https://docs.cyberun.cloud/llms.txt

Use this file to discover all available pages before exploring further.

Authorizations

​
Authorization
string
header
required

User session JWT (Bearer ). Must be paired with the X-Team-ID request header on team-scoped endpoints so the server knows which team's resources to operate on.

Headers

​
X-Team-ID
string<uuid>

UUID of the team to scope the request to. Used by dual-auth endpoints (runtime + scoped management):

  • JWT callers MUST send it — a user may belong to multiple teams and the runtime cannot otherwise know which one to operate on. Missing header → 400.
  • Credential callers (sk-, dk-) can omit it because the team is derived from the credential row itself. Any value sent is ignored.
Example:

"019abc12-4567-7890-abcd-ef1234567891"

Query Parameters

​
current_page
integer
default:1

Page number to retrieve (1-based). Default: 1.

Required range: x >= 1
Example:

1

​
per_page
integer
default:20

Number of items per page (1–100). Default: 20.

Required range: 1 <= x <= 100
Example:

20

​
status
enum<string>

Filter tasks by status. Current state of the task:

  • pending: Task created, waiting to be picked up by the scheduler.
  • waiting: The scheduler received the task, waiting for an available agent with matching labels.
  • queued: Task assigned to an agent, waiting for ACK.
  • running: Agent is executing the ComfyUI workflow.
  • completed: Execution finished successfully, output is available.
  • failed: Execution failed, check the error field for details.
  • cancelled: Task was cancelled before completion.
Available options:
pending,
waiting,
queued,
running,
completed,
failed,
cancelled

Response

Task list

​
task_list
object[]
required

List of tasks for the current page.

​
page_meta
object
required

Pagination metadata included in all list responses.