How to retrieve a contact comment in Zoho Desk

Retrieving a specific comment on a Zoho Desk contact is straightforward once you have both the contact ID and the comment ID — a single GET request returns the full comment record.

Why this matters

When building integrations, automations, or audit workflows, you may need to fetch a particular comment left on a contact record rather than pulling all comments at once. This targeted retrieval keeps API calls efficient and reduces unnecessary data transfer. Support operations teams at Beam Help — independent expert support for Zoho, not official Zoho support — frequently use this endpoint when syncing contact notes into external systems.

Step-by-step

Step 1. Identify the two required path parameters before making any request: the contactId of the contact record and the commentId of the specific comment you want to retrieve. Both values are strings and must be present — the endpoint will not resolve without them. ^[8]

Step 2. Construct your request URL using the following pattern:

GET /api/v1/contacts/{contactId}/comments/{commentId}

Replace {contactId} with the actual contact's ID and {commentId} with the target comment's ID. ^[8]

Step 3. Send the request using your preferred HTTP client. The operation name in Zoho Desk's API layer is getcontactcomment, and it maps to a standard GET call. In Python, the call looks like this: ^[8]

def get_contact_comment(self, contactId: str, commentId: str, p: dict = None):
    return self.c.request("GET", f"/api/v1/contacts/{contactId}/comments/{commentId}", p, None)

The optional p parameter can carry any additional query parameters your implementation requires. ^[8]

Step 4. Parse the response payload. A successful call returns the comment data associated with that specific contact and comment ID combination. Store or process the result according to your integration's needs. ^[8]

Common pitfalls

• Wrong or swapped IDs — Passing a commentId in the contactId position (or vice versa) will result in a failed lookup. Double-check that each ID maps to the correct path segment before sending the request. ^[8]
• Missing parameters — Both contactId and commentId are required path parameters. Omitting either one means the endpoint cannot be resolved and the request will fail. ^[8]
• Incorrect contact–comment association — If the commentId does not belong to the specified contactId, the API will not return the expected record. Verify the relationship between the two IDs in your data source first. ^[8]

What to check

• Confirm that both contactId and commentId are valid, non-null strings pulled from your Zoho Desk data before firing the request. ^[8]
• Verify that your API credentials have the necessary read permissions on the Contacts module in Zoho Desk. ^[8]
• After receiving the response, validate that the returned comment ID in the payload matches the commentId you requested, confirming you retrieved the correct record. ^[8]