---
title: "Glossary"
description: "Definitions of the terms used across the SignatureAPI docs, from envelope and ceremony to audit trail, trusted timestamp, PAdES and qualified signature."
canonical: "https://signatureapi.com/docs/glossary"
source: "https://signatureapi.com/docs/glossary.md"
last_verified_api_version: "1.18.0"
last_modified: "2026-11-18T13:06:40Z"
---

# Glossary

Definitions of the terms used across the SignatureAPI docs, from envelope and ceremony to audit trail, trusted timestamp, PAdES and qualified signature.

_Last verified against API version 1.18.0._

The terms you'll meet across these docs, each with a one-line definition and a link to the page that covers it in depth. Terms that need more than a line have their own explainer.

## Explainers

- [Envelope](https://signatureapi.com/docs/glossary/envelope): The container for documents and recipients, and the unit you're billed for.

- [Audit trail](https://signatureapi.com/docs/glossary/audit-trail): The record of who did what, and when, during signing.

- [Document hash](https://signatureapi.com/docs/glossary/document-hash): How a fingerprint of the file makes any later change visible.

- [Trusted timestamp](https://signatureapi.com/docs/glossary/timestamp): Proof from a timestamp authority that a document existed, unchanged, at a given time.

- [Advanced electronic signature](https://signatureapi.com/docs/glossary/advanced-electronic-signature): The middle eIDAS level, and why SignatureAPI doesn't produce it.

- [Qualified electronic signature](https://signatureapi.com/docs/glossary/qualified-electronic-signature): The highest eIDAS level, made with a certificate from a QTSP.

- [PAdES, CAdES and CMS](https://signatureapi.com/docs/glossary/signature-formats): The formats that carry a digital signature inside a PDF or next to any file.

## All terms

**Core concepts**

- **[Audit log](https://signatureapi.com/docs/api/resources/deliverables/standard)**: The record of every action taken during the signing process, with a certificate of completion. The standard deliverable includes it.
- **[Ceremony](https://signatureapi.com/docs/api/resources/ceremonies/object)**: A guided session in which a recipient reviews the documents and performs their required actions, such as signing.
- **[Deliverable](https://signatureapi.com/docs/api/resources/deliverables/object)**: The PDF generated after the envelope completes, with the signed documents and, by default, an audit log.
- **[Document](https://signatureapi.com/docs/api/resources/documents/object)**: A PDF or DOCX file in an envelope that recipients review and sign. A DOCX template can generate it from your data.
- **[Document hash](https://signatureapi.com/docs/glossary/document-hash)**: A short fingerprint of a file, such as its SHA-256. Changing one byte changes it, which is what makes a signed document tamper-evident.
- **[Envelope](https://signatureapi.com/docs/api/resources/envelopes/object)**: A container that holds documents and recipients. It organizes and tracks the signing workflow from creation to completion.
- **[Place](https://signatureapi.com/docs/api/resources/places/object)**: A location on a document where a recipient performs an action, such as signing or typing, or where information is displayed automatically.
- **[Recipient](https://signatureapi.com/docs/api/resources/recipients/object)**: A party to an envelope, usually a person. Its type (signer, approver, preparer, automatic signer or qualified signer) sets what it does.
- **[Routing](https://signatureapi.com/docs/api/resources/envelopes/routing)**: The order in which recipients receive and act on the envelope: sequential (the default: one at a time) or parallel.
- **[Template](https://signatureapi.com/docs/api/resources/documents/templates)**: A DOCX file with {{key}} fields that SignatureAPI merges with the data you send to produce the final document.
- **[Trusted timestamp](https://signatureapi.com/docs/glossary/timestamp)**: A signed token from a timestamp authority (RFC 3161) proving that data existed, unchanged, at a given time. Every deliverable seal carries one.

**Recipients**

- **[Approver](https://signatureapi.com/docs/api/resources/recipients/approver)**: A recipient who reviews documents, can fill in input places, and approves without signing. Approver actions are not recorded in the audit log.
- **[Automatic signer](https://signatureapi.com/docs/api/resources/recipients/automatic-signer)**: A recipient whose signature is applied automatically from images you provide, with a mandate. No ceremony and no email.
- **[Preparer](https://signatureapi.com/docs/api/resources/recipients/preparer)**: A recipient who fills in document fields before signers receive the envelope. Preparer actions are not recorded in the audit log.
- **[Qualified signer](https://signatureapi.com/docs/api/resources/recipients/qualified-signer)**: A recipient who signs with a qualified electronic signature (QES) through your own trust service provider.
- **[Signer](https://signatureapi.com/docs/api/resources/recipients/signer)**: A recipient who reviews documents and adds a signature or initials. Every envelope needs at least one signing recipient.

**Qualified signatures**

- **[Advanced electronic signature (AdES)](https://signatureapi.com/docs/qualified-signatures)**: A signature uniquely linked to the signer, that identifies them, made with data under their sole control, and that shows later changes.
- **[CMS signature](https://signatureapi.com/docs/glossary/signature-formats)**: Cryptographic Message Syntax, also called PKCS#7: the container for a digital signature. CAdES and PAdES signatures are built on it.
- **[Digest](https://signatureapi.com/docs/qualified-signatures/how-it-works)**: A short fingerprint of the exact document the signer reviewed. The signer's approval is bound to it, and the worker sees only the digest.
- **[eIDAS](https://signatureapi.com/docs/qualified-signatures)**: The EU regulation on electronic identification and trust services (Regulation (EU) No 910/2014). It defines three levels of electronic signature.
- **[PAdES](https://signatureapi.com/docs/qualified-signatures/how-it-works)**: The standard format for signatures inside a PDF. Each qualified signature sits in the deliverable as a PAdES signature.
- **[Qualified certificate](https://signatureapi.com/docs/qualified-signatures)**: The digital certificate a QTSP issues in the signer's name. A qualified signature is made with one.
- **[Qualified electronic signature (QES)](https://signatureapi.com/docs/qualified-signatures)**: An advanced signature made with a qualified certificate. It has the same legal effect as a handwritten signature in every EU member state.
- **[Qualified trust service provider (QTSP)](https://signatureapi.com/docs/qualified-signatures)**: A company that an EU supervisory body approved to verify identities and issue qualified certificates. You choose the provider.
- **[Sandbox worker](https://signatureapi.com/docs/qualified-signatures/how-it-works)**: The hosted worker that stands in for a provider in test mode. Its certificates are not qualified.
- **[Signing worker](https://signatureapi.com/docs/qualified-signatures/signing-workers)**: An HTTPS service, run by you or your provider, that translates SignatureAPI's requests into calls to the provider's API.
- **[Simple electronic signature (SES)](https://signatureapi.com/docs/qualified-signatures)**: Any electronic data a person uses to sign: a typed name, a drawn signature, a click. A regular signer produces one.

## Related

- [Concepts](https://signatureapi.com/docs/api/concepts): how envelopes, documents, recipients, places, ceremonies and deliverables fit together.
- [Are electronic signatures legal?](https://signatureapi.com/docs/legal-validity/overview): ESIGN, UETA and eIDAS in plain words.
- [FAQ](https://signatureapi.com/docs/faq): short answers to common questions.
