---
title: "Preparer"
description: "A recipient type who fills in document fields on behalf of other signers"
canonical: "https://signatureapi.com/docs/api/resources/recipients/preparer"
source: "https://signatureapi.com/docs/api/resources/recipients/preparer.md"
last_verified_api_version: "1.18.0"
last_modified: "2026-11-18T12:07:52Z"
---

# Preparer

A recipient type who fills in document fields on behalf of other signers

_Last verified against API version 1.18.0._

A **preparer** is a recipient who fills in document fields before the envelope reaches a signer. Preparers can complete text inputs, checkboxes, and dropdowns, but they cannot add signatures or initials.

Use preparers when someone needs to populate document data before a signer receives the envelope. Common examples include:

- A sales representative entering pricing, dates, or contract terms
- An internal team member adding details visible to other recipients
- An administrator collecting information separately from signatures

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

## The preparer's ceremony

The preparer accesses the envelope through the **preparer's ceremony**.

The preparer reviews the documents and fills in all input places assigned to them. These places may include:

- Text input fields for names, dates, or other values
- Checkboxes for selecting options
- Other data entry fields defined in the document

![Text input](https://signatureapi.com/docs/images/text-input-guides.webp)

After filling in all required places, the preparer clicks **Finish**. The envelope then proceeds to the next recipient.

![Prepared confirmation](https://signatureapi.com/docs/images/prepared-confirmation.webp)

> **Note:** Preparer 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 a preparer recipient before any signers in the recipient list.

2. **Preparer completes their ceremony**

   The preparer enters required information such as pricing, dates, or terms.

3. **Subsequent recipients see the data**

   Recipients who act after the preparer see the document with the preparer's fields already filled in.

4. **Signers complete signing**

   Signers review the document and add their signatures.

## Creating an envelope with a preparer

Specify `"type": "preparer"` for recipients who should fill in fields before the signer receives the document. Use sequential routing so the preparer acts first.

```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": "preparer", "key": "sales_rep", "name": "Sam Patel", "email": "sam.patel@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 sales representative fills in the agreement details first. Then the two signers receive the document in order. With sequential routing, the preparer's input is visible to the signer.

## Assigning places to a preparer

Assign places to a preparer using the `recipient_key` property. Preparers can fill in input places, such as text inputs, checkboxes, dropdowns and radio groups. Signature and initials places cannot be assigned to preparers: 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 for the preparer and a signer
[
  { "key": "contract_value", "type": "text_input", "recipient_key": "sales_rep" },
  { "key": "client_signs_here", "type": "signature", "recipient_key": "client" }
]
```

## Delivery

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

The preparer 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 object](https://signatureapi.com/docs/api/resources/recipients/object) - See all recipient properties
- [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 preparer accesses the envelope
- [Approver](https://signatureapi.com/docs/api/resources/recipients/approver) - Add a reviewer who approves without signing
- [Envelope routing](https://signatureapi.com/docs/api/resources/envelopes/routing) - Configure the order recipients act on the envelope
