- Introduction
- OAuth
- API Endpoint
- Quick start with Zoho Sign's API
- Postman collection
- SwaggerHub
- Basic concepts
- Getting started with Zoho Sign's API under 2 minutes
- Signer groups
- Document Management
- POSTCreate document
- PUTUpdate document
- POSTSend document for signature
- POSTCorrect document
- GETGet details of a particular document
- GETGet documents list
- GETDownload PDF
- GETDownload particular PDF file
- GETDownload completion certificate
- GETGet document form data
- POSTRecall Document
- POSTRemind Recipient
- PUTDelete Document
- PUTExtend document
- POSTCreate new Folder
- GETGet folder list
- GETRetrieve field type
- GETGet document type
- POSTCreate new document type
- POSTUpdate document type
- Template Management
- Embedded Signing
- Embedded Sending
- Use Cases
- How-to guides
- Sending a signing request via SMS
- Enforce authentication
- Add fields to your document
- In-Person signing
- Sign documents with digital signature providers
- Sending documents in bulk
- eStamping
- Collecting payments from my recipients
- Adding witness to your envelope
- Manages recipients
- Sending an envelope to a signer group
- Replace signer group with normal recipients
- API error codes
- API limitation
- Security
- Contact details for technical assistance
Setting authentication mode to recipient
To enforce authentication for a particular recipient, verify_recipient parameter to be set as true and verification mode has to be set in verification_type parameter supports EMAIL, SMS, and OFFLINE.
Sample Payload
{
"requests": {
"actions": [
{
"verify_recipient": true,
"verification_type": "EMAIL",
"recipient_countrycode_iso": "IN", // pass if SMS OTP
"recipient_phonenumber": "9999999999", // pass if SMS OTP
"verification_code": "123456" // pass if OFFLINE
}
]
}
}
© 2025, Zoho Corporation Pvt. Ltd. All Rights Reserved.