How to get call comment details in Zoho Desk

Retrieving the details of a specific comment on a Zoho Desk call record is straightforward using the Zoho Desk REST API — you simply issue a GET request with both the call ID and the comment ID as path parameters.

Why this matters

When building integrations, automations, or audit workflows around Zoho Desk telephony, you may need to programmatically inspect what was noted during or after a call. Fetching a single comment by its ID lets your application display, log, or process that annotation without pulling every comment on the call. This is especially useful for event-driven pipelines that receive a commentId from a webhook and need to enrich it with full details.

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

---

Step-by-step

Step 1. Identify the two required path parameters you will need before making the request: the callId (the unique identifier of the call record in Zoho Desk) and the commentId (the unique identifier of the specific comment you want to retrieve). Both values are strings. ^[1]

Step 2. Construct the API endpoint by substituting your values into the following pattern:

GET /api/v1/calls/{callId}/comments/{commentId}

For example, if your call ID is 123456789 and your comment ID is 987654321, the path becomes /api/v1/calls/123456789/comments/987654321. ^[1]

Step 3. Add your authentication headers (OAuth 2.0 bearer token) and, if needed, pass any optional query parameters using the p parameter dictionary. The operation name for this endpoint is getcallcomment_details. ^[1]

Step 4. Send the request. Using the Python SDK pattern, the call looks like this:

response = client.get_call_comment_details(
    callId="123456789",
    commentId="987654321"
)

Internally, this issues a GET request to the constructed path, forwarding any optional p parameters as query arguments. ^[1]

Step 5. Parse the response body. The API will return the details for that specific comment on the specified call record. Store or process the fields your integration requires (such as comment text, author, or timestamp). ^[1]

---

Common pitfalls

• Wrong ID order: The path requires callId first, then commentId. Swapping them will result in a 404 or an unexpected record being returned. Double-check the order before sending. ^[1]
• Invalid or mismatched IDs: If the commentId does not belong to the call identified by callId, the API will not return a valid result. Always ensure both IDs are sourced from the same call record. ^[1]
• Missing authentication: Like all Zoho Desk API endpoints, this request requires a valid OAuth 2.0 token scoped to Desk. An absent or expired token will result in an authentication error before the endpoint is even reached. ^[1]

---

What to check

• Confirm both IDs are correct — verify that the callId and commentId exist in your Zoho Desk environment and that the comment genuinely belongs to that call before making the request. ^[1]
• Verify the response payload — ensure the returned object contains the comment fields your downstream process expects; if the response is empty or malformed, re-check your authentication scope and parameter formatting. ^[1]
• Check rate limits — if you are fetching comment details in bulk across many calls, confirm you are staying within Zoho Desk API rate limits to avoid throttling errors. ^[1]