# Send an Envelope Using a Template

Templates are ideal when you send the **same document repeatedly** (e.g. onboarding forms, sales contracts, compliance documents).

Using a Template means:

- Fields and signing steps are already configured
- You only supply signer details and any optional prefilled fields


## 📥 Workflow overview

1. Create your Template in the Signable web app
2. Retrieve Template details using its fingerprint
3. Submit the envelope request referencing the Template


> 💡 **Already authenticated?**
If not, follow the [Authentication guide](/authentication).


## Step 1 — Set up your Template (in the web app)

1. Go to [Templates](https://signable.app/templates/page/1)
2. Upload your document(s)
3. Add fields and parties
4. (Optional) Mark fields as **prefillable** if you want to populate them via API


## Step 2 — Retrieve Template details

Start by listing all Templates available to your account.

### 1. List your Templates

**Endpoint**


```http
GET https://api.signable.co.uk/v1/templates/
```

> For full endpoint details, see the **List Templates** reference: [GET List templates](/openapi/templates/listtemplates).


From the response, find the Template you want to use by checking the `template_title`. Copy its `template_fingerprint` — you’ll use this in the next request.

### 2. Retrieve details for a specific Template

**Endpoint**


```http
GET https://api.signable.co.uk/v1/templates/{template_fingerprint}
```

**Example response**


```http
{
  "http": 200,
  "template_id": "53690003",
  ...
  "template_parties": [
    {
      "party_id": "20459705",
      "party_name": "Party",
      "party_merge_fields": [
        {
          "field_id": "450927743",
          "field_merge": "Name of Sender",
          "field_type": "text"
        }
      ]
    }
  ]
}
```

### What this response tells you

You’ll see two important sets of identifiers:

- `party_id`: Unique IDs for each party defined in the Template.
You’ll use these in **Step 4** to attach real signers to the correct party positions.
- `field_id`: IDs of merge fields you can prefill in the envelope request.
For example, text fields, dates, or other prefillable inputs.


These IDs ensure your API request maps correctly to the Template’s structure.

## Step 3 — Create your envelope request

Once you’ve collected the `template_fingerprint`, `party_id`, and optional `field_id` values, you’re ready to send an envelope.

**Endpoint**


```http
POST https://api.signable.co.uk/v1/envelopes
```

**Example request body**


```http
{
    "envelope_title": "Melbourne Road 23/06/25",
    "envelope_parties": [
      {
        "party_name": "Alex Mitchell",
        "party_email": "abby+alex@signable.co.uk",
        "party_id": "20748256",
        "party_role": "signer"
      },
      {
        "party_name": "Abby Signers",
        "party_email": "abby@signable.co.uk",
        "party_id": "20748255",
        "party_role": "signer"
      }
    ],
    "envelope_documents": [
      {
        "document_title": "TC 2025 v2",
        "document_template_fingerprint": "28f9add86f25028df2eee9adee866aba",
        "document_merge_fields": [
          {
            "field_id": "454958773",
            "field_value": "Note that breakables are not included in rent cost"
          }
        ]
      }
    ]
  }
```

### What’s happening in this request

- Alex Mitchell is assigned to the Template party with `party_id: 20748256` for Template `28f9add86f25028df2eee9adee866aba`.
- The Template field with `field_id: 454958773` will be prefilled with: *“Note that breakables are not included in rent cost”.*


This assigns your signers to fields and adds prefilled content directly into the Template before it’s sent to the recipients.

## What happens next

- Signers receive an email with their signing link
- You receive an envelope fingerprint in API response
- You can subscribe to webhooks for status updates (optional)