How to list agent teams in Zoho Desk

Retrieving the teams associated with a specific agent in Zoho Desk is straightforward using the REST API — a single GET request returns the full list of teams linked to that agent's ID.

Why this matters

When building integrations, automations, or admin dashboards on top of Zoho Desk, you often need to know which teams an agent belongs to — for example, to route tickets correctly, audit team membership, or synchronise data with an external system. Rather than navigating the UI manually for each agent, the API lets you retrieve this information programmatically at scale. As independent expert support for Zoho (not official Zoho support), Beam Help documents this endpoint so your developers can get up and running quickly.

Step-by-step

Step 1. Identify the agent_id of the agent whose teams you want to list. This is the unique identifier Zoho Desk assigns to each agent record. You can obtain it from a prior API call that returns agent details, or from your Zoho Desk admin panel. ^[6]

Step 2. Construct the request using the following endpoint pattern:

GET /api/v1/agents/{agent_id}/teams

Replace {agent_id} with the actual numeric or string identifier for the agent you are querying. ^[6]

Step 3. Optionally, include the p parameter in your query string to control pagination if the agent belongs to a large number of teams. Pass it as a dictionary of key-value pairs alongside your request. ^[6]

Step 4. Send the authenticated GET request to the Zoho Desk API base URL for your data centre, appending the path above. A successful response will return the list of teams associated with that agent. ^[6]

Step 5. If you are working in Python, the call can be structured as shown below, where agent_id is a string and p is an optional dictionary of query parameters:

def list_associated_teams_of_agent(self, agent_id: str, p: dict = None):
    return self.c.request("GET", f"/api/v1/agents/{agent_id}/teams", p, None)

This wraps the endpoint in a reusable method on your API client object. ^[6]

Common pitfalls

• Wrong data centre base URL. Zoho Desk operates across multiple regional data centres (US, EU, IN, AU, etc.). Make sure the base URL you prefix to /api/v1/agents/{agent_id}/teams matches the data centre where your Zoho Desk account is hosted, otherwise you will receive authentication or 404 errors. ^[6]
• Missing or expired OAuth token. All Zoho Desk API calls require a valid OAuth 2.0 access token in the Authorization header. If your token has expired, the request will be rejected before it reaches the endpoint. ^[6]
• Invalid agent_id format. Passing a malformed or non-existent agent ID will result in an error response. Always validate the ID against a known agent list before making the call. ^[6]

What to check

• Confirm the agent ID is correct by cross-referencing it with your Zoho Desk agent roster before calling the endpoint.
• Verify pagination — if the response appears incomplete, check whether additional pages exist by inspecting the response metadata and adjusting the p parameter accordingly. ^[6]
• Inspect team membership in the UI after your API call to confirm the returned team list matches what is configured under your Zoho Desk admin settings, ensuring the data is current. ^[6]