Skip to navigation
API ReferenceOperationsOperations 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)

Authentication

AuthorizationBearer

Bearer authentication of the form Bearer <token>, where token is your auth token.

Path parameters

task_idstringRequired

Request

This endpoint expects an object.
assigned_user_idslist of stringsOptional
deadline_timestampdatetimeOptional
department_idstringOptional
department_id__set_to_NonebooleanOptionalDefaults to false
descriptionstringOptional<=8192 characters
entry_tagstringOptional
entry_tag__set_to_NonebooleanOptionalDefaults to false
task_typeenumOptional

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.

titlestringOptional<=512 characters

Response

Successful Response

Errors

422
Operations Tasks Update V1request Unprocessable Entity Error