Envelope Sending Options
This document contains alternative envelope-sending endpoints for share-code, Quick Send, public Quick Send, and One-time Send.
DocStudio provides several endpoints for sending envelopes in addition to the standard POST /api/v1/envelope/send flow. The correct endpoint depends on whether the envelope uses a reusable template, uploaded external documents, a public sending flow, or a one-time template.
Business goals
The envelope-sending endpoints support the following business goals:
Send from a shared template. Use a share code and verification code to create and send an envelope without referencing the template UUID directly.
Send external documents quickly. Upload existing files and define recipients without constructing template and envelope XML.
Provide a public sending flow. Allow a signer to send one external document through a verification-code-based request.
Use a template once. Send an envelope from inline template and envelope XML when the template must not remain available for reuse.
Choose a sending method
POST /api/v1/envelope/send
Send from an existing reusable template
Template UUID and template version
POST /api/v1/envelope/send-by-share-code
Send from a shared template
Share code and verification code
POST /api/v1/envelope/quick-send
Send one or more external documents from a mailbox
API token and Mailbox header
POST /api/v1/envelope/public-quick-send
Publicly send one external document
Verification code and signer email
POST /api/v1/envelope/one-time-send
Send from inline template and envelope XML
Template is marked as deleted after use
Use the standard Send Envelope endpoint when the template must remain reusable. The sections below describe the alternative sending methods.
Quick Send and Public Quick Send
Authentication
API token and Mailbox header
Public verification-code flow
Files
One or more files parts
One file part
Recipient input
recipients array
One signer email
Endpoint
/api/v1/envelope/quick-send
/api/v1/envelope/public-quick-send
Send an envelope by share code
Use POST /api/v1/envelope/send-by-share-code when a template is made available through a share code. The request contains the share code, its verification code, and the envelope XML serialized as a JSON string.
See XML payloads for guidance on serializing envelope XML as a JSON string.
Request
shareCode
string
Yes
Share code that identifies the shared template
verificationCode
string
Yes
Verification code for the shared-template flow
data
string
Yes
Envelope XML serialized as a JSON string
agreed
boolean
No
Indicates whether the required agreement was accepted
Response
A successful request returns 201 Created. Save the returned identifiers and token because they identify the created envelope and its mailbox context.
token
UUID
Token returned for the share-code sending flow
envelopeUuid
UUID
UUID of the created envelope
mailboxUuid
UUID
UUID of the mailbox associated with the envelope
Quick Send external documents
Use POST /api/v1/envelope/quick-send to send existing files without preparing template XML. The request uses multipart/form-data and contains one or more files together with a JSON data part.
The operation requires an API token and the sender mailbox UUID in the Mailbox header.
Headers
Authorization
Yes
Bearer authorization token
Mailbox
Yes
UUID of the sender mailbox
Accept
No
application/json
Request parts
files
array of binary files
Yes
External documents included in the envelope
data
JSON object
Yes
QuickSendDTO sent as a blob with Content-Type: application/json
The data object supports the following properties:
subject
string
Yes
Envelope subject
message
string
No
Message displayed to recipients
recipients
array
No
Recipients and their required actions
signatureAlgorithm
string
No
Signature algorithm: DSTU4145 or ECDSA_RSA
signatureContainer
string
No
Signature container: P7S, ASICE, or P7S_ENVELOPED
recipientExperience
object
No
Language, locale, and time-zone settings for recipients
Each object in recipients supports these properties:
recipient
string
Yes
Recipient identifier
approver
boolean
No
Requires the recipient to approve the document
signer
boolean
No
Requires the recipient to sign the document
eInkSignature
boolean
No
Enables an electronic handwritten signature action
The recipient value identifies the recipient. The example uses an email address. Set the recipient action fields required by the workflow.
When recipientExperience is included, provide its required properties:
language
en
Recipient interface language
locale
en-US
Recipient locale
timezone
Europe/Kyiv
Recipient time zone
Practical example: Send a contract for signature
The following request uploads a PDF contract and sends it to a signer:
A successful request returns 201 Created with the envelope UUID:
Public Quick Send
Use POST /api/v1/envelope/public-quick-send to send one external document through a public verification-code-based flow. Unlike Quick Send, this endpoint accepts one file and does not define a Mailbox header.
The request uses multipart/form-data. The data part must be sent as a JSON blob with Content-Type: application/json.
Request parts
file
binary file
Yes
External document included in the envelope
data
JSON object
Yes
Public sending configuration
The data object contains the following properties:
verificationCode
string
Yes
Verification code for the public sending flow
agreed
boolean
No
Indicates whether the required agreement was accepted
signer
Yes
Email address of the signer
Practical example: Publicly send one document
A successful request returns 201 Created. The response uses id as the envelope identifier:
Use Send Envelope when the document flow requires a reusable template.
One-time Send
Use POST /api/v1/envelope/one-time-send when the integration provides both the template XML and envelope XML in the request. The template is used for this sending operation and is then marked as deleted.
Headers
Authorization
Yes
Bearer authorization token
Content-Type
Yes
application/json
Mailbox
Yes
UUID of the sender mailbox
Request
templateXml
string
Yes
Template XML serialized as a JSON string
envelopeXml
string
Yes
Envelope XML serialized as a JSON string
signatureAlgorithm
string
No
Signature algorithm: DSTU4145 or ECDSA_RSA
signatureContainer
string
No
Signature container: P7S, ASICE, or P7S_ENVELOPED
Response
A successful request returns 201 Created with the created envelope UUID:
Error handling
Share-code sending can return 405 Method Not Allowed when the server disables share-code sending. For complete error response schemas and status codes, use the Swagger UI.
Related topics
Last updated
Was this helpful?
