Zoho Desk exposes a dedicated API endpoint that lets you pull feedback statistics for any Help Center article programmatically, giving you a clean, structured way to measure how useful your knowledge base content is.
Why this matters
If you manage a Zoho Desk Help Center, knowing whether readers find articles helpful is critical for content improvement. Rather than manually checking the portal UI, you can automate the collection of feedback data — for example, to feed a dashboard, trigger alerts when an article's rating drops, or schedule regular exports. This is especially valuable for teams maintaining large knowledge bases across multiple Help Centers.
Step-by-step
Step 1. Confirm you have API access to your Zoho Desk organisation. You will need a valid OAuth 2.0 token with the appropriate Desk scopes before making any calls. Ensure your token has read permissions for Help Center resources. [2]
Step 2. Identify the two key identifiers you need before calling the endpoint: the helpcenterid for the Help Center where the article lives, and the articleid for the specific article whose feedback you want to retrieve. Both values can be found via other Zoho Desk API list calls (e.g., listing Help Centers or listing articles within a Help Center). [2]
Step 3. Make a GET request to the following endpoint, substituting your real IDs into the path: [2]
GET /api/v1/helpcenter/{helpcenter_id}/articles/{article_id}/feedback/statisticsFor example, if your Help Center ID is 123456 and your article ID is 789012, the request path becomes:
GET /api/v1/helpcenter/123456/articles/789012/feedback/statisticsStep 4. Optionally, pass the p query parameter to control pagination if the endpoint supports it. This is useful when you are iterating over feedback data across multiple pages of results. [2]
Step 5. If you are working in Python, you can wrap the call in a reusable method. The pattern below illustrates the structure — replace self.c.request with your own HTTP client logic: [2]
def get_article_feedback_statistics(self, helpcenter_id: str, article_id: str, p: dict = None):
"""Get article feedback statistics"""
return self.c.request(
"GET",
f"/api/v1/helpcenter/{helpcenter_id}/articles/{article_id}/feedback/statistics",
p,
None
)Step 6. Parse the response payload returned by Zoho Desk. The statistics data will reflect the aggregated feedback for the specified article within the specified Help Center. [2]
Common pitfalls
- Mixing up IDs: Using a
helpcenteridfrom one portal with anarticleidfrom a different Help Center will result in an error or empty response. Always verify that both IDs belong to the same Help Center context. [2] - Undocumented vs. documented endpoints: The Zoho Desk community has noted that some reporting-related endpoints exist but are not officially documented (for example, paths like
/v1/reports/staticReports). We recommend relying only on documented endpoints such as the feedback statistics one above, since undocumented endpoints may change without notice. [1] - Pagination handling: The optional
pparameter suggests the response may be paginated. If you are expecting statistics across a large dataset, make sure your integration handles multi-page responses rather than assuming a single call returns everything. [2]
What to check
- Both IDs are correct: Verify your
helpcenteridandarticleidby cross-referencing them against a list call before hitting the statistics endpoint. [2] - OAuth token scope: Confirm your access token includes read permissions for Help Center articles; a missing scope is the most common cause of
401or403responses. [2] - Response completeness: Check whether the returned statistics cover the full date range you expect — if the article is new, there may be little or no feedback data yet. [2]
---
*Beam Help is an independent expert support resource for Zoho products and is not official Zoho support. For platform-level issues, always raise a ticket directly with the Zoho Desk support team.*