---
title: "Update Meeting Task"
method: PATCH
path: "/inbox/meetings/tasks/{task_id}"
tags: ["AI Inbox"]
---

# Update Meeting Task

`PATCH /inbox/meetings/tasks/{task_id}`

## Request

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

Patch a meeting task. Reassignment re-checks participant scope.

THREE-STATE nullable fields: omit `assignee_user_id` or
`due_date` to leave it alone, send it as `null` to CLEAR it. The proxy
forwards with `exclude_unset=True` precisely so the app can still tell
those apart - dumping every field would turn each PATCH into a full
overwrite that cleared whatever the caller did not mention.

Pass `expected_updated_at` to refuse the write if someone else moved the
task since you read it.

## Path parameters

- `task_id` string, required: Meeting task id.

## Headers

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

## Request body

- MeetingTaskUpdateRequest: Patch a meeting task. NULLABLE FIELDS ARE THREE-STATE, and that is the whole point of PATCH here: * field absent from the body -> leave unchanged * field present and `null` -> clear it (unassign / drop due date) * field present with a value -> set it (reassignment is re-validated) The proxy forwards with `exclude_unset=True` so the app's own `model_fields_set` check still distinguishes "sent null" from "not sent". Dumping every field would turn every PATCH into a full overwrite that cleared whatever the caller did not mention.
  - `title` string, nullable
  - `description` string, nullable
  - `status` 'open' | 'in_progress' | 'completed' | 'done' | 'cancelled', nullable
  - `priority` integer, nullable
  - `due_date` string, date-time, nullable
  - `assignee_user_id` string, nullable
  - `expected_updated_at` string, date-time, nullable: Optimistic concurrency: the `updated_at` you read. If the task moved since, the update is refused instead of silently overwriting someone else's edit.

## Response `200`

Successful Response

- ApiResponseInboxPayload
  - `data` InboxPayload, required: An open envelope for a comment, an assignment or a workspace. Open because a comment carries attachment refs and mention metadata that grow, and because an assignment result reports per-assignee outcomes.
  - `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)