Envelope Send
Sends an envelope that has already been created, delivering it to its recipients. There is no request body — the envelope is identified by envelopeId in the path, and what gets sent is the draft as it currently stands, including any changes made through signatures-envelope-update since the envelope was created.
Only an envelope in Draft status can be sent. Sending validates the persisted draft and moves the envelope out of Draft, so the same envelope cannot be sent a second time — see signatures-envelope-resend to notify a recipient again.
Who is notified, and when, depends on the signing order. When envelope.isSignOrder is false, every recipient is emailed as soon as the envelope is sent. When it is true, only the recipient first in the signing order is emailed at send time, and each subsequent recipient is notified once the recipient before them has signed. Where a position in the order is held by a sign group, every member of that group is notified at the same time.
Once an envelope has been sent, its documents, recipients and fields are fixed — signatures-envelope-update applies only while the envelope is still in Draft. The expiration settings (expireInDays and alertDaysBeforeExpiry) are the only things that can still be changed, through signatures-envelope-edit.
Only the envelope's creator may call this. Unlike the envelope document and attachment download operations, there is no anonymous transaction-token (tid) access here: a valid Authorization bearer token is always required.
This operation is metered across six dimensions, returned in consumption: envelopes-sent is always 1. recipients-sent is the number of recipients on the envelope. recipients-sent-mfa counts the recipients with isMfaEnabled set, signature-fields-sent the signature fields, digital-signature-fields-sent the digitalsignature fields, and attachment-fields-sent the attachment fields.
Those last four are omitted from the list entirely when their count is zero — they are never reported as 0 — and any dimension the subscription plan does not include is omitted too. The list is therefore usually shorter than six entries, and an absent dimension means either none were sent or the plan does not meter it.
JWT token to authenticate the request.
In: header
API key, sent as a request header.
In: header
Path Parameters
GUID of the envelope to send, as returned by signatures-envelope-create in result.data.envelope.id. The envelope must be in Draft status and must have been created by the calling user.
uuidResponse Body
application/json
application/json
application/json
curl -X GET "https://example.com/signatures/envelope/66e0fdcc-3b59-46e8-aef9-f55cb2cad859/send"{ "result": { "statusCode": 200, "message": "OK", "data": { "envelope": { "id": "66e0fdcc-3b59-46e8-aef9-f55cb2cad859", "message": "Envelope successfully sent" } } }, "origin": "GET https://api.doctavian.com/v1/signatures/envelope/{envelopeId}/send", "dateTime": "2026-07-20T12:00:00.000Z", "consumption": [ { "dimension": "envelopes-sent", "value": 1 }, { "dimension": "recipients-sent", "value": 2 }, { "dimension": "signature-fields-sent", "value": 2 } ], "userId": "76106861-30d2-4f54-a40e-be0c678795ca", "operationId": "a1c73f26e80b4d5590e2f8471bc6d039"}{ "error": { "message": "Envelope not found.", "statusCode": 400, "innerErrors": [ { "code": "ENVELOPE_ID_INVALID", "message": "Envelope not found.", "userMessage": "Envelope not found." } ] }, "origin": "GET https://api.doctavian.com/v1/signatures/envelope/{envelopeId}/send", "dateTime": "2026-07-20T12:00:00.000Z", "userId": "230390bd-9a84-467e-ba11-6550ff20e7f6", "operationId": "d3b9afd2f196690fa3d3b4feb5c58198"}{ "error": { "statusCode": 500, "message": "An unexpected error occurred while sending the envelope.", "innerErrors": [ { "code": "FUNCTION_EXECUTION_ERROR", "message": "An unexpected error occurred while sending the envelope.", "userMessage": "Something went wrong. Please try again or contact support." } ] }, "origin": "GET https://api.doctavian.com/v1/signatures/envelope/{envelopeId}/send", "dateTime": "2026-07-20T12:00:00.000Z", "userId": "b08de32e-e596-45ae-ac5e-5c9e263755aa", "operationId": "123e21e74ff2a16e18f56f7f44fc75f0"}