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

# Prepare a Document Before Sending to Sign

> Use a preparer to fill in document fields before the envelope reaches the signer

A **preparer** is a recipient who fills in document fields before the envelope reaches a signer. This is useful when one person needs to populate document data on behalf of another. For example, a sales representative can enter pricing, dates, or contract terms before the customer receives the document to sign.

Preparers can complete text inputs, checkboxes, and dropdowns, but cannot add signatures or initials. After filling in all required fields, the preparer clicks **Finish**, and the envelope proceeds to the next recipient.

In this example, we will create an envelope with:

* A single PDF document.
* A preparer (a sales representative) who fills in a text input field with the contract value.
* A signer (the customer) who receives the document after the preparer has finished and adds their signature.
* Sequential routing so the preparer acts before the signer.

## Prepare your Document

Placeholders are text markers within your PDF document indicating specific locations for items such as signatures, initials, or text inputs. Each placeholder follows the format `[[place_key]]`, where `place_key` uniquely identifies the specific location within your document.

In this example, we have prepared a document containing two placeholders:

* `[[contract_value]]` marks the position where the preparer will enter the contract value as a text input.
* `[[customer_signature]]` marks the position where the signer will place their signature.

<Tip>In our document, the placeholders are highlighted in blue for visibility. However, we recommend setting them to white so they remain invisible to recipients.</Tip>

## Create the Envelope

When creating the envelope:

* Set `routing` to `sequential` (this is the default, but it is good practice to set it explicitly).
* Add recipients in the order they should act. The preparer must appear before the signer in the recipients array.
* Add place objects to the `places` array inside the document object:
  * For the preparer's text input: set `type` to `text_input` and `recipient_key` to the preparer's key.
  * For the signer's signature: set `type` to `signature` and `recipient_key` to the signer's key.

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

{
    "title": "Sales Agreement",
    "routing": "sequential",
    "documents": [
        {
            "url": "https://example.com/sales-agreement.pdf",
            "places": [
                {
                    "key": "contract_value",
                    "type": "text_input",
                    "recipient_key": "sales_rep"
                },
                {
                    "key": "customer_signature",
                    "type": "signature",
                    "recipient_key": "customer"
                }
            ]
        }
    ],
    "recipients": [
        {
            "key": "sales_rep",
            "type": "preparer",
            "name": "Alex Smith",
            "email": "alex@company.com"
        },
        {
            "key": "customer",
            "type": "signer",
            "name": "Jordan Lee",
            "email": "jordan@customer.com"
        }
    ]
}
```

<Note>The `delivery_type` for preparers defaults to `none`, meaning the completed deliverable will not be automatically emailed to the preparer. Set `delivery_type` to `email` if you want SignatureAPI to deliver the completed deliverable by email.</Note>

## Result

The preparer (Alex Smith) accesses the document first and fills in the contract value field. After clicking **Finish**, the envelope proceeds to the signer.

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

The signer (Jordan Lee) then receives the document with the preparer's field already filled in and can review the completed details before adding their signature.

## Try It

[Try this example in Postman](/docs/api/postman) using your [test API key](/docs/api/test-mode) to create a free, non-binding test envelope. Test envelopes won't send emails, but you can review them in your dashboard.

## Keep Learning

* Learn more about the [preparer recipient type](/docs/api/resources/recipients/preparer) and how it differs from other recipient types.
* Explore other [types of places](/docs/api/resources/places/object), such as [checkboxes](/docs/api/resources/places/checkbox), [dropdowns](/docs/api/resources/places/dropdown), or [text inputs](/docs/api/resources/places/text-input).
* Learn about [sequential signing](/docs/api/guides/how-to/sequential-signing) for workflows where the order of signing matters.
* Learn about [parallel signing](/docs/api/guides/how-to/parallel-signing) for workflows where recipients can sign in any order.