# Update a task

```http
PUT https://secure.yoprint.com/v2/api/store/{team_slug}/v2/work_pipeline/{hash_id}
```

- API version: v2
- Operation ID: `v2_public_job_work_pipeline_update`
- Section: Production › [Tasks](https://developer.yoprint.com/reference/tasks.md)
- Web page: https://developer.yoprint.com/reference/tasks/v2-job-work-pipeline-update/
- Authentication: `Authorization: Bearer YOUR_API_KEY`

Changes a task's name, note, preset, status, position, dates or assignees, and returns it. Send only what you change.

Send `start_date` and `due_date` together (both may be null). A start after the due date is a 422 ("Invalid date range. Due Date should be greater than Start Date."). Changing a task's dates resets the job's dates to span its dated tasks: the earliest task start and the latest task due date (none when no task has dates).

Assignees: `unassign_all` runs first, then `assigned_users` are added, then `unassigned_users` are removed. To change only the status, Change a task's status does the same and also returns the previous status.

## Permission

Any member of the team. No sales order permission is checked.

## Business rules

- A task's status must be a status of its task preset. An unknown preset is a 422 "Pipeline not found!"; a status from another preset a 422 "Pipeline Status not found!".
- `assigned_users` must be members of your team (404 otherwise). `unassigned_users` isn't checked: ids that aren't assigned are ignored.

## Side effects

- Changing the dates may change the job's dates.
- Changing `status_id` sends the `work_pipeline.status_changed` webhook and records the status history.
- Open Admin Portal pages refresh.

## Path parameters

- `team_slug` (string, required): Your team slug, shown as Team ID next to your API key in Profile. Example `your-team`.
- `hash_id` (string, required): The task's hash id. Hash ids only: a unique key or a document number gives 404. Example `hpioY1gDBQZdbI`.

## Request body

Content type `application/json`, required.

Fields:

- `assigned_users` (array of strings, optional): User hash ids to add.
- `color` (string, optional): A hex color. Validated but not saved.
- `due_date` (string (date-time) | null, optional): ISO 8601, or null to clear. Send with `start_date`.
- `name` (string, optional)
- `note` (string, optional)
- `pipeline_id` (string, optional): Move the task to another task preset. Send a `status_id` of that preset with it.
- `position` (integer, optional): Minimum -2147483648. Maximum 2147483647.
- `start_date` (string (date-time) | null, optional): ISO 8601, or null to clear. Send with `due_date`; dates change only when both are sent.
- `status_id` (string, optional): A status of the task's preset.
- `unassign_all` (boolean | null, optional): Remove every assignee first.
- `unassigned_users` (array of strings, optional): User hash ids to remove.

### Example request

```bash
curl -X PUT 'https://secure.yoprint.com/v2/api/store/your-team/v2/work_pipeline/hpioY1gDBQZdbI' \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -H 'Accept: application/json' \
  -H 'X-Yoprint-Decimal-Format: exact-v1' \
  -H 'Content-Type: application/json' \
  -d '{
    "assigned_users": [
      "4mdDkMg3dgQOa3"
    ],
    "unassign_all": true
  }'
```

Another example: Move a task:

```bash
curl -X PUT 'https://secure.yoprint.com/v2/api/store/your-team/v2/work_pipeline/hpioY1gDBQZdbI' \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -H 'Accept: application/json' \
  -H 'X-Yoprint-Decimal-Format: exact-v1' \
  -H 'Content-Type: application/json' \
  -d '{
    "due_date": "2026-11-06T17:00:00Z",
    "start_date": "2026-11-06T09:00:00Z"
  }'
```

## Response

`200` Successful response.

Fields:

- `data` (object, required): A task.
  - `assigned_users` (array of objects, optional): Who is assigned.
    - Each item:
      - `avatar_url` (string | null, optional)
      - `id` (string, optional): The user.
      - `name` (string, optional)
  - `created_at` (string (date-time), optional)
  - `due_date` (string (date-time) | null, optional): Task due date. ISO 8601 with offset, or null.
  - `id` (string, optional): The task.
  - `job_id` (string, optional): The job.
  - `job_is_rush` (boolean | integer | null, optional)
  - `job_item_count` (number | null, optional)
  - `job_name` (string | null, optional)
  - `job_scoped_id` (string, optional): The job number with its prefix.
  - `job_status_id` (string | null, optional): The job's current status.
  - `name` (string, optional)
  - `note` (string | null, optional)
  - `order_id` (string, optional): The order.
  - `order_name` (string | null, optional)
  - `order_scoped_id` (string | null, optional): The order number.
  - `pipeline_id` (string, optional): The task preset it comes from.
  - `position` (integer, optional): Order among tasks; lower comes first. 0 when unset.
  - `sales_order` (object, optional): A summary of the job's order.
    - `created_by` (string | null, optional): Who created the order.
    - `cust_due_date` (string (date-time) | null, optional): Order customer due (in-hand) date. ISO 8601 with offset, or null.
    - `customer_id` (string | null, optional): The customer.
    - `customer_name` (string | null, optional)
    - `due_date` (string (date-time) | null, optional): Order production due date. ISO 8601 with offset, or null.
    - `external_type` (string | null, optional): `shopify` when the order came from Shopify, else null.
    - `is_quote` (boolean, optional)
    - `issue_date` (string (date-time) | null, optional): Order issue date. ISO 8601 with offset, or null.
    - `object_type` (string | null, optional): `sales_order` or `quote`.
    - `ship_due_date` (string (date-time) | null, optional): Order ship-by date. ISO 8601 with offset, or null.
    - `shopify_deleted_externally` (boolean, optional)
    - `shopify_deleted_externally_at` (string (date-time) | null, optional): When it was deleted in Shopify. ISO 8601 with offset, or null.
    - `start_date` (string (date-time) | null, optional): Order production start. ISO 8601 with offset, or null.
    - `status_id` (string | null, optional): The order status.
  - `start_date` (string (date-time) | null, optional): Task start. ISO 8601 with offset, or null.
  - `status` (object, optional): A status: label, kind and place in the list.
    - `color` (string | null, optional): Hex color.
    - `customer_label` (string, optional)
    - `id` (string, optional): The status.
    - `label` (string, optional)
    - `pipeline_id` (string, optional): Only on the statuses of a task preset (`role` `pipeline`): the task preset. Absent on other statuses.
    - `position` (integer, optional): Its place in the team's list: sort by it to find the next status.
    - `role` (string, optional): Which list it belongs to: `job` for job statuses, `pipeline` for the statuses of a task preset. One of: `"order"`, `"quote"`, `"job"`, `"purchase_order"`, `"shipment"`, `"customer_message"`, `"pipeline"`.
    - `trashed` (boolean, optional): The status was deleted.
    - `type` (string, optional): The kind of status: `start` (Pending), `pre_production` and `in_progress` (In Progress), `end` (Completed). One of: `"start"`, `"pre_production"`, `"in_progress"`, `"end"`.
  - `status_completion_date` (string (date-time) | null, optional): When it reached a Completed status. ISO 8601 with offset, or null.
  - `status_id` (string, optional): The task's status (a status of its task preset).
  - `status_last_change_date` (string (date-time) | null, optional): When the status last changed. ISO 8601 with offset, or null.
  - `updated_at` (string (date-time), optional)
- `status` (integer, required)
- `success` (boolean, required)

Example response:

```json
{
  "data": {
    "assigned_users": [
      {
        "avatar_url": null,
        "id": "4mdDkMg3dgQOa3",
        "name": "Alex Rivera"
      }
    ],
    "created_at": "2026-11-03T15:00:00+00:00",
    "due_date": "2026-11-06T17:00:00+00:00",
    "id": "hpioY1gDBQZdbI",
    "job_id": "WaGvtaWsx7Kcn4",
    "job_is_rush": 1,
    "job_item_count": 48,
    "job_name": "Front print",
    "job_scoped_id": "JOB-2419",
    "job_status_id": "scaWHQnPLtqMPT",
    "name": "Burn screens",
    "note": null,
    "order_id": "sFbALVSYD55eXe",
    "order_name": "Team shirts",
    "order_scoped_id": "SO1001",
    "pipeline_id": "SE3SfXjt6dPfnH",
    "position": 1,
    "sales_order": {
      "customer_id": "ifAHmADekGZ6id",
      "customer_name": "Northwind Apparel",
      "is_quote": false,
      "object_type": "sales_order",
      "status_id": "wgbOT87gGZvhgy"
    },
    "start_date": "2026-11-06T09:00:00+00:00",
    "status": {
      "color": "#2196f3",
      "customer_label": "In Progress",
      "id": "hTFITko5Q0R83y",
      "label": "Burning",
      "pipeline_id": "SE3SfXjt6dPfnH",
      "position": 2,
      "role": "pipeline",
      "trashed": false,
      "type": "in_progress"
    },
    "status_completion_date": null,
    "status_id": "hTFITko5Q0R83y",
    "status_last_change_date": "2026-11-03T15:05:00+00:00",
    "updated_at": "2026-11-03T16:00:00+00:00"
  },
  "status": 200,
  "success": true
}
```

## Errors

- `401` The API key is missing or wrong (`unauthenticated`).
- `403` You are not allowed to do this. `api_access_not_in_plan`: your team's plan doesn't include API access (Pro and above, with an active subscription or trial), so every request answers this until the team upgrades. When your role lacks the permission the operation needs, the body is only `{"message": "Insufficient Permission"}`. Other refusals use the error envelope, with `unauthorized` or `user_is_not_authorized`.
- `404` Not found. `page_not_found`: the team slug is unknown, you are not a member of the team, or an id in the path is not one of this team's. `code: null`, with a message that starts "No query results for": there is no record with that id.
  - When: The task or a user isn't your team's. Fix: Check the ids.
- `422` The request was refused and changed nothing. `validation_failed` lists what to fix in `error.fields`; other codes name a business rule, explained in `error.message`. A few checks answer with only `{"message": "..."}`. An operation that calls another service (a payment provider, a carrier, an accounting app) can answer `connect_timeout` ("Please retry again") when that service does not answer in time: the change may or may not have happened there, so read the record back before you retry.
  - When: Dates out of order or sent alone, an unknown preset, or a status from another preset. Fix: Send both dates in order and a status of the task's preset.

## Related

- [Get a task](https://developer.yoprint.com/reference/tasks/v2-job-work-pipeline-show.md): `GET /v2/api/store/{team_slug}/v2/work_pipeline/{hash_id}`
- [Change a task's status](https://developer.yoprint.com/reference/tasks/v2-job-work-pipeline-change-status.md): `PUT /v2/api/store/{team_slug}/v2/work_pipeline/{hash_id}/status`
- [Assign or unassign a person on a task](https://developer.yoprint.com/reference/tasks/v2-job-work-pipeline-assign.md): `PUT /v2/api/store/{team_slug}/v2/work_pipeline/{hash_id}/assign`