AI Inbox

Update Meeting Task

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.

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

Path parameters

task_idstring required

Meeting task id.

Headers

Authorizationstring nullable
X-Target-Org-Idstring nullable

Request body

titlestring nullable
descriptionstring nullable
status'open' | 'in_progress' | 'completed' | 'done' | 'cancelled' nullable
priorityinteger nullable
due_datestring date-time nullable
assignee_user_idstring nullable
expected_updated_atstring 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

Successful Response

dataInboxPayload 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.

Changes

No recorded changes to this operation across all 2 revisions of this API.