Understanding Signing Process Data

Introduction

A signing process data object contains all information related to a signing process. Integrators have full freedom to choose how this information is displayed to their end‑users.

Behind the scenes, a signing process in the Sign API corresponds to a Leap project. Both represent a workflow structure that defines how the process progresses, who is involved, the status of each task, and other operational details.

Because the signing process data includes a large amount of information, the sections below highlight the most relevant fields to help integrators understand and use them effectively.

Relevant fields in signing process data

Signing process data is presented in JSON format.

Fields				Notes
`id`				ID of the signing process.
`name`				Name of the signing process.
`projectUrl`				A link for the Project Owner to view the status of the signing process. This link provides direct access. Please treat it as sensitive information.
`anchors[]`	`anchorDocument`	`id`		ID of the document to be signed.
	`anchorDocument`	`fileName`		Name of the document to be signed.
	`steps[]`	`tasks[]`	`id`	ID of a Sign task.
			`taskStatus`	Status of a Sign task.
			`taskUrl`	A link for the Signer to open the signing interface and complete the document signing. This link provides direct access. Please treat it as sensitive information.

The signing process data includes more fields than those listed here. If you require further information or assistance, feel free to contact us at support@documill.com.