---
title: REST API - Update Comment Request
slug: rm/rest-api-update-comment-request
docTags: 
createdAt: 2026-06-09T13:38:46.906Z
---

```bash
/api/v1/projects/{projectId}/artifacts/{artifactId}/comments/{commentId}
```

# Description

Updates the specified comment.

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

# URL Structure

```bash
[Blueprint_URI]/api/v1/projects/{projectId}/artifacts/{artifactId}/comments/{commentId}
```

- `ProjectId`: The ID of the project containing the comment you want to update.
- `ArtifactId`: The ID of the artifact containing the comment you want to update.
- `CommentId`: The ID of the comment you want to update.

# Supported Methods

- [PATCH](docId\:RcjvHRLbY6de-zGKeHxuI) 

:::hint{type="info"}
You can [override the PATCH](docId\:RcjvHRLbY6de-zGKeHxuI) method and use the [POST](docId\:Hsi_LzXS8g_RX_ydUdZKg) method instead.
:::

# Request Body

You must specify the new comment information in the body of the request. Read more about how to [update the comment in the request body](docId:-imE-8RgZNC7Zy7-vf9of).

# 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](docId\:Sv9GjVErxCZcgqdn28J7U), Traces, Offset or Limit parameters.
  - A required value has not been provided.
  - If you are submitting a [POST](docId\:Hsi_LzXS8g_RX_ydUdZKg) or [PATCH](docId\:RcjvHRLbY6de-zGKeHxuI) 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**

```bash
https://production.blueprintcloud.com/api/v1/projects/220870/artifacts/220914/comments/583921
```

**Request Body**

```xml
<?xml version="1.0" ?><Comment xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.blueprintsys.com/blueprint/api/v1">  <Description>Comment created by API</Description>  <Status>Open</Status></Comment>
```

**Response Body**

```xml
<?xml version="1.0" ?><string xmlns="http://schemas.microsoft.com/2003/10/Serialization/">Comment Updated Successfully.</string>
```

## JSON Example

**Request URI**

```bash
https://production.blueprintcloud.com/api/v1/projects/220870/artifacts/220914/comments/58392-1
```

**Request Body**

```json
{  "Status": "Open",  "Description": "Comment created by API"}
```

**Response Body**

```bash
"Comment Updated Successfully."
```