How to delete an event comment in Zoho Desk

Deleting an event comment in Zoho Desk is done via a single DELETE API call that targets the specific event and comment by their respective IDs.

Why this matters

When collaborating on events in Zoho Desk, agents may leave comments that become outdated, incorrect, or simply need to be removed for housekeeping. Knowing the correct API endpoint — and how it relates to similar comment-deletion endpoints across other Zoho Desk entities — ensures you can build reliable automation or perform clean-up operations programmatically. This is especially relevant for teams managing integrations or custom Zoho Desk workflows.

> Note: Beam Help is an independent expert support resource, not official Zoho support.

---

Step-by-step

Step 1. Confirm you have the correct OAuth scopes configured for your Zoho Desk integration. To perform any write or delete operation against events, your token must include Desk.events.ALL or at minimum Desk.events.DELETE in its scope list. ^[5]

Step 2. Identify the two required path parameters you will need before making the call:

• eventId — the unique identifier of the event that contains the comment.
• commentId — the unique identifier of the specific comment you want to remove. ^[1]

Both values are strings. If you are unsure how to retrieve them, query the event's comment list first using a GET request against the same event resource, then note the IDs from the response.

Step 3. Issue a DELETE request to the following endpoint, substituting your real IDs into the path: ^[1]

DELETE /api/v1/events/{eventId}/comments/{commentId}

Step 4. In Python, if you are using a wrapper client, the call looks like this: ^[1]

result = desk_client.delete_event_comment(
    eventId="your_event_id_here",
    commentId="your_comment_id_here"
)

The optional p parameter can carry additional query parameters if your integration requires them; otherwise it defaults to None. ^[1]

Step 5. Check the HTTP response status. A successful deletion typically returns a 2xx status code with no body or a minimal confirmation payload. If you receive a 4xx error, revisit Steps 1 and 2 to verify your scopes and IDs.

---

Common pitfalls

• Wrong entity endpoint. Zoho Desk exposes similar DELETE endpoints for comments on tickets (/api/v1/tickets/{ticketid}/comments/{commentid}), tasks (/api/v1/tasks/{taskId}/comments/{commentId}), contracts (/api/v1/contracts/{contractId}/comments/{commentId}), calls (/api/v1/calls/{callId}/comments/{commentId}), accounts (/api/v1/accounts/{accountId}/comments/{commentId}), and articles (/api/v1/articles/{articleId}/comments/{commentId}). [^2,3,4,6,7,8] Using the wrong parent resource path will result in a 404 or an unintended deletion on a different record type.

• Insufficient OAuth scope. If your token was generated without Desk.events.DELETE or Desk.events.ALL, the API will reject the request with an authorisation error. Always review your scope configuration before debugging the request itself. ^[5]

• Swapped IDs. Passing the commentId in the eventId position (or vice versa) is a common mistake when IDs are similarly formatted strings. Double-check the order: event ID comes first in the path, comment ID second. ^[1]

---

What to check

• Scope coverage: Verify that Desk.events.DELETE or Desk.events.ALL is present in your OAuth token's scope list before making the call. ^[5]
• Correct endpoint path: Confirm you are calling /api/v1/events/{eventId}/comments/{commentId} and not one of the similarly structured endpoints for tickets, tasks, or other entities. [^1,2,3]
• Valid IDs: After the deletion, attempt to fetch the comment via a GET request to confirm it no longer exists and that you targeted the intended record. ^[1]