---
title: "What is an e-signature envelope?"
description: "An envelope holds the documents to sign and the people who sign them. Learn what goes in one, how it moves from processing to completed, and how it is billed."
canonical: "https://signatureapi.com/docs/glossary/envelope"
source: "https://signatureapi.com/docs/glossary/envelope.md"
last_verified_api_version: "1.18.0"
last_modified: "2026-11-18T18:19:06Z"
---

# What is an e-signature envelope?

An envelope holds the documents to sign and the people who sign them. Learn what goes in one, how it moves from processing to completed, and how it is billed.

_Last verified against API version 1.18.0._

An **envelope** is the container for one signing transaction. It holds the documents to sign, the recipients who act on them, and the settings that control how signing happens. The name comes from paper: you put the contract in an envelope, address it to the signers, and send it.

In SignatureAPI, you create an envelope with one request to [Create an envelope](https://signatureapi.com/docs/api/resources/envelopes/create). Its ID is a plain UUID, such as `eb4cf433-a8af-4161-b37b-7ef57d423e56`.

## What's inside an envelope

| Part                                                                        | What it is                                                                                                                                                                                                                                                                                                                                                                                                              |
| --------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [Documents](https://signatureapi.com/docs/api/resources/documents/object)   | 1 to 10 PDF or DOCX files. A DOCX can be a [template](https://signatureapi.com/docs/api/resources/documents/templates) that SignatureAPI fills with your data.                                                                                                                                                                                                                                                          |
| [Recipients](https://signatureapi.com/docs/api/resources/recipients/object) | 1 to 10 people (or automatic signers) who sign, approve or prepare the documents.                                                                                                                                                                                                                                                                                                                                       |
| [Places](https://signatureapi.com/docs/api/resources/places/object)         | The spots on each document where a recipient signs, initials or types, or where a value such as the completion date appears.                                                                                                                                                                                                                                                                                            |
| [Routing](https://signatureapi.com/docs/api/resources/envelopes/routing)    | Whether recipients act one at a time (`sequential`, the default) or all at once (`parallel`).                                                                                                                                                                                                                                                                                                                           |
| Settings                                                                    | [Language](https://signatureapi.com/docs/api/resources/envelopes/language), [time zone](https://signatureapi.com/docs/api/resources/envelopes/timezone), [topics](https://signatureapi.com/docs/api/resources/envelopes/topics), [metadata](https://signatureapi.com/docs/api/resources/envelopes/metadata) and the [deliverable](https://signatureapi.com/docs/api/resources/deliverables/object) you want at the end. |

## How an envelope moves

An envelope has one `status` at a time:

1. **`processing`**: SignatureAPI downloads the documents, merges templates and finds the places.
2. **`in_progress`**: recipients are signing. Each one gets a [ceremony](https://signatureapi.com/docs/api/resources/ceremonies/object).
3. **`completed`**: every recipient has finished. SignatureAPI builds the deliverable.

An envelope can also end as **`failed`**, when an error stops it during processing or signing, or **`canceled`**, when you [cancel it](https://signatureapi.com/docs/api/resources/envelopes/cancel). Each change emits an [envelope event](https://signatureapi.com/docs/api/resources/events/envelope-events), so you can follow it with webhooks instead of polling. See [Envelope lifecycle](https://signatureapi.com/docs/api/resources/envelopes/lifecycle) for every transition.

## Envelopes and billing

An envelope is also the unit SignatureAPI bills. Only completed envelopes count, and the number of documents or recipients doesn't change the count: two documents sent to three signers is one envelope. [Test envelopes](https://signatureapi.com/docs/api/test-mode) are free. See [Pricing](https://signatureapi.com/pricing).

## Related

- [The envelope object](https://signatureapi.com/docs/api/resources/envelopes/object): every field.
- [Quickstart](https://signatureapi.com/docs/api/guides/quickstart): create your first envelope.
- [Glossary](https://signatureapi.com/docs/glossary): other terms.
