# Send an Envelope Using Multiple Templates

You can also create and send a single envelope that pulls in multiple Templates.
This is useful when your workflow spans several documents, each with their own
fields and party setups (e.g. onboarding packs, contract bundles, multi-stage compliance flows).

The overall flow is the same as using a single Template:

1. **Create each Template** in the web app
2. **Retrieve Template details** (including `template_fingerprint`, `party_id`, and optional `field_id`)
3. **Submit an envelope request** — this is where there is a slight difference.


## Step 3 - Create your envelope request

> 💡 Make sure you've read [Send an Envelope Using a Template](/guides/send-envelope-template) before continuing.
The only difference is:


Inside each object in `envelope_parties`, instead of supplying a single `party_id`, include a `party_documents` array with:

- `party_id` — The party identifier from the specific Template
- `document_template_fingerprint` — The Template fingerprint that party position comes from


Everything else - merge fields, envelope title, notifications - works exactly the same as with a single Template.

**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_role": "signer",
        "party_documents": [
          {
            "party_id": 20748256,
            "document_template_fingerprint": "28f9add86f25028df2eee9adee866aba"
          },
          {
            "party_id": 20748265,
            "document_template_fingerprint": "88d2c9e8dc4a69ce1cd97ac1684f3e45"
          }
        ]
      },
      {
        "party_name": "Abby Signers",
        "party_email": "abby@signable.co.uk",
        "party_role": "signer",
        "party_documents": [
          {
            "party_id": 20748255,
            "document_template_fingerprint": "28f9add86f25028df2eee9adee866aba"
          }
        ]
      }
    ],
    "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"
          }
        ]
      },
      {
        "document_title": "TC 2025 v3",
        "document_template_fingerprint": "88d2c9e8dc4a69ce1cd97ac1684f3e45"
      }
    ]
  }
```

### What’s happening in this request

- Alex Mitchell is assigned to:
  - Template party with `party_id: 20748256` for Template `28f9add86f25028df2eee9adee866aba`, **and**;
  - Template party with `party_id: 20748265` for Template `88d2c9e8dc4a69ce1cd97ac1684f3e45`
- Abby Signers is assigned to:
  - Template party with `party_id: 20748255` 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)