Resolve or reopen a comment

PATCH

/v1/data/{artifactId}/comments/{commentId}/resolve

curl --request PATCH \
  --url https://shareout.site/v1/data/example/comments/example/resolve \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{ "resolved": true }'

• Production

Signed-in caller: the comment’s author, the artifact owner, the assignee, or anyone with comment access — owner or collaborator (across linked accounts), an internal member of the artifact’s workspace when it is workspace- or public-visible, or a comment grant. A view-only grant does not qualify.

Authorizations

• bearerAuth

Parameters

Path Parameters

artifactId

required

string

Artifact ID (e.g. art_abc123).

commentId

required

string

Request Body^required

Media typeapplication/json

object

resolved

false reopens the thread.

boolean

default: true

Responses

200

The updated comment

Media typeapplication/json

object

success

boolean

data

object

id

cmt_ + 24 hex characters.

string

contextId

string | null

parentId

string | null

authorId

string | null

authorName

string

content

string

createdAt

string format: date-time

updatedAt

string format: date-time

resolved

boolean

resolvedBy

string | null

resolvedAt

string | null format: date-time

position

Pin position on the page, when the comment was placed as a pin.

mentions

Array<string>

authorType

guest = a verified guest with no account (their email is never returned).

string

Allowed values: human agent guest

assigneeUserId

string | null

assigneeEmail

string | null

dueAt

string | null format: date-time

versionId

Id of the version that was live when the comment was written; null on older comments.

string | null

reactions

object

key

additional properties

object

count

integer

mine

boolean

Example

{
  "data": {
    "authorType": "human"
  }
}

403

FORBIDDEN (no comment access) or COMMENTS_DISABLED

404

COMMENT_NOT_FOUND