---
title: "Create"
method: POST
path: "/operations/operations_tasks/v1"
tags: ["/operations/operations_tasks"]
---

# Create

`POST /operations/operations_tasks/v1`

Creates a new OperationsTask on an Order where the caller is coordinator or executor. Seeds department_id from the caller's Order department fields. | authz: min_org_role=operator | (OperationsTaskClientCreate1) -> (PydanticObjectId)

## Request body

- OperationsTaskClientCreate1
  - `schema_version` 1, required
  - `order_id` string, required
  - `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_timestamp` string, date-time
  - `assigned_user_ids` string[]

## Response `200`

Successful Response

- string

## 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)