Zoho Sign
Connect Zoho Sign to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Record your Zoho Sign connection as digital signature evidence.
| Category | Digital Signature |
| Connect with | API token |
| What a connection produces | Connection record |
Connect with an API token
-
In Zoho Sign:
- Sign in to the Zoho API Console at
https://api-console.zoho.com/and click Add Client ID to register a client; note the Client ID and Client Secret it gives you. - Under the Generate Code tab, enter read-only scopes (for example
ZohoSign.documents.READ,ZohoSign.templates.READ,ZohoSign.account.READ), set the time duration and click CREATE. Copy the generated code. - Exchange the code for tokens with
POST https://accounts.zoho.com/oauth/v2/token?code=<Code>&client_id=<Client ID>&client_secret=<Client Secret>&redirect_uri=<Redirect URL>&grant_type=authorization_code, and paste the access token into Safeguard's API token / Personal access token field.
Where to find the other values:
- Base URL (optional): Not shown in a documented UI location. Zoho's quick start uses
https://accounts.zoho.comfor tokens; data-center-specific domains are not listed on the fetched pages. - Account / Org / Workspace (optional): Not shown in a documented UI location.
Zoho Sign's public documentation does not cover every step.
Zoho Sign has no static API key; it uses OAuth 2.0. Access tokens usually expire in one hour, while the refresh token stays valid until revoked, so a pasted access token goes stale fast. Zoho's quick start example uses the broad ZohoSign.documents.ALL,ZohoSign.templates.ALL scopes; the READ scopes come from the OAuth scope list. The client type choice in the API Console (for example a self client) was not described on the fetched page.
- Sign in to the Zoho API Console at
-
On Compliance › Connectors, open Zoho Sign, click Connect, choose API token and fill in:
Field What to enter API token / Personal access token Required. Stored encrypted and never shown again. Base URL (optional) - Account / Org / Workspace (optional) - -
Click Connect with token.
Frameworks
Zoho Sign publishes no API for what these tests check, so its evidence is an attestation: connect it to record the connection, then attest the result. An accepted attestation counts toward each control below.
| Framework | Evidence | Controls | Tests |
|---|---|---|---|
| SOC2 | Attestation | CC6.2, CC6.3 | 1 |
| ISO/IEC 27001 | Attestation | A.5.18 | 1 |
| HIPAA Security Rule | Attestation | 164.308(a)(3) | 1 |
| PCI DSS | Attestation | 7.2.4 | 1 |
| NIST CSF 2.0 | Attestation | PR.AA-05 | 1 |
Related
- Digital Signature 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