Review API
Update Review Discussion
Create a review thread, reply, edit or delete your own comment, or resolve or reopen a thread. Use body for create, reply and edit; thread_id for reply, resolve and reopen; comment_id for edit and delete; original_item_id only to start an item thread. Requires a user token and the same review and item access as the app. Closed or applied reviews are read-only.
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
Body
application/json
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 
