PSA Data Export guide

Create Zoho Desk API credentials for backup

At a glance

Set up least-privilege Zoho Desk read access using OAuth 2.0 scopes plus organization ID, with tenant and regional details checked before backup.

Published · Updated
On this page

Before you create credentials

Sign in as an administrator authorized to create integrations. Decide who owns rotation and revocation. Confirm the account plan exposes the modules you need and use a dedicated integration identity rather than a person's everyday login.

Create the Zoho Desk credential

Register an OAuth client in the correct Zoho data center, request read scopes, and record the Desk organization ID required on API calls. The current native model is OAuth 2.0 scopes plus organization ID. Follow the Zoho Desk official documentation in the live tenant because labels, available scopes, and regional hosts can change.

Choose read access

Request read access only for tickets and fields, threads and comments, contacts and accounts, and attachments and ticket history where exposed. Do not grant create, update, or delete permissions when the vendor offers separate scopes. Some products attach visibility to the underlying user role even when a token itself exists.

Record connection details safely

Keep the credential secret together with the tenant identifier, subdomain or base URL, region/data center, expiration date, and granted scopes. Do not paste secrets into tickets, screenshots, source control, browser localStorage, or this marketing site.

Validate the connection

Call a harmless documented read endpoint, confirm the expected tenant, then list a small sample from each selected record group. Record permission failures and unavailable modules. Every module request needs an OAuth token and the Desk orgId header; use the OAuth and API domain for the tenant's Zoho data center.

Rotate or revoke access

Create the replacement first, validate it, update the consuming application through its secret store, then revoke the prior credential. Recheck scheduled captures after a role, license, region, or owner changes.

Plan your independent PSA archive

Keep source history available after your move. Join the waitlist for invitation-only BackupPSA access, or contact us about your platform.

We’ll only use your email to contact you about BackupPSA access.

Questions about your PSA? Email contact@backuppsa.com.