Skip to content

Glossary

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.

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. Its ID is a plain UUID, such as eb4cf433-a8af-4161-b37b-7ef57d423e56.

What’s inside an envelope

PartWhat it is
Documents1 to 10 PDF or DOCX files. A DOCX can be a template that SignatureAPI fills with your data.
Recipients1 to 10 people (or automatic signers) who sign, approve or prepare the documents.
PlacesThe spots on each document where a recipient signs, initials or types, or where a value such as the completion date appears.
RoutingWhether recipients act one at a time (sequential, the default) or all at once (parallel).
SettingsLanguage, time zone, topics, metadata and the deliverable 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.
  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. Each change emits an envelope event, so you can follow it with webhooks instead of polling. See Envelope 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 are free. See Pricing.