---
title: "Concepts"
description: "The building blocks of SignatureAPI: envelopes hold documents and recipients, places mark where to sign, and deliverables return the signed files."
canonical: "https://signatureapi.com/docs/api/concepts"
source: "https://signatureapi.com/docs/api/concepts.md"
last_verified_api_version: "1.18.0"
last_modified: "2026-11-18T11:48:47Z"
---

# Concepts

The building blocks of SignatureAPI: envelopes hold documents and recipients, places mark where to sign, and deliverables return the signed files.

_Last verified against API version 1.18.0._

SignatureAPI organizes the document signing process around a few core concepts. An envelope holds documents and recipients. Places on each document say what each recipient fills in. Each recipient acts in a ceremony, and the completed envelope produces a deliverable.

**Anatomy of an envelope**

Parts:

- **[Envelope](https://signatureapi.com/docs/api/resources/envelopes/object)**: The container for documents and recipients. Produces the deliverable when it completes.
- **[Document](https://signatureapi.com/docs/api/resources/documents/object)**: A PDF or DOCX file inside the envelope. Holds the places.
- **[Recipient](https://signatureapi.com/docs/api/resources/recipients/object)**: A person or automatic signer who acts on the envelope.
- **[Place](https://signatureapi.com/docs/api/resources/places/object)**: A region on a document. Most places name the recipient who fills them in recipient_key.
- **[Ceremony](https://signatureapi.com/docs/api/resources/ceremonies/object)**: The session where a recipient reviews the documents and fills their places.
- **[Deliverable](https://signatureapi.com/docs/api/resources/deliverables/object)**: The signed documents and the audit log.

Connections:

- Envelope to Document: contains
- Envelope to Recipient: contains
- Document to Place: has
- Place to Recipient: assigned to
- Recipient to Ceremony: signs in
- Envelope to Deliverable: produces

| Part                                                                           | What it is                                                                                                           |
| ------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------- |
| [Envelope](https://signatureapi.com/docs/api/resources/envelopes/object)       | The container for documents and recipients. It tracks the signing workflow from creation to completion.              |
| [Document](https://signatureapi.com/docs/api/resources/documents/object)       | A PDF or DOCX file inside the envelope, provided as is or generated from a template.                                 |
| [Place](https://signatureapi.com/docs/api/resources/places/object)             | An interactive region on a document, such as a signature or a text input. Most places are assigned to one recipient. |
| [Recipient](https://signatureapi.com/docs/api/resources/recipients/object)     | A person or automatic signer who acts on the envelope.                                                               |
| [Ceremony](https://signatureapi.com/docs/api/resources/ceremonies/object)      | The session where a recipient reviews the documents and completes their places.                                      |
| [Deliverable](https://signatureapi.com/docs/api/resources/deliverables/object) | The signed documents and the audit log, produced when the envelope completes.                                        |

## Envelope

An [Envelope](https://signatureapi.com/docs/api/resources/envelopes/object) is a container that holds documents and recipients. It organizes and tracks the entire signing workflow from creation to completion.

## Documents

[Documents](https://signatureapi.com/docs/api/resources/documents/object) are the files within an envelope that recipients need to review and sign. You can provide PDFs directly or generate documents from [templates](https://signatureapi.com/docs/api/resources/documents/templates) with dynamic data.

Each document has [places](https://signatureapi.com/docs/api/resources/places/object): the regions where a recipient signs, initials, or enters information. A place's `recipient_key` names the recipient who completes it. A [text place](https://signatureapi.com/docs/api/resources/places/text) shows fixed text and has no recipient.

## Recipients

[Recipients](https://signatureapi.com/docs/api/resources/recipients/object) are the people who interact with the envelope. Each recipient has a [type](https://signatureapi.com/docs/api/resources/recipients/object#type) (signer, approver, preparer, automatic signer, or qualified signer) that determines what actions they can perform.

## Ceremony

A [Ceremony](https://signatureapi.com/docs/api/resources/ceremonies/object) is a guided session in which a recipient reviews the documents and performs their required actions, such as signing. Each recipient completes their own ceremony, and you can control the [signing order](https://signatureapi.com/docs/api/resources/envelopes/routing) (parallel or sequential).

## Deliverable

After all [recipients have completed](https://signatureapi.com/docs/api/resources/recipients/lifecycle) their actions, the [envelope is completed](https://signatureapi.com/docs/api/resources/envelopes/lifecycle). A [Deliverable](https://signatureapi.com/docs/api/resources/deliverables/object) is then generated, containing the signed documents and an audit log. The deliverable is sent to the recipients and is available for download via the API.
