---
title: "List"
method: GET
path: "/operations/operations_task_lists/list/v1"
tags: ["/operations/operations_task_lists"]
---

# List

`GET /operations/operations_task_lists/list/v1`

Lists OperationsTaskLists for the caller's organization with filtering, sorting, and pagination. | authz: min_org_role=operator | () -> (OperationsTaskListListRes)

## Query parameters

- `sort_by` 'created_at_timestamp' | 'updated_at_timestamp' | 'name'
- `sort_order` 'asc' | 'desc' — Sort order for query results
- `page` integer
- `page_size` integer
- `filter_archived` boolean, nullable — Filter by archived flag. None=all, True=archived only, False=unarchived only.

## Response `200`

Successful Response

- OperationsTaskListListRes
  - `items` OperationsTaskList1[], required
    - `schema_version` 1, required
    - `name` string, required
    - `description` string, nullable
    - `entries` OperationsTaskListEntry1[]
      - `task_type` 'review_order_details' | 'flight_check' | 'facility_check' | 'weather_check' | 'book_cargo' | 'track_and_verify' | 'contact_customer' | 'contact_agent' | 'contact_airline' | 'contact_other' | 'finalize_billing' | 'custom' | 'other', required — Coarse functional buckets a dispatcher batch-processes (powers the per-type functional-queue index). Granular SOP specifics live in the Task's `title`/`description`, not here. Ordered roughly along the shipment lifecycle (review -> research -> book -> track/verify -> contact -> billing). The buckets are the distinct *modes of work* an operator sits down and batches; the exact SOP step (e.g. "Send Shipping Label", "CBC Call", "Get Pack Time") is captured in the title. Contact is split by *who* (customer, agent, airline, other), not by *channel* (call vs. email) — the recipient is what a dispatcher batches around, and the channel is captured in title/description detail.
      - `title` string, required
      - `description` string, required
      - `deadline_anchor` 'from_first_task' | 'from_previous_task' — What an entry's `deadline_offset_seconds` is measured from. Resolved in a single forward pass at apply time (see module docstring).
      - `deadline_offset_seconds` integer
      - `uuid` string
    - `_id` string, required
    - `org_id` string, required — Must be a string starting with `org_`
    - `archived` boolean
    - `created_by_user_id` string, required — Must be a string starting with `user_`
    - `created_at_timestamp` string, date-time, required
    - `updated_at_timestamp` string, date-time, required
  - `total_count` integer, required

## Other responses

- `422` — Validation Error

---

[API](https://skmtc.dev/chrt/apis/chrt-fastapi.md) · [All operations](https://skmtc.dev/chrt/apis/chrt-fastapi/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/chrt/chrt-fastapi/revisions/ea04e157edb3/schema)