Skip to main content
POST
Update Review Discussion

Authentication and permissions

Token requirements: User-based token (OAuth). Send a bearer access token for one of these identities. The permissions and resource restrictions below also apply.
Permissions joined by + are all required; or separates alternatives. Full-access keys still cannot call endpoints marked unsupported. Workspace keys must allow every workspace checked by the request. OAuth access depends on the user’s roles and resource access. Requires a user token and the same review and item access as comments in the app. Comments stay within the review’s organization. Only the author may edit or delete a comment. Closed or applied reviews are read-only.
  • User: session review: Requires permission to view configuration sessions in the session’s workspace.
  • User: promotion: Requires review or apply permission on the target workspace, or both staging permission on the target workspace and author permission on the source workspace.
  • User: parent-to-branch pull: For a recorded parent-to-branch pull, staging permission on the target branch and branch permission on the source parent also authorize access.

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

review_id
string
required

Body

application/json
operation
enum<string>
required
Available options:
REVIEW_DISCUSSION_OPERATION_UNSPECIFIED,
REVIEW_DISCUSSION_OPERATION_CREATE_THREAD,
REVIEW_DISCUSSION_OPERATION_REPLY,
REVIEW_DISCUSSION_OPERATION_EDIT,
REVIEW_DISCUSSION_OPERATION_DELETE,
REVIEW_DISCUSSION_OPERATION_RESOLVE,
REVIEW_DISCUSSION_OPERATION_REOPEN
threadId
string

Required for reply, resolve and reopen.

commentId
string

Required for edit and delete.

originalItemId
string | null

Set only when creating a thread on an item.

body
string

Required for create_thread, reply and edit.

Response

200 - application/json

Success

data
data · object