Add or replace document in envelope
Adds or replaces a document in an existing draft or in-process envelope. An in-process envelope is one that has been sent but not yet completed or voided.
Note: When adding or modifying documents for an in-process envelope, Docusign recommends locking the envelope prior to making any changes.
To add a new document, set the documentId path parameter to a new document ID.
To replace a document, set the documentId path parameter to the document ID of the existing document.
The tabs of the original document will be applied to the new document.
For example, a request in cURL looks like this:
If HTML document files contain <img> elements with the src attribute set to a path or URL, those images will not be displayed. Images in HTML files must be encoded in Base64 format, like this:
<img src="data:image/gif;base64,R0lGODlh...IQAAOw==" alt="Base64 encoded image" width="150" height="150"/>
Related topics
Authentication
OAuth 2.0 access token (JWT or auth-code grant). Sent as
Authorization: Bearer <token> on every request except
GET /v2.1 and GET /service_information, which are
public discovery endpoints.
Path parameters
The external account number (int) or account ID Guid.
The unique ID of the document within the envelope.
Unlike other IDs in the eSignature API,
you specify the documentId yourself.
Typically the first document has the ID
1, the second document 2, and so on,
but you can use any numbering scheme
that fits within a 32-bit signed integer
(1 through 2147483647).
Tab objects have a documentId property
that specifies the document on which to place
the tab.
The envelope’s GUID.
Example: 93be49ab-xxxx-xxxx-xxxx-f752070d71ec
Request
Response
If recipients were added by converting form fields into tabs, their IDs appear here. This property is read-only.
When true, the document has editable form fields that are made available through a PDF format.
This string sets the display and behavior properties of the document during signing. Valid values:
modal
The document is shown as a supplement action strip and can be viewed, downloaded, or printed in a modal window. This is the recommended value for supplemental documents.
inline
The document is shown in the normal signing window. This value is not used with supplemental documents, but is the default value for all other documents.
The document’s bytes. This field can be used to include a base64 version of the document bytes within an envelope definition instead of sending the document using a multi-part HTTP request. The maximum document size is smaller if this field is used due to the overhead of the base64 encoding.
When true,
the document is included in the combined document download (documentsCombinedUri). This is only applied to supplemental documents.
The default value is true.
The document’s file name.
Example: Q1-Report.docx
The order in which to sort the results.
Valid values are:
asc: Ascending order.desc: Descending order.
Sets how the signer interacts with the supplemental document. Valid values:
no_interaction
No recipient action is required.
view
The recipient is required to view the document.
accept
The recipient is required to accept the document by selecting accept during signing, but is not required to view the document.
view_accept
The recipient is required to view and accept the document.
When true, the sender cannot change any attributes of the recipient. Used only when working with template recipients.
When true, the sender may not remove the recipient. Used only when working with template recipients.
The type of this tab. Values are:
ApproveCheckBoxCompanyDateDateSignedDeclineEmailEmailAddressEnvelopeIdFirstNameFormulaFullNameInitialHereInitialHereOptionalLastNameListNoteNumberRadioSignerAttachmentSignHereSignHereOptionalSsnTextTitleZip5Zip5Dash4