Update or complete a task
Update attributes of an existing task, or complete it. Tasks are created automatically by warehouse operations and this endpoint allows modifying task properties such as priority, notes, locations, quantities, and custom fields. To complete a single task, send status: "completed" together with the attributes required by that task’s type. To complete multiple tasks of the same type in one call use POST /api/tasks/complete_collection. Type-specific receive and load actions are documented under the Goods In: Receipts and Loads tags respectively.
Request Structure
Completing a Task
A single task is completed through this endpoint by settingstatus to "completed" together with the attributes required for the task’s type. The table below lists the minimum payload to complete each type; additional fields may be set in the same request when they need updating at the same time.
| Task type | Minimum attributes to complete |
|---|---|
PICK | status, confirmed_quantity, location_to_id (drop location) |
RCV | status, confirmed_quantity, location_to_id, storage_unit_to_id |
PWAY | status, confirmed_quantity, location_to_id, storage_unit_to_id |
TRAN | status, location_to_id, storage_unit_to_id |
CONV | status (optionally confirmed_quantity; defaults to the task’s start_quantity) |
REPLEN | status, confirmed_quantity, location_to_id |
DISP | status for SHIPMENT subtype only. LOAD-subtype DISP tasks must be completed by dispatching the load, not via this endpoint. |
LOAD | Not completable via this endpoint. Use POST /api/load_tasks/{id}/load_storage_unit. |
POST /api/tasks/complete_collection with a task_type_code and a filters block.
Key Fields
| Field | Required | Description |
|---|---|---|
account_id | No | Stock account ID |
warehouse_id | No | Warehouse ID |
priority | No | Task priority (higher = more urgent) |
notes | No | Free-text notes |
status | No | Task status. Set to completed to complete the task (see Completing a Task above). |
location_from_id | No | Source location ID |
location_to_id | No | Destination location ID |
product_id | No | Product ID |
start_quantity | No | Starting quantity (>= 0) |
confirmed_quantity | No | Confirmed/completed quantity (>= 0) |
start_at | No | Planned start datetime |
end_at | No | Planned end datetime |
completed_at | No | Completion datetime |
assigned_at | No | Assignment datetime |
user_id | No | Assigned user ID |
user_created_by_id | No | User who created the task |
user_completed_by_id | No | User who completed the task |
device_type_id | No | Device type ID |
device_id | No | Device ID |
storage_unit_from_id | No | Source storage unit ID |
storage_unit_to_id | No | Destination storage unit ID |
stock_id | No | Associated stock record ID |
load_id | No | Associated load ID |
load_drop_id | No | Associated load drop ID |
dispatch_container_id | No | Associated dispatch container ID |
parent_task_id | No | Parent task ID for subtasks |
transaction_number_id | No | Transaction number ID |
transaction_line_id | No | Transaction line ID |
stock_description | No | Stock description text |
drop_sequence | No | Drop sequence (1-9999999999) |
serial_numbers | No | Array of serial number strings |
string1-string5 | No | Custom string fields |
integer1-integer5 | No | Custom integer fields |
datetime1-datetime5 | No | Custom datetime fields |
boolean1-boolean5 | No | Custom boolean fields |
Authorizations
OAuth 2.0 authentication. Use the client credentials or authorization code flow to obtain an access token.
The subdomain/tenant name identifying which tenant's data to access. Required for all API requests.
Path Parameters
The unique identifier of the task to update
Body
Response
Task updated successfully
Task response in JSON:API format

