Sign in
/operations/operations_tasks

Create

Creates a new OperationsTask on an Order where the caller is coordinator or executor. Uses the explicit department_id or leaves the task unassigned. | authz_personas=[coordinator_org_operators, order_executor_org_operators] | (OperationsTaskClientCreate1) -> (PydanticObjectId)

post/operations/operations_tasks/v1

Request body

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

Response

Successful Response

string required

Changes