REST API - Update Reply Request

/api/v1/projects/{projectId}/artifacts/{artifactId}/comments/{commentId}/replies/{replyId}

Description

Updates the specified reply.

You can only update a reply if Blueprint is configured to allow the updating of published comments and replies.

URL Structure

[Blueprint_URI]/api/v1/projects/{projectId}/artifacts/{artifactId}/comments/{commentId}/replies/{replyId}
  • ProjectId: The ID of the project containing the reply you want to update.
  • ArtifactId: The ID of the artifact containing the reply you want to update.
  • CommentId: The ID of the comment associated with the reply you want to update.
  • ReplyId: The ID of the reply you want to update.

Supported Methods

Request Body

You must specify the new reply information in the body of the request. Read more about how to update the reply in the request body.

HTTP Status Codes

  • 200: OK
  • 201: Successfully Created
  • 206: Partial Content
  • 400: Bad Request
    This error can occur for a variety of reasons:
    • At least one URI or request body parameter is invalid, such as one of the Filter, Traces, Offset or Limit parameters.
    • A required value has not been provided.
    • If you are submitting a POST or PATCH request and have not added the X-HTTP-Method-Override parameter to your request header.
  • 401: Unauthorized
    • The Blueprint token is missing, invalid or expired.
  • 403: Forbidden
    • The applicable permissions are needed. For example, this error can occur when:
      • An Author or Collaborate license is needed for access.
      • Comment permissions are needed on the artifact.
      • Edit permissions are needed on the change summary job.
  • 404: NotFound
    • Item is not found in the project. For example, this error can occur when:
      • Artifact not found.
      • Artifact type not found.
      • Project not found.
      • ALM target not found.
      • Change summary job not found.
      • User does not have edit permissions for this artifact, project or ALM target.
  • 409: Conflict
    • Reason for failure can be found in the response body. Additional information may also be found in the log.
  • 411: Length Required
    • If the Content-Length header is missing in the request.
  • 413: Request Entity Too Large
    • If the provided file size is larger than allowed.
  • 415: Unsupported Media Type
    • If the provided media type is not of MIME Multipart Content "form-data."
  • 416: Request Range Not Satisfiable
    • If offset points to a part of a collection that is not available.
  • 500: Internal Server Error
  • 501: Not Implemented

Examples

XML Example

Request URI

https://production.blueprintcloud.com/api/v1/projects/220870/artifacts/220914/comments/583921/replies/233454

Request Body

<?xml version="1.0" ?>
<Reply xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.blueprintsys.com/blueprint/api/v1">
  <Description>&lt;html&gt;&lt;head&gt;&lt;/head&gt;&lt;body&gt;&lt;div&gt;&lt;p&gt;&lt;span&gt;&lt;span&gt;Reply&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;&lt;/div&gt;&lt;/body&gt;&lt;/html&gt;</Description>
</Reply>

Response Body

<?xml version="1.0" ?>
<string xmlns="http://schemas.microsoft.com/2003/10/Serialization/">The reply was successfully updated.</string>
JSON Example

Request URI

https://production.blueprintcloud.com/api/v1/projects/220870/artifacts/220914/comments/583921/replies/233454

Request Body

{
  "Description": "<html><head></head><body><div><p><span><span>Reply</span></span></p></div></body></html>"
}

Response Body

"The reply was successfully updated."