Skip to content
For LLMsView as Markdown·

DocuSign eSignature

Create, send, and manage envelopes and signing ceremonies via DocuSign.

DetailValue
CategoryLegal
Base URLhttps://na4.docusign.net/restapi/v2.1
AuthenticationOAuth2
Endpoints5
Connector keydocusign-esign

Using DocuSign eSignature in a workflow

  1. Go to Connections and click New Connection.
  2. Pick DocuSign eSignature from the marketplace.
  3. Enter your credentials (see Authentication above for what's expected).
  4. In a workflow, drop an API Call node and select this connection.
  5. Pick the operation you need from the Operation dropdown — the full list is below.

Available endpoints

EndpointSummary
GET /accounts/{accountId}/envelopesList envelopes
POST /accounts/{accountId}/envelopesCreate and send an envelope
GET /accounts/{accountId}/envelopes/{envelopeId}Get envelope details
GET /accounts/{accountId}/envelopes/{envelopeId}/documentsList envelope documents
GET /accounts/{accountId}/templatesList templates

Each endpoint is documented in full below. Use the outline on the right to jump to one.

GET /accounts/{accountId}/envelopes

List envelopes

DetailValue
Operation IDlegal.listEnvelopes
MethodGET
Path/accounts/{accountId}/envelopes

Parameters

NameLocationTypeRequired
accountIdpathstringYes

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your DocuSign eSignature connection from the Connection dropdown.
  3. In the Operation dropdown, select legal.listEnvelopes.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream DocuSign eSignature API reference.

POST /accounts/{accountId}/envelopes

Create and send an envelope

DetailValue
Operation IDlegal.createEnvelope
MethodPOST
Path/accounts/{accountId}/envelopes

Parameters

NameLocationTypeRequired
accountIdpathstringYes

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your DocuSign eSignature connection from the Connection dropdown.
  3. In the Operation dropdown, select legal.createEnvelope.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream DocuSign eSignature API reference.

GET /accounts/{accountId}/envelopes/{envelopeId}

Get envelope details

DetailValue
Operation IDlegal.getEnvelope
MethodGET
Path/accounts/{accountId}/envelopes/{envelopeId}

Parameters

NameLocationTypeRequired
accountIdpathstringYes
envelopeIdpathstringYes

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your DocuSign eSignature connection from the Connection dropdown.
  3. In the Operation dropdown, select legal.getEnvelope.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream DocuSign eSignature API reference.

GET /accounts/{accountId}/envelopes/{envelopeId}/documents

List envelope documents

DetailValue
Operation IDlegal.listDocuments
MethodGET
Path/accounts/{accountId}/envelopes/{envelopeId}/documents

Parameters

NameLocationTypeRequired
accountIdpathstringYes
envelopeIdpathstringYes

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your DocuSign eSignature connection from the Connection dropdown.
  3. In the Operation dropdown, select legal.listDocuments.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream DocuSign eSignature API reference.

GET /accounts/{accountId}/templates

List templates

DetailValue
Operation IDlegal.listTemplates
MethodGET
Path/accounts/{accountId}/templates

Parameters

NameLocationTypeRequired
accountIdpathstringYes

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your DocuSign eSignature connection from the Connection dropdown.
  3. In the Operation dropdown, select legal.listTemplates.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream DocuSign eSignature API reference.