How to retrieve article history in Zoho Desk

Retrieving article history in Zoho Desk is done through a dedicated Help Center API endpoint that accepts your Help Center ID and Article ID as path parameters.

Why this matters

When your team manages a knowledge base inside Zoho Desk, tracking how articles have changed over time is essential for auditing, quality control, and rollback decisions. If you are building an integration or automation that needs to surface revision data programmatically, knowing the correct endpoint and required identifiers saves significant trial-and-error. This is particularly useful for teams that publish and update support articles frequently and need a reliable audit trail.

Step-by-step

Step 1. Confirm you have a valid Zoho Desk API connection in place, including a current OAuth access token and your organisation ID (orgid). The Zoho Desk client must be initialised with your API domain, access token, and org ID before any calls can succeed. If your token has expired, the connection layer should handle a refresh using your stored refreshtoken before proceeding.^[3]

Step 2. Identify the two required path parameters you will need for the request:

• helpcenter_id — the unique identifier of the Help Center where the article lives.
• article_id — the unique identifier of the specific article whose history you want to retrieve.

Both values are strings and must be substituted directly into the endpoint path.^[2]

Step 3. Make a GET request to the following endpoint, replacing the placeholders with your actual IDs:^[2]

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

Step 4. Optionally, pass a pagination parameter p as a query parameter if you expect a large number of history entries and need to page through results. This parameter is supported by the endpoint but is not required for a basic call.^[2]

Step 5. In Python, using the Zoho Desk API wrapper, the call looks like this:^[2]

history = api.get_article_history(
    helpcenter_id="your_helpcenter_id",
    article_id="your_article_id",
    p={}  # optional pagination dict
)

The method issues a GET request internally and returns the history payload for the specified article.^[2]

Step 6. Parse the response. The returned data will contain the revision history for that article. Inspect the response structure to extract the fields relevant to your use case, such as timestamps, editor information, or version content.^[2]

Common pitfalls

• Missing or stale access token. If your OAuth token has expired and the refresh logic fails (for example, because the refresh_token is no longer stored), the API call will be rejected. Always verify that token refresh is working correctly before making article history requests.^[3]
• Wrong orgid. Zoho Desk requires the organisation ID to be set on the client. If orgid is blank or incorrect, requests will fail or return data from the wrong organisation. The recommended approach is to auto-discover the org ID by calling the organisations endpoint on first use and persisting it for subsequent calls.^[3]
• Confusing Help Center ID with Portal ID. The endpoint specifically requires a helpcenter_id, not a general portal or department ID. Using the wrong identifier will result in a 404 or empty response.^[2]

> Note: Beam Help is independent expert support for Zoho and is not official Zoho support. If you need vendor-level assistance, contact Zoho directly through your account portal.

What to check

• Confirm that the helpcenterid and articleid values you are using actually exist in your Zoho Desk instance by cross-referencing them in the Desk admin UI before making the API call.^[2]
• Verify your OAuth access token is valid and that your token refresh mechanism is correctly updating the stored accesstoken and tokenexpires_at fields after each refresh.^[3]
• Check that the org_id on your Desk client is populated; if it is empty, trigger the auto-discovery flow against the organisations endpoint to retrieve and persist the correct value.^[3]