List tasks for a workspace

GET

/workspaces/{id}/tasks

const url = 'https://your-org.evershell.ai/v1/workspaces/example/tasks';
const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};

try {
  const response = await fetch(url, options);
  const data = await response.json();
  console.log(data);
} catch (error) {
  console.error(error);
}

curl --request GET \
  --url https://your-org.evershell.ai/v1/workspaces/example/tasks \
  --header 'Authorization: Bearer <token>'

Permissions: workspace:read or workspace:read:own (creator-match on :own).

Authorizations

bearerAuth

Parameters

Path Parameters

required

string

Responses

200

Bare JSON array of Task objects, ordered newest-first.

application/json

Array<object>

object

required

string

org_id

string

workspace_id

required

string

description

string

status

required

Lifecycle: submitted → delivered (handed to the agent) → running → optional compacting interludes → terminal completed / failed / cancelled. delivery_failed is a separate terminal state when the agent never accepted the task (typically unreachable pod).

string

Allowed values: submitted delivered running compacting completed failed cancelled delivery_failed

created_at

required

string format: date-time

completed_at

string format: date-time

duration_seconds

Wall-clock duration in seconds, populated once the task reaches a terminal status. Server-derived from (completed_at − created_at).

number

reason

string

Example

[
  {
    "id": "task_01HZ",
    "status": "submitted"
  }
]

403

Caller lacks the required scope, or cross-org access attempted

application/json

object

error

required

object

code

required

Closed-enum slug (e.g. permission_denied, validation_error, workspace_not_found)

string

message

required

Human-readable summary

string

request_id

required

Server-generated request id for correlating logs

string

details

Optional structured context. Validation errors land at details.fields as a per-field map.

object

key

additional properties

any

Example

{
  "error": {
    "code": "permission_denied",
    "message": "caller lacks required scope",
    "request_id": "7f3a9c2e"
  }
}

404

Resource not found in the caller’s org

application/json

object

error

required

object

code

required

Closed-enum slug (e.g. permission_denied, validation_error, workspace_not_found)

string

message

required

Human-readable summary

string

request_id

required

Server-generated request id for correlating logs

string

details

Optional structured context. Validation errors land at details.fields as a per-field map.

object

key

additional properties

any

Example

{
  "error": {
    "code": "permission_denied",
    "message": "caller lacks required scope",
    "request_id": "7f3a9c2e"
  }
}