---
title: "Approver"
description: "A recipient type who reviews and approves documents without adding a signature"
canonical: "https://signatureapi.com/docs/api/resources/recipients/approver"
source: "https://signatureapi.com/docs/api/resources/recipients/approver.md"
last_verified_api_version: "1.18.0"
last_modified: "2026-11-18T17:41:33Z"
---

# Approver

A recipient type who reviews and approves documents without adding a signature

_Last verified against API version 1.18.0._

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

> **Note:** Approvers are functionally equivalent to [preparers](https://signatureapi.com/docs/api/resources/recipients/preparer). The difference is in the wording shown during the ceremony. Approvers see "Approve" as the final action. Preparers see "Finish".

## Approver vs. signer

|                            | Approver   | Signer   |
| -------------------------- | ---------- | -------- |
| Reviews documents          | Yes        | Yes      |
| Fills in input places      | Yes        | Yes      |
| Adds signature or initials | No         | Yes      |
| Recorded in audit log      | No         | Yes      |
| Recipient type             | `approver` | `signer` |

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**. A confirmation screen appears once the approval is complete.

**Video: Approve an envelope**

An approver reviews the document in the ceremony, selects Approve, and sees the confirmation screen.

[Watch the video](https://signatureapi.com/videos/approver-approve.mp4)
[Captions (WebVTT)](https://signatureapi.com/videos/approver-approve.vtt)

> **Note:** Approver actions are not recorded in the audit log. Only signer actions appear in the audit log attached to the deliverable.

### Rejecting

Instead of approving, the approver can select **Reject** and enter a reason to reject. Then:

- The approver's status becomes `rejected`, and a `recipient.rejected` event is emitted. An embedded ceremony also sends the `ceremony.declined` [message](https://signatureapi.com/docs/embedded/ceremony-events).
- The envelope stays `in_progress` but can't complete, and recipients after the approver are not notified.
- To continue, [replace the approver](https://signatureapi.com/docs/api/resources/recipients/replace) with someone else, or [cancel the envelope](https://signatureapi.com/docs/api/resources/envelopes/cancel).

See [Declined requests](https://signatureapi.com/docs/api/resources/recipients/lifecycle#declined-requests) in the recipient lifecycle.

## 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.

```http {8,19}
POST /v1/envelopes HTTP/1.1
Host: api.signatureapi.com
X-API-Key: YOUR_API_KEY
Content-Type: application/json

{
  "title": "Service Agreement",
  "routing": "sequential",
  "documents": [
    {
      "url": "https://pub-9cb75390636c4a8a83a6f76da33d7f45.r2.dev/docs-samples/acme-service-agreement.pdf",
      "places": [
        { "key": "client_signs_here", "type": "signature", "recipient_key": "client" },
        { "key": "provider_signs_here", "type": "signature", "recipient_key": "provider" }
      ]
    }
  ],
  "recipients": [
    { "type": "approver", "key": "manager", "name": "Alex Chen", "email": "alex.chen@example.com" },
    { "type": "signer", "key": "client", "name": "Jane Doe", "email": "jane.doe@example.com" },
    { "type": "signer", "key": "provider", "name": "John Smith", "email": "john.smith@example.com" }
  ]
}
```

In this example, the manager reviews and approves the agreement first. Then the two signers receive the document in order.

## Assigning places to an approver

Approvers, like preparers, can fill in input places: text inputs, checkboxes, dropdowns, radio groups and the other input types. Assign places to an approver using the `recipient_key` property. Signature and initials places cannot be assigned to approvers: the request fails with [`incompatible-places`](https://signatureapi.com/docs/v1/errors/incompatible-places). Input places need [sequential routing](https://signatureapi.com/docs/api/resources/envelopes/routing).

```json Places assigned to the approver
[
  { "key": "approval_notes", "type": "text_input", "recipient_key": "manager" },
  { "key": "terms_reviewed", "type": "checkbox", "recipient_key": "manager" }
]
```

The values the approver enters are visible to recipients who act after them.

## Delivery

The `delivery_type` controls whether SignatureAPI emails the completed deliverable to the approver. It defaults to `none`, so the approver does not receive the deliverable. Set it to `email` if you want them to receive it.

The approver receives an email with the ceremony link when their ceremony uses `email_link` authentication, which is the default. To share the ceremony URL yourself instead, create the ceremony with [`custom` authentication](https://signatureapi.com/docs/api/guides/how-to/custom-authentication).

## Next steps

- [Recipient lifecycle](https://signatureapi.com/docs/api/resources/recipients/lifecycle) - Understand recipient status transitions
- [Create a ceremony](https://signatureapi.com/docs/api/resources/ceremonies/create) - Customize how the approver accesses the envelope
- [Signer](https://signatureapi.com/docs/api/resources/recipients/signer) - Add a recipient who signs documents
- [Preparer](https://signatureapi.com/docs/api/resources/recipients/preparer) - Add a recipient who fills in fields before signing
- [Create an envelope](https://signatureapi.com/docs/api/resources/envelopes/create) - Include approvers in a new envelope
