---
title: "Update Subtask"
method: PUT
path: "/tasks/{task_id}/subtasks/{subtask_id}"
tags: ["Tasks"]
---

# Update Subtask

`PUT /tasks/{task_id}/subtasks/{subtask_id}`

## Request

- Base URL: `https://be.graph8.com/api/v1`
- URL: `https://be.graph8.com/api/v1/tasks/{task_id}/subtasks/{subtask_id}`
- Auth: HTTP bearer

Patch a subtask. Omitted fields are left alone.

Two exceptions worth knowing. An explicit `null` on `due_date`,
`assignee_id` or `task_type` CLEARS that field, which is different from
omitting it. And `records: []` clears every record link, while omitting
`records` leaves them unchanged.

`expected_updated_at` makes the update conditional: if the stored row has
moved on, the write is refused instead of overwriting someone else's edit.

## Path parameters

- `task_id` string, required: Parent task id (UUID).
- `subtask_id` string, required: Subtask id (UUID).

## Headers

- `Authorization` string, nullable
- `X-Target-Org-Id` string, nullable

## Request body

- SubtaskUpdateRequest: Patch a subtask. Omitted fields are left alone. `records` is the exception: an EMPTY list clears every record link, while omitting it leaves the links unchanged.
  - `tags` string[], nullable: Replace the labels.
  - `expected_updated_at` string, nullable: Optimistic-concurrency guard. When set and the stored row is newer, the update is refused instead of overwriting.
  - `title` string, nullable: New title.
  - `description` string, nullable: New body.
  - `due_date` string, nullable: ISO 8601. Send explicit null to clear.
  - `assignee_id` string, nullable: Send explicit null to unassign.
  - `assignee_name` string, nullable: Assignee display name.
  - `status` string, nullable: New status.
  - `priority` integer, nullable: New priority.
  - `task_type` string, nullable: Send explicit null to clear.
  - `reminder_at` string, nullable: ISO 8601 UTC reminder.
  - `clear_reminder` boolean, nullable: Explicitly remove the reminder.
  - `visibility` string, nullable: public | team | private.
  - `records` object[], nullable: Replace record links. Empty list clears them; omit to leave alone.

## Response `200`

Successful Response

- ApiResponseCrmRecordPayload
  - `data` CrmRecordPayload, required: An open envelope for one record, one dashboard or one job receipt. Open because most of these reads are COMPUTED shapes - an engagement summary, a next-best-step, an intelligence status - that grow with the product, and dropping a field from an advisory read makes it say "nothing to report" rather than "we did not tell you".
  - `pagination` PaginationMeta
    - `page` integer, required: Current page number (1-indexed)
    - `limit` integer, required: Items per page
    - `total` integer, required: Total number of items
    - `has_next` boolean, required: Whether there are more pages
    - `next_cursor` string, nullable: Opaque cursor for the next page; null when there are no more items. Pass it back as the `cursor` query param to fetch the following page without computing page numbers.
    - `total_available` integer, nullable: Search endpoints only: how many records really match, when known. Can be larger than `total`, which is capped at the 10,000 results that can be paged. For company search this is a distinct-company estimate. Null when unknown; absent outside search.
    - `total_is_lower_bound` boolean, nullable: Search endpoints only: true when more records match than `total` shows (the result set is larger than the 10,000 results that can be paged). Absent outside search.
    - `notes` string[], nullable: Search endpoints only: plain-language notes about the result, e.g. that more records match than can be paged, or that a reversed `between` range was put in order.

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/graph8/apis/graph8-developer-api.md) · [All operations](https://skmtc.dev/graph8/apis/graph8-developer-api/llms.txt) · [OpenAPI document](https://skmtc.dev/graph8/apis/graph8-developer-api/revisions/89fc11143b70?raw)