Skip to main content
An approver is a recipient who reviews and approves documents without adding a signature. Approvers can fill in input places, but they cannot add signatures or initials. Use approvers for workflows that need a review or authorization step before the document reaches a signer. Common examples include:
  • Manager approval before a contract is sent to an external party
  • Compliance review before finalization
  • Internal sign-off where a formal signature is not required
  • Multi-stage approval workflows with different levels of authorization
Approvers are functionally equivalent to preparers. The difference is in the wording shown during the ceremony. Approvers see “Approve” as the final action. Preparers see “Finish”.

​
Approver vs. signer

ApproverSigner
Reviews documentsYesYes
Fills in input placesYesYes
Adds signature or initialsNoYes
Recorded in audit logNoYes
Recipient typeapproversigner
Use an approver when someone needs to authorize a document without creating a signature record. Use a signer when a legally binding signature is required.

​
The approver’s ceremony

The approver accesses the envelope through the approver’s ceremony. The approver reviews the documents and fills in any input places assigned to them, such as text boxes or checkboxes. After completing all required actions, the approver clicks Approve. Approve button A confirmation screen appears once the approval is complete. Approved confirmation
Approver actions are not recorded in the audit log. Only signer actions appear in the audit log attached to the deliverable.

​
Workflow example

1

Create an envelope

Include an approver recipient before any signers in the recipient list.
2

Approver completes their ceremony

The approver reviews the documents and fills in any assigned input places.
3

Subsequent recipients see the data

Recipients who act after the approver see the document with the approver’s fields already filled in.
4

Signers complete signing

Signers review the approved document and add their signatures.

​
Creating an envelope with an approver

Specify "type": "approver" for recipients who should review and approve without signing. Use sequential routing so the approver acts before the signer. 
// POST https://api.signatureapi.com/v1/envelopes
// X-API-Key: key_test_...
// Content-Type: application/json

{
    "title": "Service Agreement",
    "recipients": [
        {
            "key": "manager",
            "type": "approver",
            "name": "Sarah Chen",
            "email": "sarah@company.com"
        },
        {
            "key": "client",
            "type": "signer",
            "name": "Michael Torres",
            "email": "michael@client.com"
        }
    ],
    "routing": "sequential",
    //...
}
In this example, the manager reviews and approves the agreement first. Then the client receives the document to sign.

​
Assigning places to an approver

Approvers can fill in text inputs, checkboxes, and dropdowns. Assign places to an approver using the recipient_key property. Signature and initials places cannot be assigned to approvers. 
{
    "documents": [
        {
            "places": [
                {
                    "type": "text_input",
                    "recipient_key": "manager",
                    "key": "approval_notes",
                    //...
                },
                {
                    "type": "checkbox",
                    "recipient_key": "manager",
                    "key": "terms_reviewed",
                    //...
                }
            ],
            //...
        }
    ],
    //...
}
The values the approver enters are visible to recipients who act after them.

​
Delivery

The delivery_type defaults to none for approvers. SignatureAPI does not send an invitation email. Your application is responsible for sharing the ceremony URL with the approver. Set delivery_type to email if you want SignatureAPI to send the invitation automatically.

​
Next steps