How to get view records count in Zoho Desk

Retrieving the record count for a specific view in Zoho Desk is straightforward using the Desk REST API — a single GET request returns the total number of records associated with any given view ID.

Why this matters

When building dashboards, automations, or reporting tools on top of Zoho Desk, you often need to know how many records (tickets, contacts, etc.) belong to a particular saved view without fetching every record. This count endpoint lets you surface that number efficiently, without pagination overhead or unnecessary data transfer. It's also useful for conditional logic — for example, triggering an alert only when a view exceeds a certain ticket threshold.

Step-by-step

Step 1. Ensure your OAuth token includes the correct Zoho Desk scopes before making any API calls. At minimum you will need scopes such as Desk.tickets.READ and Desk.basic.READ to access view data. A full working scope set also covers contacts, tasks, settings, and search — for example Desk.tickets.ALL, Desk.contacts.READ, Desk.search.READ, and others depending on what your view surfaces. ^[2]

Step 2. Identify the view_id for the view whose record count you want. You can retrieve the total number of views available in your portal first by calling the views count endpoint:

GET /api/v1/views/count

This operation (getviewcount) accepts an optional parameter p for additional query options and returns the number of views configured in your Desk portal. ^[7]

Step 3. Once you have the view_id, call the view records count endpoint:

GET /api/v1/views/{view_id}/records/count

Replace {viewid} with the actual ID of the view you are querying. The operation name is getviewrecordscount and it accepts two parameters: view_id (required, the view identifier) and p (optional, a dictionary of additional query parameters). ^[1]

Step 4. In Python, the call looks like this:

def get_view_records_count(self, view_id: str, p: dict = None):
    """Get View Records Count"""
    return self.c.request("GET", f"/api/v1/views/{view_id}/records/count", p, None)

Pass your target view_id as a string, and optionally supply a p dict if you need to filter or paginate the count query. ^[1]

Step 5. To initialise the Zoho Desk API client correctly, make sure your connection object carries the deskorgid. The client is constructed using your API domain, a valid access token, the organisation ID, and a token-refresh callback. If the org_id is missing, the client will attempt to auto-discover it by calling the organisations endpoint on first use. ^[8]

Step 6. Handle the response in your application. The API returns the count value which you can extract and display, log, or use in conditional logic. If the result is None or the response is empty, treat this as an inability to determine the count and surface an appropriate message to the user. ^[3]

Common pitfalls

• Missing or incorrect view_id: Passing an invalid or non-existent view ID will result in an error response. Always validate the view ID by listing available views before querying their record counts. ^[7]
• Insufficient OAuth scopes: If your token does not include the relevant Desk.tickets.READ or module-specific READ scope, the API will reject the request. Double-check your configured scopes match the data the view is built on. ^[2]
• Missing deskorgid: The Zoho Desk client requires an organisation ID to route requests correctly. If this is absent from your connection configuration, the client will attempt discovery automatically, but this adds latency and can fail if the organisations endpoint is also scope-restricted. ^[8]
• Confusing view count vs. view records count: There are two distinct endpoints — one returns how many *views* exist (GET /api/v1/views/count), and the other returns how many *records* are inside a specific view (GET /api/v1/views/{view_id}/records/count). Make sure you are calling the right one for your use case. ^[1][7]

What to check

• OAuth scopes are correctly set — confirm your token includes at minimum Desk.tickets.READ and Desk.basic.READ before making the call. ^[2]
• The view_id is valid — verify the ID exists in your portal by first calling GET /api/v1/views/count and listing available views. ^[7]
• The API response contains a non-null count value — if the result is empty or None, check your deskorgid configuration and token validity before assuming the view is empty. ^[8][3]

---

*Beam Help provides independent expert guidance for Zoho products and is not official Zoho support.*