Delete Comments in ClickUp

/ ClickUp / By

How to Delete Task Comments in ClickUp via API

Deleting comments through the ClickUp API is essential when you need to clean up task discussions, remove outdated information, or automate moderation across your workspace. This step-by-step guide explains how to use the official REST endpoint to safely remove a comment from a task.

Understanding the ClickUp comment delete endpoint

The ClickUp developer platform exposes a dedicated endpoint to delete a comment from a task. This endpoint accepts a DELETE request and requires the comment ID you want to remove.

The operation is permanent, so you should confirm that your automation or integration targets the correct comment before sending the request.

When you call the delete endpoint successfully, the API responds with a JSON object indicating that the comment has been deleted.

Prerequisites for using the ClickUp API

Before you can delete comments through the ClickUp REST API, make sure you have the following in place:

  • A ClickUp account with access to the relevant Workspace.
  • A valid personal token or OAuth token.
  • The ID of the comment you plan to delete.
  • A tool to send HTTP requests, such as cURL, Postman, or an application using your preferred programming language.

If you are planning a broader automation or integration project around ClickUp and other platforms, consider working with a specialist consultancy like Consultevo to help design and optimize your workflows.

ClickUp delete comment endpoint details

The clickup comment deletion endpoint uses the DELETE HTTP method and targets a specific comment by ID. According to the official documentation, the structure looks like this:

  • Method: DELETE
  • Base URL: https://api.clickup.com/api/v2/
  • Path: comment/{comment_id}

Replace {comment_id} with the actual ID of the comment that you want to remove from a task.

You can review the full API reference and any recent updates directly on the official documentation page: ClickUp Delete Comment reference.

Required headers for ClickUp delete requests

To authenticate and format your request properly, you must add specific headers when calling the delete endpoint for comments in ClickUp.

  • Authorization: Your API token in the form Authorization: <your-token>.
  • Content-Type: application/json, even though the DELETE operation does not require a request body for this endpoint.

Make sure that your token has access to the Workspace where the comment exists. If the token does not have sufficient permissions, the request will fail with an error status.

Step-by-step: Delete a comment in ClickUp via API

Follow these steps to remove a task comment from ClickUp using the official REST endpoint.

Step 1: Locate the ClickUp comment ID

The delete endpoint works with a comment ID, not a task ID. You will need to fetch or otherwise store this ID before deleting the comment. Typical ways to obtain the ID include:

  • Calling the endpoint that lists comments on a task and reading the returned IDs.
  • Storing comment IDs in your own database at the time they are created.
  • Retrieving IDs from a previous response when integrating ClickUp into your application.

Once you have the correct ID, you are ready to construct your delete request.

Step 2: Build the ClickUp DELETE URL

Construct the full URL by inserting the comment ID into the endpoint path. For example:

https://api.clickup.com/api/v2/comment/<comment_id>

Replace <comment_id> with the exact identifier value that you obtained in the previous step.

Step 3: Send the DELETE request to ClickUp

Use your preferred HTTP client to send the delete request. A basic cURL example looks similar to this pattern:

curl -X DELETE 
  -H "Authorization: <your-token>" 
  -H "Content-Type: application/json" 
  "https://api.clickup.com/api/v2/comment/<comment_id>"

Update the token and comment ID with your own values. The same structure applies in Postman, JavaScript, Python, or any other HTTP client when removing a comment from ClickUp.

Step 4: Interpret the ClickUp API response

On success, the API responds with JSON data that confirms the deletion. The response structure is designed to clearly indicate that the target comment is no longer present.

If the comment does not exist, is already deleted, or your token lacks permission, the response will contain an error status code and a corresponding message. You should inspect both the status code and the error field to understand what went wrong.

Handling errors when deleting ClickUp comments

When working with the delete comment endpoint in ClickUp, you might encounter several common error scenarios. Handling them programmatically will make your integration more reliable.

  • 401 Unauthorized: The token is missing, invalid, or expired. Confirm that the Authorization header is present and the token is correct.
  • 403 Forbidden: The token does not have permission to delete comments in the relevant Workspace, Space, or task.
  • 404 Not Found: The comment ID is incorrect, or the comment has already been removed.
  • 429 Too Many Requests: You have exceeded the ClickUp rate limit. In this case, implement retry logic with exponential backoff.

Your application should log the status code, message, and any additional details returned by the ClickUp API. This will help you diagnose failures and improve your automation over time.

Best practices for managing ClickUp comments via API

Use the following recommendations when you build workflows around deleting comments in ClickUp:

  • Confirm ownership: Ensure that your automation only deletes comments that your team is authorized to manage.
  • Log deletions: Store the comment ID, task ID, timestamp, and user who initiated the removal so that you can audit actions later.
  • Implement safeguards: Add confirmation steps or business rules so that critical comments are not removed unintentionally.
  • Respect rate limits: Batch operations and add delays when deleting large numbers of comments from ClickUp to avoid throttling.

These practices will help you maintain clean task threads in ClickUp while preserving traceability and stability in your integrations.

Integrating ClickUp comment deletion into workflows

Once you understand the delete endpoint, you can embed it into larger automation flows around ClickUp. Typical use cases include:

  • Automatically removing bot or system messages after they are no longer useful.
  • Cleaning up test data comments after QA cycles.
  • Implementing moderation rules where certain phrases trigger automatic deletion and replacement with a standardized note.
  • Synchronizing ClickUp task discussions with external systems while pruning duplicates or outdated information.

Combining the delete comment endpoint with other APIs, such as task or list operations, allows you to build richer solutions that keep your ClickUp workspace organized and aligned with your business logic.

Next steps with the ClickUp API

Now that you can delete comments using the ClickUp REST endpoint, explore related endpoints for creating and listing comments, managing tasks, and orchestrating entire workflows across your Workspace. Always keep the official documentation bookmarked, as it is the authoritative source for any changes to the API specification, permissions, or rate limits.

By following the steps and best practices outlined here, you will be able to manage comment lifecycles in ClickUp programmatically, maintain cleaner task histories, and build more robust integrations across your project management stack.

Need Help With ClickUp?

If you want expert help building, automating, or scaling your ClickUp workspace, work with ConsultEvo — trusted ClickUp Solution Partners.

Get Help

“`

Verified by MonsterInsights