Zoho Desk
Overview
Pre-built tooling
Pre-built integrations
No pre-built integration yet (time to contribute: <48h)
Access requirements
Pre-Requisites | Status | Comment |
---|---|---|
Paid dev account | ✅ Not required | Free Zoho account is sufficient for development. |
Paid test account | ✅ Not required | Free Zoho account is sufficient for testing. |
Partnership | ✅ Not required | |
App review | ✅ Not required | No review process for OAuth apps. |
Security audit | ✅ Not required |
Setup guide
Follow the general Zoho OAuth setup guide to create your OAuth application. When selecting scopes, make sure to include the Desk-specific scopes listed in the Common Scopes section below.
Useful links
- Zoho API Console
- Zoho Developer Hub
- OAuth 2.0 Overview
- Server-based Applications
- Get Authorization Code
- Get Access Token
- Refresh Access Token
- Multi DC Support
- OAuth Scopes
Desk-specific links
Common Scopes
- Desk.tickets.ALL - Access to all Desk tickets
- Desk.contacts.READ - Read access to Desk contacts
- Desk.contacts.UPDATE - Update access to Desk contacts
- Desk.contacts.CREATE - Create access to Desk contacts
- Desk.tasks.ALL - Access to all Desk tasks
- Desk.basic.READ - Basic read access to Desk
- Desk.search.READ - Search functionality in Desk
API gotchas
-
Zoho uses datacenter-specific URLs for authentication. Make sure to use the correct datacenter domain extension (
com
,eu
,in
,com.cn
,com.au
) based on where your user’s account is registered. -
Zoho has rate limits that vary by service. Check the specific service documentation for details.
-
If your application needs to access multiple Zoho services, you need to request scopes for each service during the authorization process.
-
For production applications, consider implementing multi-datacenter support to handle users from different regions.
Desk-specific gotchas
- Zoho Desk API has region-specific endpoints. You need to use the correct endpoint based on the user’s region.
- The Desk API has rate limits that vary based on your Zoho Desk plan.