How to retrieve article statistics in Zoho Desk

Zoho Desk exposes two dedicated API endpoints that let you pull both general engagement statistics and feedback-specific statistics for any Help Center article programmatically — no manual UI export required.

Why this matters

If you maintain a knowledge base inside Zoho Desk, understanding how individual articles perform is critical for content optimisation. Rather than logging into the portal each time, you can automate data collection — for dashboards, scheduled reports, or quality-review pipelines — by calling these endpoints directly. This is especially useful for teams managing large Help Centers with hundreds of articles across multiple departments.

Step-by-step

Step 1. Gather your required identifiers.

Before making any call, you need two IDs: the helpcenterid for the Help Center that hosts the article, and the articleid for the specific article you want to analyse. Both are available in the Zoho Desk admin panel or can be retrieved via earlier list-type API calls. Optionally, you can pass a p parameter (a dictionary/object) for any additional query options supported by the endpoint. ^[1]

Step 2. Call the general article statistics endpoint.

Send a GET request to the following path, substituting your real IDs:

GET /api/v1/helpcenter/{helpcenter_id}/articles/{article_id}/statistics

This returns engagement data for the specified article — such as view counts and related metrics. In Python, the call looks like this: ^[1]

result = client.get_article_statistics(
    helpcenter_id="your_helpcenter_id",
    article_id="your_article_id"
)

The method issues a GET request to the path above and returns the parsed response. ^[1]

Step 3. Call the article feedback statistics endpoint.

To retrieve reader feedback data (e.g., helpful/not-helpful votes) for the same article, send a GET request to a separate path:

GET /api/v1/helpcenter/{helpcenter_id}/articles/{article_id}/feedback/statistics

The same helpcenterid and articleid parameters apply, and an optional p dictionary can be passed for filtering. In Python: ^[5]

result = client.get_article_feedback_statistics(
    helpcenter_id="your_helpcenter_id",
    article_id="your_article_id"
)

This call is distinct from the general statistics endpoint and targets the /feedback/statistics sub-resource specifically. ^[5]

Step 4. Handle the response.

Both endpoints return their data as structured response objects. Parse the returned payload according to your use case — for example, writing values to a database, feeding a BI tool, or triggering alerts when an article's feedback score drops below a threshold. Because both calls share the same parameter signature (helpcenterid, articleid, optional p), you can loop over a list of article IDs to batch-collect statistics across your entire Help Center. [^1,5]

Common pitfalls

• Confusing the two endpoints. The general statistics path ends at .../statistics, while the feedback path includes .../feedback/statistics as an intermediate segment. Mixing them up will return a 404 or the wrong dataset. [^1,5]
• Undocumented vs. documented endpoints. The Zoho Desk community has noted that some reporting-related paths (such as /v1/reports/staticReports) appear to be undocumented and therefore unreliable for production use. Stick to the documented article statistics endpoints covered here to avoid breakage after platform updates. ^[2]
• Missing or incorrect IDs. Passing a helpcenter_id that does not match the portal associated with your API credentials will result in an authorisation or not-found error. Always verify both IDs before automating calls at scale. ^[1]

What to check

• Confirm both IDs resolve correctly — make a simple GET on the article itself before appending /statistics to ensure the helpcenterid and articleid combination is valid. ^[1]
• Verify the feedback endpoint returns distinct data — the /feedback/statistics response should contain vote or rating fields that are absent from the general statistics response; if both look identical, double-check the URL path. ^[5]
• Review rate limits and pagination — if you are looping over many articles, check whether the optional p parameter supports pagination flags to avoid hitting API rate limits. [^1,5]

---

*Beam Help is an independent expert support resource for Zoho products and is not official Zoho support. Always cross-reference with the latest Zoho Desk API documentation for your data centre region.*