# Zoho Sign Integration via LowCodeAPI

**Last Updated**: February 11, 2026

## Overview

Electronic signature

The Zoho Sign API provides access to:

- **Zoho Suite** - Related functionality

## Base Endpoint

```
https://api.lowcodeapi.com/zohosign/
```

**Important**: Always include the provider name in the URL path after `api.lowcodeapi.com/`

## Authentication

LowCodeAPI handles authentication automatically. You only need to:

1. **Sign up** at [Zoho Sign](https://www.zoho.com/en-in/sign)
2. **Get your credentials** from [credential page](https://accounts.zoho.com/developerconsole)
3. **Connect your account** in LowCodeAPI dashboard
4. **Use your `api_token`** in all requests

The `api_token` is your LowCodeAPI authentication token. LowCodeAPI will automatically:
- Fetch your provider credentials (API keys, OAuth tokens, etc.)
- Apply them to each request
- Handle token refresh for OAuth providers

**Auth Type**: OAUTH2.0

## URL Format (Important)

LowCodeAPI supports **two URL formats** for endpoints with path parameters. **Always try New Format first**, and only fall back to Old Format if it doesn't work.

### New Format (Priority) - Dynamic Path Parameters

- **Path parameters stay in the URL path** - Do NOT convert to query parameters
- **Provider name is always in the URL path** after `api.lowcodeapi.com/`
- Pattern: `https://api.lowcodeapi.com/{provider}/{path_with_params}?api_token={api_token}`

**Example**:
```bash
# New Format - Path parameter stays in the URL path
https://api.lowcodeapi.com/zohosign/resource/{RESOURCE_ID}?api_token=YOUR_API_TOKEN
```

### Old Format (Fallback) - Sanitized Path + Query Parameters

- **Path parameters become query parameters**
- **Provider name is always in the URL path**
- Pattern: `https://api.lowcodeapi.com/{provider}/{sanitized_path}?{path_params}&api_token={api_token}`

**Example**:
```bash
# Old Format - Path parameter becomes a query parameter
https://api.lowcodeapi.com/zohosign/resource/id?id=RESOURCE_ID&api_token=YOUR_API_TOKEN
```

### Decision Flow for AI Agents

1. Always use **New Format first** - Keep path parameters in the URL path
2. If you get a 404 or error, try **Old Format** with sanitized path
3. Log which format worked for future requests to this provider

## API Categories

- **Document Management** - 2 endpoints
- **Template Management** - 2 endpoints

## Common Endpoints

### Category: Document Management

#### Create document

**Method**: `POST` | **LowCodeAPI Path**: `/api/v1/requests`

**New Format (Priority)**:
```bash
https://api.lowcodeapi.com/zohosign/api/v1/requests?api_token=YOUR_API_TOKEN
```

**Old Format (Fallback)**:
```bash
https://api.lowcodeapi.com/zohosign/api/v1/requests?api_token={api_token}
```

**Description**: This will create a new document

**Request Body**:
```json
{
  "key": "value"
}
```

**Request Body Fields**:

| Field | Type | Required | Description |
|-------|------|----------|-------------|
| ` action_type` | string | No |   Recipient Action [SIGN|VIEW|INPERSONSIGN|APPROVER] |
| `is_sequential` | boolean | No | Sequential signing / Parallel Signing |
| `recipient_email` | string | No | Recipient email  |
| `recipient_name` | string | No |   Recipient name |
| `request_name` | string | No | name to be given to the signature request |
| `verify_recipient` | boolean | No | Inperson recipient name |

**Example Request**:
```bash
# NEW FORMAT (PRIORITY) - Path parameters stay in URL
curl -X POST "https://api.lowcodeapi.com/zohosign/api/v1/requests?api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"key": "value"}'
```

**Example Response**:
```json
{
  "data": {
    // Provider response here
  }
}
```

**Official Documentation**: [Create document](https://www.zoho.com/sign/api/document-managment/create-document.html)

---

#### Update document

**Method**: `PUT` | **LowCodeAPI Path**: `/api/v1/requests/[request_id]`

**New Format (Priority)**:
```bash
https://api.lowcodeapi.com/zohosign/api/v1/requests/[request_id]?api_token=YOUR_API_TOKEN
```

**Old Format (Fallback)**:
```bash
https://api.lowcodeapi.com/zohosign/api/v1/requests/request_id?request_id={request_id}&api_token={api_token}
```

**Description**: This will help you to update an existing document

**Path Parameters**:

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `request_id` | string | Yes | Request Id |

**Request Body**:
```json
{
  "key": "value"
}
```

**Request Body Fields**:

| Field | Type | Required | Description |
|-------|------|----------|-------------|
| ` verify_recipient` | boolean | No | Authentication needs to be done or not |
| `action_type` | string | No | Recipient Action [SIGN | VIEW | INPERSONSIGN | APPROVER] |
| `in_person_name` | string | No | Inperson recipient name |
| `is_sequential` | boolean | No | Sequential signing / Parallel Signing |
| `recipient_email` | string | No | Recipient email  |
| `recipient_name` | string | No | Recipient name |
| `request_name` | string | No | name to be given to the signature request |

**Example Request**:
```bash
# NEW FORMAT (PRIORITY) - Path parameters stay in URL
curl -X PUT "https://api.lowcodeapi.com/zohosign/api/v1/requests/[request_id]?api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"key": "value"}'
```

**Example Response**:
```json
{
  "data": {
    // Provider response here
  }
}
```

**Official Documentation**: [Update document](https://www.zoho.com/sign/api/document-managment/update-document.html)

---

### Category: Template Management

#### Update template

**Method**: `PUT` | **LowCodeAPI Path**: `/api/v1/templates/[template_id]`

**New Format (Priority)**:
```bash
https://api.lowcodeapi.com/zohosign/api/v1/templates/[template_id]?api_token=YOUR_API_TOKEN
```

**Old Format (Fallback)**:
```bash
https://api.lowcodeapi.com/zohosign/api/v1/templates/template_id?template_id={template_id}&api_token={api_token}
```

**Description**: This will help you to update an existing template.

**Path Parameters**:

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `template_id` | string | Yes | Template Id |

**Request Body**:
```json
{
  "key": "value"
}
```

**Request Body Fields**:

| Field | Type | Required | Description |
|-------|------|----------|-------------|
| `action_type` | srting | No | Recipient Action [SIGN | VIEW | INPERSONSIGN] |
| `in_person_name` | srting | No | Inperson recipient name |
| `is_sequential` | boolean | No | Sequential signing / Parallel Signing[true/false] |
| `recipient_email` | srting | No | Recipient email  |
| `recipient_name` | srting | No | Recipient name  |
| `role` | srting | No | Role of the recipient |
| `template_name` | number | No | name to be given to the signature request |
| `verify_recipient` | boolean | No | Authentication needs to be done or not |

**Example Request**:
```bash
# NEW FORMAT (PRIORITY) - Path parameters stay in URL
curl -X PUT "https://api.lowcodeapi.com/zohosign/api/v1/templates/[template_id]?api_token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"key": "value"}'
```

**Example Response**:
```json
{
  "data": {
    // Provider response here
  }
}
```

**Official Documentation**: [Update template](https://www.zoho.com/sign/api/template-managment/update-template.html)

---

#### Get template details

**Method**: `GET` | **LowCodeAPI Path**: `/api/v1/templates/[template_id]`

**New Format (Priority)**:
```bash
https://api.lowcodeapi.com/zohosign/api/v1/templates/[template_id]?api_token=YOUR_API_TOKEN
```

**Old Format (Fallback)**:
```bash
https://api.lowcodeapi.com/zohosign/api/v1/templates/template_id?template_id={template_id}&api_token={api_token}
```

**Description**: Get the details of a particular template using its id - specifically lists the pre fill fields that need to be sent in order to convert the template into a document

**Path Parameters**:

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `template_id` | string | Yes | Template Id |

**Example Request**:
```bash
# NEW FORMAT (PRIORITY) - Path parameters stay in URL
curl -X GET "https://api.lowcodeapi.com/zohosign/api/v1/templates/[template_id]?api_token=YOUR_API_TOKEN"
```

**Example Response**:
```json
{
  "data": {
    // Provider response here
  }
}
```

**Official Documentation**: [Get template details](https://www.zoho.com/sign/api/template-managment/get-template-details.html)

---

## API Definition Endpoints

You can retrieve the complete OpenAPI specification for this provider using these endpoints:

**New Format (OpenAPI spec with dynamic path parameters):**
```bash
curl -X GET "https://backend.lowcodeapi.com/zohosign/openapi"
```

**Old Format (API definition with sanitized paths):**
```bash
curl -X GET "https://backend.lowcodeapi.com/zohosign/definition"
```

## Response Format

All responses from LowCodeAPI are wrapped in a `data` key:

```json
{
  "data": {
    // Actual response from provider API
  }
}
```

The `data` key contains the raw response from the provider's API.

## Complete Endpoint Reference

For a complete list of all 4 endpoints, refer to:
- **Official Provider Documentation**: https://www.zoho.com/sign/api/

## Usage Examples

### Example 1: Basic API Request (New Format)

Making a simple request to Zoho Sign:

```bash
# Replace RESOURCE_ID with an actual resource ID from your Zoho Sign account
curl -X GET "https://api.lowcodeapi.com/zohosign/resource/{RESOURCE_ID}?api_token=YOUR_API_TOKEN"
```

### Example 2: Request with Query Parameters (New Format)

Request with specific parameters:

```bash
# Include query parameters for filtering
curl -X GET "https://api.lowcodeapi.com/zohosign/resources?filter=value&api_token=YOUR_API_TOKEN"
```

## Error Handling

Standard HTTP status codes apply. All responses are wrapped in a `data` key:
```json
{
  "data": {
    // Actual response from provider
  }
}
```