What is an Approver?

An Approver represents any person that needs to validate the content of a Signature Request before it can be signed. It can be, for example, a manager or a member of the legal service.

The use of Approvers allows you to build up a validation workflow for your Signature Requests. Indeed, a Signer will NOT be notified and therefore won't be able to sign a Signature Request until every Approver has given their approbation.

Add an Approver to a Signature Request

• Endpoint: Create a new Approver
• URL: POST /signature_requests/{signatureRequestId}/approvers
• Description: Adds an Approver to a given Signature Request.

An Approver can be any person implied in the validation process of a Signature Request. Therefore, it can be added in several ways:

• From scratch, by adding their first name, last name and email.
• As an existing User through its unique identifier.
• As an existing Contact through its unique identifier.
• As an existing Signer through its unique identifier. If a person is intended to approve and sign a Signature Request, it must be added as a Signer AND an Approver.

🚧

Limitations

• A maximum of 10 approvers can be added per Signature Request.

All the endpoints available to manage Approvers can be found in our API Reference.

What if an Approver rejects a Signature Request?

If an Approver refuses to validate a Signature Request, it is possible for them to add a refusal reason. This value can be retrieved in the approver.rejected webhook event (see webhook payload).

Set Approvers order

When configuring a Signature Request, you can choose whether Approvers must complete their actions in a specific order or simultaneously.

If you choose the sequential option, you can also set the exact order in which which Approvers must complete their actions.

For more details, see Configure recipient ordering.