Skip to main content
PATCH
Update a conversation review
Requires Editor, Admin, or Owner. Read the current review’s revision, then send it as expected_revision with at least one of status, flagged, or note. A stale revision returns 409. Retrieve the latest review and reconcile changes before retrying; do not blindly overwrite another reviewer’s work. Notes must contain 1–2,000 characters after trimming. Invalid or empty changes return 422; a missing conversation returns 404. The response is the updated review, including its new revision and history.

Authorizations

Authorization
string
header
required

Bandwidth Labs OAuth access token. Uses the user's selected workspace; the workspace header is not required. Do not also send an API key. Bearer-only operations may additionally require the Labs super_user role.

Headers

X-VOAI-ORGANIZATION-ID
string | null

Required with X-BW-LABS-AGENTS-API-KEY: the positive local workspace ID to access. The key owner must be a current member. Missing or invalid IDs return 400; non-member workspaces return 403. Not required for bearer authentication, which uses the user's selected workspace.

Path Parameters

run_id
integer
required

Body

application/json
expected_revision
integer
required
Required range: x >= 0
flagged
boolean | null
note
string | null
Required string length: 1 - 2000
status
enum<string> | null
Available options:
not_reviewed,
in_review,
reviewed

Response

Successful Response

flagged
boolean
default:false
history
History · object[]
notes
Notes · object[]
reviewer
string | null
revision
integer
default:0
status
enum<string>
default:not_reviewed
Available options:
not_reviewed,
in_review,
reviewed
updated_at
string | null