Zoho Desk

Connect Zoho Desk to collect ticketing evidence with automated compliance tests, switched on per workspace.

Connect with an API token

1. In Zoho Desk:

   1. Sign in to the Zoho API Console (api-console.zoho.com).
   2. Click GET STARTED, hover over the Self Client option and click CREATE NOW.
   3. Click CREATE, then click OK. The Client ID and Client Secret appear under the Client Secret tab.
   4. Open the Generate Code tab. Enter the Zoho Desk read scopes Safeguard needs (Zoho refers you to the product's API documentation for scope names), choose an expiry time (the default is 3 minutes), add a description, and click CREATE.
   5. Select Zoho Desk and the required portal, then click CREATE again. Copy or download the authorization code.
   6. Exchange the code for tokens with a POST to {accounts-server-url}/oauth/v2/token using client_id, client_secret, grant_type=authorization_code and code. Paste the returned access_token into Safeguard.

   Where to find the other values:

   • Data center (optional): Use the data center where your Zoho account is registered. Zoho's accounts servers are accounts.zoho.com (US), accounts.zoho.eu (EU), accounts.zoho.in (IN), accounts.zoho.com.au (AU), accounts.zoho.jp (JP), accounts.zohocloud.ca (CA), accounts.zoho.sa (SA) and accounts.zoho.uk (UK); the token response's api_domain also shows which one applies.

   Zoho Desk's public documentation does not cover every step.

   Zoho access tokens are valid for 1 hour; the refresh token from the same exchange does not expire and is used to mint new access tokens. The scope name Desk.basic.READ from the earlier draft and per-data-center API Console addresses were not on the fetched pages. Where the Zoho Desk UI shows the Organization ID (orgId) could not be confirmed from an official page: the Desk API reference (desk.zoho.com/DeskAPIDocument) was too large to fetch, and web search was unavailable. Zoho Desk also returns the orgId from its GET /api/v1/organizations endpoint per that API reference (not verified in this pass).

   Source: zoho.com, zoho.com, zoho.com, checked 2026-10-07.

   The permissions Safeguard needs: Desk.basic.READ. Safeguard's compliance tests for Zoho Desk need the credential on the API token tab: an OAuth connection cannot read everything they check.

2. On Compliance › Connectors, open Zoho Desk, click Connect, choose API token and fill in:

   Field	What to enter
   Organization ID	Required.
   Access token	Required. Stored encrypted and never shown again.
   Data center (optional)	—

3. Click Connect with token.

Frameworks

Safeguard's automated tests read Zoho Desk and map to the controls below. When a test passes, the result is evidence toward each control it maps to, in every framework listed. It is evidence toward a control, not proof that the control is met on its own.

These tests are switched on per workspace by the Safeguard team.

Related

• Ticketing connectors
• Compliance connectors: how connecting works, card statuses and multiple accounts
• Connector setup reference: every connector in one table
• Frameworks and connectors: how connectors provide evidence for frameworks