Sign in
/operations/operations_tasks

Update

Updates editable fields (task_type, title, description, entry_tag, deadline_timestamp, assigned_user_ids, department_id) on an OperationsTask. | authz: min_org_role=operator | (OperationsTaskClientUpdate1) -> (bool)

patch/operations/operations_tasks/v1/{task_id}

Path parameters

task_idstring required

Request body

department_idstring nullable
department_id__set_to_Noneboolean
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'

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 nullable
descriptionstring nullable
entry_tagstring nullable
deadline_timestampstring date-time nullable
assigned_user_idsstring[]
entry_tag__set_to_Noneboolean

Response

Successful Response

boolean required

Changes