Skip to main content

Endpoint

Authentication

This endpoint requires an OAuth access token. Send it as a bearer token:
Required scope: tasks:write
The envelope is created as the access token’s user, and any replacement signing document is uploaded as them.

Path Parameters

Request Body

The request body must be a JSON object with the following fields:

Required Fields

Optional Fields

Recipient Object Fields

File Object Fields

Conditional rules enforced by the API:
  • recipients may only be provided when custom_recipients is true, and each recipient must include both email and name.
  • signing_document is required when replace_signing_document is true, and may only be provided when replace_signing_document is true.
Violating these returns a 422 Validation Error.

Request Example

Response

Success Response

Status Code: 200 OK

Response Fields

Envelope URL Object Fields

Error Responses

400 Bad Request

Returned when the access token has no user behind it. client_credentials tokens act as the admin who created the application, so this applies only to tokens issued before application creators were recorded.

401 Unauthorized

Returned when the access token is missing, unknown, revoked, or expired, or when an X-API-Key was sent instead of a bearer token. See OAuth error responses.

403 Forbidden

Returned when the token lacks the required scope:
Or when the user may not act on this task:

404 Not Found

Returned when the task does not exist.

409 Conflict

Returned when the task is not at a signature step or signature has already been initiated.

422 Validation Error

Returned when the request body is invalid (for example, recipients provided without custom_recipients=true, or signing_document missing when replace_signing_document=true).

429 Too Many Requests

Returned when your organization exceeds its per-minute request limit.

500 Internal Server Error

Returned when signature initiation fails due to a server error.

Notes

Call Get Signature Details first to read the step status and existing recipients, and to obtain the step_run_id.
By default (custom_recipients=false), the envelope uses the recipients already configured on the signature step. Set custom_recipients=true and supply recipients to upsert recipients before sending. Set create_envelope_url=true to receive a coordinator URL for editing or viewing the envelope.
Set replace_signing_document=true and include signing_document only when you need to swap the document before sending. Otherwise the document already on the step is used.

Use Cases

This endpoint is useful for:
  • Contract execution - Create and send a signature envelope after review and approval
  • Custom signing workflows - Upsert recipients or replace the signing document at send time
  • Coordinator handoff - Return an envelope URL so a coordinator can edit or view the envelope
  • Multi-party agreements - Configure signers and viewers for a structured signing process