Zoho Sign icon

Zoho Sign

Interact with the Zoho Sign API

Document → Update

AI-generated

Summary

Update information regarding an existing document signing request in Zoho Sign by modifying its properties such as name, category, notes, expiration, signing order, reminders, folder placement, and recipient actions.

Inputs

  • Request ID (required) — Request ID associated with the document signing request to update
  • Request Name — New name for the signature request
  • Select Request Type ID (required) — Document category ID to assign to the request
  • Notes — Message to be sent to all recipients in common
  • Expiration Days — Number of days after which the document signing request will expire
  • Is Sequential (required) — Whether signing is sequential (true) or parallel (false)
  • Email Remainder — Whether to send automatic email reminders to recipients
  • Remainder Period — Interval in days to send automatic reminders
  • Folder ID — Folder ID to move the request into
  • Actions Mapping Mode — Choose between 'simple' to manually set limited action options or 'complex' to provide a full JSON for recipient actions
  • Actions (required) — In 'simple' mode, list of recipient actions such as SIGN or VIEW with recipient details and optional verification
  • Actions JSON (required) — In 'complex' mode, JSON string describing detailed recipient actions
  • Simplify Output (required) — Whether to return a simplified output or the full response

Output shape

a single record

Returns the updated request details including its status, name, owner email, request type, and recipient actions. The output can be simplified or detailed depending on the 'Simplify Output' parameter.

Examples

Example 1: Update a document request with new name, category, notes, expiration, and recipient actions in simple mode

Provide the required Request ID and Request Type ID, optionally set other fields, select 'simple' actions mapping, and list the recipient actions with emails and signing roles

Example 2: Update a document request using complex JSON for recipient actions

Provide Request ID and Request Type ID, optionally other fields; set actions mapping to 'complex' and supply a JSON string with detailed recipient actions structure

Links

Discussion