/operations/operations_tasks

Retrieves a single OperationsTask by id. | authz: min_org_role=operator | () -> (OperationsTask1)

get/operations/operations_tasks/v1/{task_id}

Request

  • Base URL
    http://localhost:8000
  • URL
    http://localhost:8000/operations/operations_tasks/v1/{task_id}
  • Auth
    HTTP bearer

Path parameters

task_idstring required

Response

Successful Response

schema_version1 required
order_idstring required
task_type'review_order_details' | 'flight_check' | 'facility_check' | 'weather_check' | 'book_cargo' | 'customs' | '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.

titlestring required
descriptionstring required
deadline_timestampstring date-time
assigned_user_idsstring[]
department_idstring nullable
_idstring required
order_short_idstring required
order_off_chrt_reference_idstring nullable

Must be a URL-safe string of 1-64 characters. Allowed characters: A-Z, a-z, 0-9, '.', '_', '~', '-' (RFC 3986 unreserved).

org_idstring required

Must be a string starting with org_

source_task_list_idstring nullable
entry_tagstring nullable
status'not_started' | 'in_progress' | 'blocked' | 'completed' | 'skipped' | 'cancelled'

Operator-driven lifecycle of an operations task.

Manually driven by operators for now (no automatic transitions). Kept structurally parallel to the Check status model in anticipation of the eventual Task <-> Check merge.

completed_at_timestampstring date-time nullable
completed_by_user_idstring nullable

Must be a string starting with user_

Changes

    • warning

      added the new blocked enum value to the response property for the response status

    • warning

      added the new customs enum value to the response property for the response status

    • info

      added the optional property to the response with the status