Deliverables are the final, tamper-proof output of a completed envelope. Until now, every deliverable shipped with the same structure: signed documents followed by an audit log and certificate of completion. Starting today, deliverables come in two flavors, standard and simple, so you can pick the shape that best fits each workflow.
Standard and simple
Standard is the default and matches the existing behavior. It includes every signed document along with an appended audit log and a certificate of completion that lists recipient actions, timestamps, and authentication details. This is the right choice when you need a full evidentiary record in a single file.
Simple contains only the signed documents, with no audit log pages appended to the PDF. It’s useful when the audit trail is tracked elsewhere, when you want a cleaner end-user artifact, or when downstream systems expect the document to end exactly as it was originally authored.
Both types carry the same cryptographic seal and can be verified for integrity at any time. The audit log remains accessible through the API for simple deliverables, so nothing is lost, only relocated.
Creating deliverables
You can generate additional deliverables on a completed envelope through the Create Deliverable endpoint and pass the type field to choose between standard and simple. See the deliverable object docs for the full schema.
