Skip to main content
PATCH
/
comments
/
:id
/
unresolve
Unresolve Comment
curl --request PATCH \
  --url https://api.example.com/comments/:id/unresolve
{
  "id": "<string>",
  "body": "<string>",
  "filePath": "<string>",
  "lineNumber": 123,
  "pullRequestId": "<string>",
  "userId": 123,
  "parentCommentId": "<string>",
  "resolved": true,
  "createdAt": "<string>",
  "updatedAt": "<string>"
}
Mark a previously resolved comment thread as unresolved. This is useful when a discussion needs to be reopened or when new issues are discovered related to a previously resolved comment.

Authentication

This endpoint requires JWT authentication. Include the JWT token in the Authorization header:
Authorization: Bearer <token>

Path Parameters

id
string
required
The ID of the comment to mark as unresolved

Response

id
string
The unique identifier for the comment
body
string
The content of the comment
filePath
string
The file path where the comment was made
lineNumber
number
The line number in the file
pullRequestId
string
The ID of the pull request
userId
number
The ID of the user who created the comment
parentCommentId
string
The ID of the parent comment if this is a reply
resolved
boolean
Set to false indicating the comment is now unresolved
createdAt
string
ISO 8601 timestamp of when the comment was created
updatedAt
string
ISO 8601 timestamp of when the comment was last updated

Example

curl -X PATCH https://api.diffy.com/comments/1/unresolve \
  -H "Authorization: Bearer <token>"

Response

{
  "id": "1",
  "body": "This function could be optimized by caching the result",
  "filePath": "src/utils/processor.ts",
  "lineNumber": 42,
  "pullRequestId": "123456789",
  "userId": 5,
  "parentCommentId": null,
  "resolved": false,
  "createdAt": "2026-03-01T10:30:00Z",
  "updatedAt": "2026-03-01T16:20:00Z"
}

Build docs developers (and LLMs) love