canonical: https://jentic.com/apis/zoho.com/zoho-sign-api

# Zoho Sign API

Digital signature API for sending, signing, and managing documents. The API exposes 9 endpoints secured with oauth2 authentication.

## For AI agents

Programmatically get account info, list users. Covers 9 operations with oauth2 authentication.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- Get account info
- List users
- Create document request
- Update request
- Delete request

## Use cases

### Developer Tools Operations

Use the Zoho Sign API to perform developer tools operations programmatically. The API provides 9 endpoints covering core functionality including get account info, list users, create document request.

Example prompt: Call GET /accounts to get account info

### Automated Accounts Management

Automate accounts operations by combining multiple Zoho Sign API endpoints. Agents can list users and then create document request in a single workflow.

Example prompt: Call GET /users to list users, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Zoho Sign API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle oauth2 tokens manually.

Example prompt: Search Jentic for 'get account info', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /accounts | Get account info |
| GET | /users | List users |
| POST | /requests | Create document request |
| GET | /requests | List document requests |
| GET | /requests/{request_id} | Get document request |
| PUT | /requests/{request_id} | Update request |
| DELETE | /requests/{request_id} | Delete request |
| GET | /templates | List templates |

## Key resources

- **Accounts** — Operations related to Accounts
- **Requests** — Operations related to Requests
- **Templates** — Operations related to Templates
- **Users** — Operations related to Users

## Why Jentic

- **Setup:** Wiring Zoho Sign by hand means running its OAuth 2.0 flow, refreshing tokens, and mapping request and template shapes against the sign.zoho.com host yourself. Through Jentic you install once, import Zoho Sign from the API Directory, store the OAuth credential once, and your agent calls it.
- **Permission scoping:** Zoho Sign puts the request id in the URL path (/requests/{request_id}), so a rule can pin your agent to one signature request: it can read and update that request and nothing else. You choose the operations it may call, so destructive ones like request deletion are not included unless you add them.
- **Credential handling:** Your Zoho Sign OAuth credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'get account info' or 'create a signature request', and Jentic returns the matching Zoho Sign operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the Zoho Sign API use?

The Zoho Sign API uses OAuth 2.0 for authorization. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I get account info with the Zoho Sign API?

Yes. Use the GET /accounts endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Zoho Sign API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I get account info through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get account info'. Jentic returns the matching Zoho Sign API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Zoho Sign API have?

The Zoho Sign API exposes 9 endpoints covering accounts, requests, templates operations.

### Can I limit what my agent is allowed to do with the Zoho Sign API?

Yes. Because you run Jentic One yourself, your own rules decide which Zoho Sign operations and which OAuth credential the agent may use. Since the request id sits in the URL path (/requests/{request_id}), you can pin the agent to a single signature request so it only reads and updates that one request and nothing else. You choose the operations it can call, so destructive ones like request deletion (DELETE /requests/{request_id}) stay off unless you explicitly add them.