> ## Documentation Index
> Fetch the complete documentation index at: https://signatureapi-daf4ee54.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Preparer

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

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](/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".</Note>

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

<img src="https://mintcdn.com/signatureapi-daf4ee54/UqiVROmDb8Tz-1YC/docs/images/text-input-guides.png?fit=max&auto=format&n=UqiVROmDb8Tz-1YC&q=85&s=2685172a19a6aa28a264f5c39f391f0d" alt="Text input" width="1090" height="258" data-path="docs/images/text-input-guides.png" />

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

<img src="https://mintcdn.com/signatureapi-daf4ee54/nTNmbAkpPw5L2NqU/docs/images/prepared-confirmation.png?fit=max&auto=format&n=nTNmbAkpPw5L2NqU&q=85&s=0d6b497b66644b25aee8dc86876354b0" alt="Prepared confirmation" width="606" height="285" data-path="docs/images/prepared-confirmation.png" />

<Note>Preparer actions are not recorded in the audit log. Only signer actions appear in the audit log attached to the deliverable.</Note>

## Workflow example

<Steps>
  <Step title="Create an envelope">
    Include a preparer recipient before any signers in the recipient list.
  </Step>

  <Step title="Preparer completes their ceremony">
    The preparer enters required information such as pricing, dates, or terms.
  </Step>

  <Step title="Subsequent recipients see the data">
    Recipients who act after the preparer see the document with the preparer's fields already filled in.
  </Step>

  <Step title="Signers complete signing">
    Signers review the document and add their signatures.
  </Step>
</Steps>

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

```json theme={null}
// POST https://api.signatureapi.com/v1/envelopes
// X-API-Key: key_test_...
// Content-Type: application/json

{
    "title": "Sales Agreement",
    "recipients": [
        {
            "key": "sales_rep",
            "type": "preparer",
            "name": "Alex Smith",
            "email": "alex@company.com"
        },
        {
            "key": "customer",
            "type": "signer",
            "name": "Jordan Lee",
            "email": "jordan@customer.com"
        }
    ],
    "routing": "sequential",
    //...
}
```

In this example, the sales representative fills in the agreement details first. Then the customer receives the document to sign. 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 text inputs, checkboxes, and dropdowns. Signature and initials places cannot be assigned to preparers.

```json theme={null}
{
    "documents": [
        {
            "places": [
                {
                    "type": "text_input",
                    "recipient_key": "sales_rep",
                    "key": "contract_value",
                    //...
                },
                {
                    "type": "signature",
                    "recipient_key": "customer",
                    //...
                }
            ],
            //...
        }
    ],
    //...
}
```

## Delivery

The `delivery_type` defaults to `none` for preparers. SignatureAPI does not send an invitation email. Your application is responsible for sharing the ceremony URL with the preparer.

Set `delivery_type` to `email` if you want SignatureAPI to send the invitation automatically.

## Next steps

* [Recipient object](/docs/api/resources/recipients/object) - See all recipient properties
* [Recipient lifecycle](/docs/api/resources/recipients/lifecycle) - Understand recipient status transitions
* [Create a ceremony](/docs/api/resources/ceremonies/create) - Customize how the preparer accesses the envelope
* [Approver](/docs/api/resources/recipients/approver) - Add a reviewer who approves without signing
* [Envelope routing](/docs/api/resources/envelopes/routing) - Configure the order recipients act on the envelope