Skip to main content

DocuSign eSignature

DocuSign eSignature is the world's leading electronic signature platform for sending, signing, tracking, and managing agreements digitally, with legally admissible signatures accepted in 180+ countries. It spans the full agreement lifecycle — sending documents, tracking envelope status, and managing recipients, templates, and workspaces. Its REST API offers 400+ endpoints for agreement automation.

DocuSign eSignature icon

Power end-to-end data operations for your DocuSign eSignature API with Nexla. Our bi-directional DocuSign eSignature connector is purpose-built for DocuSign eSignature, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to DocuSign eSignature or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your DocuSign eSignature workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

  • Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
  • Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
  • API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
  • Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites​

To connect Nexla to DocuSign eSignature, you need an active DocuSign account with API access and the appropriate credentials for your chosen authentication method. DocuSign supports three authentication approaches: API Key (Bearer Token), OAuth2 Authorization Code Grant, and JWT Grant for server-to-server integrations.

DocuSign Account​

Before obtaining credentials, ensure you have access to a DocuSign account:

  • For development and testing, sign up for a free DocuSign Developer account at developers.docusign.com. The developer sandbox environment (account-d.docusign.com) provides a safe environment to build and test integrations without affecting production data.

  • For production use, log in to your DocuSign production account at account.docusign.com. You will need Admin access to create integration keys and manage API credentials.

Create an Integration Key (Required for OAuth2 and JWT)​

An Integration Key (also called a Client ID) is a unique identifier that represents your application in DocuSign. It is required for both the OAuth2 Authorization Code Grant and JWT Grant authentication methods.

  1. Log in to your DocuSign account and navigate to Settings in the top navigation bar.

  2. Under the Integrations section in the left-hand sidebar, click Apps and Keys.

  3. Click the ADD APP & INTEGRATION KEY button.

  4. Enter a descriptive name for your application (e.g., "Nexla Integration") and click ADD. DocuSign automatically generates a 32-character Integration Key (GUID) for your application.

  5. Copy and securely store the Integration Key — this value is your Client ID, required for both OAuth2 and JWT authentication.

Obtain a Secret Key (Required for OAuth2 Only)​

If using the OAuth2 Authorization Code Grant method, you also need a Client Secret associated with your Integration Key:

  1. On the Apps and Keys page, click ACTIONS next to your Integration Key and select Edit.

  2. Under the Authentication section, click ADD SECRET KEY.

  3. Copy the generated secret key immediately and store it securely. DocuSign displays this key only once — it cannot be retrieved later from the DocuSign interface.

Important

Store your Client Secret in a secure location immediately after generation. If you lose the secret key, you will need to generate a new one, which will invalidate the previous secret.

Generate an RSA Key Pair (Required for JWT Only)​

If using the JWT Grant authentication method for automated server-to-server integrations:

  1. On the Apps and Keys page, click ACTIONS next to your Integration Key and select Edit.

  2. Under the Authentication section, click ADD RSA KEYPAIR. DocuSign generates a public/private RSA key pair.

  3. Download or copy the private key (in PEM format, beginning with -----BEGIN RSA PRIVATE KEY-----) and store it in a secure location. The private key is shown only once and cannot be retrieved from DocuSign after closing this dialog.

  4. The corresponding public key is automatically saved and associated with your integration in DocuSign.

Find Your User ID (Required for JWT Only)​

The User ID is the GUID of the DocuSign user that the JWT integration will act on behalf of:

  1. On the Apps and Keys page, your API Username (User ID) is displayed in the My Account Information section at the top of the page.

  2. Copy this value — it is a 32-character GUID (for example, 12345678-abcd-1234-abcd-123456789012).

Before a JWT integration can access the DocuSign API on behalf of a user, that user must explicitly grant consent to the integration. This is a one-time step per user per integration.

  1. Construct a consent URL using the format below, replacing {integration_key} with your Integration Key value and {redirect_uri} with a valid redirect URI registered for your integration:

    https://account-d.docusign.com/oauth/auth?response_type=code&scope=signature%20impersonation&client_id={integration_key}&redirect_uri={redirect_uri}

    For production accounts, replace account-d.docusign.com with account.docusign.com.

  2. Open the URL in a browser, log in with the DocuSign user account that will be impersonated, and click Accept to grant consent.

Consent must be granted once per user per integration. After consent is granted, the JWT flow can obtain access tokens programmatically without further user interaction, making it ideal for automated batch processing and server-to-server workflows.

Determine Your DocuSign Environment​

DocuSign operates separate environments for development/testing and production. When configuring your credential in Nexla, you will need to specify the correct base URL for your environment:

  • Demo (Sandbox): account-d.docusign.com — for development and testing (OAuth2 and JWT)
  • Production (US): account.docusign.com — for live US production use (OAuth2 and JWT)
  • Production (EU): account.docusign.eu — for EU-region production accounts (OAuth2 and JWT)

For the API Key (Bearer Token) method, the environment field expects the API host URL (e.g., demo.docusign.net or na2.docusign.net). Your account's API host URL is listed under Settings > Apps and Keys > Account Base URI in your DocuSign account.

Authenticate​

Credentials required​

DocuSign API Key authentication using Bearer token. Obtain an access token via the OAuth2 authorization flow or JWT assertion grant, then pass it in the Authorization header.

FieldRequiredSecretDescription
API Key ValueYesYesAn encoded string value used as a secret token to authenticate API requests
DocuSign EnvironmentYesNoDocuSign API base URL for your account environment (e.g., demo.docusign.net, na2.docusign.net, eu.docusign.net)

Create a credential in Nexla​

  1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

  2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

  3. DocuSign eSignature supports three authentication methods in Nexla. Select the method that best fits your integration scenario, and complete the corresponding fields.

DocuSign eSignature Authentication Methods

Authenticate using a pre-obtained OAuth2 access token passed as a Bearer token in the Authorization header. This method is useful when you already have a valid access token obtained through DocuSign's OAuth2 or JWT flow outside of Nexla. Note that DocuSign access tokens expire after 8 hours, so periodic token rotation is required.

  1. Enter your DocuSign OAuth2 access token in the **API Key Value** field. This Bearer token is obtained from DocuSign's OAuth2 authorization flow or JWT assertion grant and is passed in the `Authorization: Bearer {token}` request header for all API calls.
  2. Enter the API host URL for your DocuSign account environment in the **DocuSign Environment** field. This is the hostname used in API requests—for example, `demo.docusign.net` for sandbox, or your account's assigned production host (such as `na2.docusign.net` or `eu.docusign.net`). Your account's base URI is displayed under **Settings > Apps and Keys > Account Base URI** in your DocuSign account.
  1. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation and can be selected for use with a new data source or destination.

Use as a data source​

The DocuSign eSignature connector enables you to ingest envelope data, recipient information, billing records, templates, and workspace files directly from your DocuSign account into Nexla data flows. To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the DocuSign eSignature connector tile, then select the credential that will be used to connect to the DocuSign eSignature instance, and click Next; or, create a new DocuSign eSignature credential for use in this flow.

Endpoint templates​

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common DocuSign eSignature endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below. Click on an endpoint to see more information about it and how to configure your data source for this endpoint.

Get User Info

Retrieves profile information for the user associated with the current OAuth token, including name, email, and linked account details. Use this endpoint to verify the authenticated user's identity and obtain their associated account IDs before making account-level API calls.

  • This endpoint requires no additional parameters. Selecting the template is sufficient — Nexla will call the DocuSign /oauth/userinfo endpoint automatically using the authenticated credential.
  • The response includes the user's name, email address, and a list of DocuSign accounts the user has access to, along with each account's ID and base URI.

The account IDs returned by this endpoint are needed for most other DocuSign API calls. Use this endpoint first if you need to discover which DocuSign accounts are accessible with your current credentials.

Get Account Information

Retrieves detailed information for a specified DocuSign account, optionally including account settings. Use this endpoint to inspect account configuration, features enabled, and metadata about your DocuSign organization.

  • Enter the required parameters for this endpoint:

    • Account ID: The GUID of the DocuSign account to retrieve. This can be obtained from the Get User Info endpoint or from your DocuSign account settings under Settings > Account Profile > API Account ID.
    • Include Account Settings: Set to true to include the full list of account-level settings in the response, or false to retrieve only basic account information.

Get Billing Invoice

Retrieves a specific billing invoice for a DocuSign account by invoice ID. Use this endpoint to pull individual invoice details for financial reconciliation, audit trails, or accounts payable workflows.

  • Enter the required parameters for this endpoint:

    • Account ID: The GUID of the DocuSign account associated with the invoice.
    • Invoice ID: The unique identifier of the invoice to retrieve. Invoice IDs can be found in the DocuSign billing console under Settings > Billing > Invoices.

Access to billing endpoints typically requires Admin-level permissions in DocuSign. Ensure your credential's user account has the appropriate role.

List Past Due Invoices

Retrieves a list of all past due invoices for a specified DocuSign account. Use this endpoint to identify outstanding billing obligations and build automated payment reminders or finance dashboards.

  • Enter the Account ID — the GUID of the DocuSign account for which past due invoices should be retrieved.
  • The response returns an array of invoice objects, each containing invoice ID, amount due, due date, and status. Nexla will create one record per invoice in the resulting Nexset.

Get Billing Payment

Retrieves billing payment information for a specific payment record. Use this endpoint to verify payment status and pull payment details for financial reconciliation.

  • Enter the required parameters for this endpoint:

    • Account ID: The GUID of the DocuSign account associated with the payment.
    • Payment ID: The unique identifier of the payment to retrieve.

Get Account Billing Plan

Retrieves billing plan information for a specified DocuSign account, optionally including credit card details and successor plan information. Use this endpoint to monitor subscription status, plan limits, or upcoming plan changes.

  • Enter the Account ID — the GUID of the DocuSign account whose billing plan you want to retrieve.
  • Set Include Credit Card Information to true to include payment method details in the response.
  • Set Include Metadata to true to include additional plan metadata.
  • Set Include Successor Plans to true to include information about any upcoming plan changes or renewals.

Get Downgrade Plan Information

Retrieves information about any pending billing plan downgrade for a specified account. Use this endpoint to monitor queued plan changes before they take effect.

  • Enter the Account ID — the GUID of the DocuSign account for which downgrade plan information should be retrieved.
  • The response includes details about the pending downgrade, including the target plan and effective date, if a downgrade has been queued.

Get billing plan details

Retrieves detailed information about a specific DocuSign billing plan by its plan ID. Use this endpoint to compare available billing plans, review plan features, or support upgrade/downgrade decision workflows.

  • Enter the Billing Plan ID — the unique identifier of the billing plan to retrieve. Billing plan IDs can be found in the DocuSign billing plan documentation or by reviewing the plan details in your DocuSign account under Settings > Billing > Change Plan.

List bulk send batch statuses

Returns a paginated list of bulk send batch statuses for a DocuSign account. Use this endpoint to monitor the progress and results of bulk envelope sending operations, which allow you to send the same document to a large number of recipients simultaneously.

  • Enter the Account ID — the GUID of the DocuSign account for which bulk send batch statuses should be listed.
  • Optionally, enter comma-separated Batch IDs to filter results to specific bulk send batches.
  • Optionally, enter a Status value to filter batches by their current status (e.g., queued, processing, completed, failed).
  • This endpoint uses pagination. Nexla will automatically retrieve additional pages to ensure all matching batch records are included in the resulting Nexset.

Bulk send batches are created when you send envelopes to multiple recipients at once using the DocuSign Bulk Send feature. Each batch can contain up to 1,000 recipients.

List envelope status changes

Gets status changes for one or more envelopes with optional filtering by date range, status, folder, user, and other criteria. This is one of the most commonly used DocuSign endpoints and is ideal for building envelope tracking dashboards, audit reports, or event-driven workflows.

  • Enter the Account ID — the GUID of the DocuSign account from which envelopes should be retrieved.

  • Use the available filter parameters to narrow results as needed:

    • From Date: Retrieve only envelopes with status changes on or after this date (format: YYYY-MM-DD). This parameter is required unless envelope_ids or transaction_ids is specified.
    • To Date: Retrieve only envelopes with status changes on or before this date (format: YYYY-MM-DD).
    • Status: Filter by envelope status, such as sent, delivered, completed, declined, or voided.
    • Envelope IDs: Comma-separated list of specific envelope GUIDs to retrieve.
    • From To Status: Filter envelopes by a specific status transition (e.g., changed).
    • User ID: Filter envelopes by the GUID of the sender.
    • Folder IDs: Comma-separated folder IDs to limit results to envelopes in specific folders.
    • Include: Comma-separated list of additional data to include in the response, such as recipients, documents, tabs, or custom_fields.
  • This endpoint supports pagination. Nexla will automatically page through results to retrieve all matching envelopes.

The from_date parameter is required unless you specify envelope_ids or transaction_ids. For ongoing incremental ingestion, use Nexla date/time macros (such as {"{now-1}"} for the previous day) in the from_date parameter when configuring manually, or schedule this source to run periodically to capture new status changes.

Get envelope status

Retrieves the status and full details of a specific envelope by its envelope ID. Use this endpoint when you need to inspect a single envelope's current state, recipients, documents, and signing history.

  • Enter the required parameters for this endpoint:

    • Account ID: The GUID of the DocuSign account that owns the envelope.
    • Envelope ID: The unique GUID of the envelope to retrieve. Envelope IDs can be found in the DocuSign web application or by first using the List Envelope Status Changes endpoint.
  • Optionally, set Advanced Update to true to enable advanced envelope update options in the response.
  • Optionally, enter a comma-separated Include list to add extra information to the response, such as recipients, documents, custom_fields, tabs, or extensions.

Get envelope recipients

Retrieves the status and information for all recipients in a specific envelope. Use this endpoint to track who has signed, who is pending, and any recipient-level activity on an envelope.

  • Enter the required parameters for this endpoint:

    • Account ID: The GUID of the DocuSign account that owns the envelope.
    • Envelope ID: The GUID of the envelope whose recipients you want to retrieve.
  • Set Include Extended to true to include extended recipient details in the response.
  • Set Include Tabs to true to include the recipient's tab (field) data in the response.
  • Set Include Metadata to true to include recipient metadata such as custom data fields.
  • The response returns an array of recipient objects organized by recipient type (signers, carbon copies, certified delivery, etc.). Nexla will create one record per recipient in the resulting Nexset.

Get recipient tabs

Retrieves tab (form field) information for a specific signer or sign-in-person recipient within an envelope. Tabs represent the signature fields, text fields, checkboxes, and other interactive elements placed on documents for recipients to complete. Use this endpoint to extract form data filled in by signers.

  • Enter the required parameters for this endpoint:

    • Account ID: The GUID of the DocuSign account that owns the envelope.
    • Envelope ID: The GUID of the envelope containing the recipient.
    • Recipient ID: The ID of the specific recipient whose tabs you want to retrieve. Recipient IDs can be obtained from the Get Envelope Recipients endpoint.
  • Set Include Anchor Tab Locations to true to include the position data for anchor-placed tabs.
  • Set Include Metadata to true to include additional tab metadata in the response.

Tab data contains the values entered or selected by signers in form fields. This endpoint is particularly useful for extracting structured data from completed agreements for downstream processing or storage.

Get Envelope Status (Examples)

Retrieves the status and details of a specific envelope using the API version-parameterized URL format. This template is functionally equivalent to the Get Envelope Status endpoint and is provided as a reference implementation example with explicit API version configuration.

  • Enter the required parameters for this endpoint:

    • API Version: The DocuSign eSignature REST API version to use (e.g., v2.1).
    • Account ID: The GUID of the DocuSign account that owns the envelope.
    • Envelope ID: The GUID of the envelope whose status you want to retrieve.

Get Template

Retrieves a specific envelope template by its template ID for the specified DocuSign account. Templates are reusable envelope definitions that define the documents, recipients, and form fields for a standard signing workflow. Use this endpoint to inspect template configuration or audit template contents.

  • Enter the required parameters for this endpoint:

    • Account ID: The GUID of the DocuSign account that owns the template.
    • Template ID: The GUID of the template to retrieve. Template IDs can be found in the DocuSign web application under Templates, or by listing templates via the DocuSign API.
  • Optionally, enter a comma-separated Include list to add extra information to the response, such as recipients, tabs, documents, or custom_fields.

Get Workspace

Retrieves information about a specific DocuSign workspace. Workspaces are collaborative environments within DocuSign where teams can share, manage, and work with documents. Use this endpoint to retrieve workspace metadata and configuration.

  • Enter the required parameters for this endpoint:

    • Account ID: The GUID of the DocuSign account that owns the workspace.
    • Workspace ID: The unique ID of the workspace to retrieve.

Get Workspace File

Retrieves a specific file from a DocuSign workspace folder. Use this endpoint to access documents stored in workspace folders for download or further processing.

  • Enter the required parameters for this endpoint:

    • Account ID: The GUID of the DocuSign account that owns the workspace.
    • Workspace ID: The unique ID of the workspace containing the file.
    • Folder ID: The ID of the folder within the workspace where the file is located.
    • File ID: The unique ID of the file to retrieve.
  • Set Is Download to true to retrieve the file content as a download rather than metadata only.
  • Set PDF Version to true to retrieve the file as a PDF, even if it was originally uploaded in another format.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration​

DocuSign eSignature data sources can also be manually configured to ingest data from any valid DocuSign eSignature API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.

DocuSign API URLs follow the pattern https://{your-host}/v2.1/accounts/{accountId}/{resource}, where {your-host} is your account's base URI (e.g., na2.docusign.net or demo.docusign.net) and {accountId} is your DocuSign account GUID. Your account's base URI is displayed under Settings > Apps and Keys > Account Base URI.

Most DocuSign list endpoints return arrays nested under a named key rather than at the response root (e.g., envelopes, recipients, invoices, bulkBatches) — for example, the List Envelope Status Changes endpoint returns envelopes under $.envelopes[*]. Set the path to data accordingly so Nexla treats each item as a separate record.

Date/time macros are particularly useful with the List Envelope Status Changes endpoint, which accepts from_date and to_date query parameters — for example, appending ?from_date={"{now-1}"} to the envelopes URL retrieves only envelopes with status changes since the previous run period.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new DocuSign eSignature data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.

Use as a destination​

Click the + icon on the Nexset that will be sent to the DocuSign eSignature destination, and select the Send to Destination option from the menu. Select the DocuSign eSignature connector from the list of available destination connectors, then select the credential that will be used to connect to the DocuSign eSignature organization, and click Next; or, create a new DocuSign eSignature credential for use in this flow.

Endpoint templates​

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common DocuSign eSignature endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

Create Billing Payment

Posts a payment to a past due invoice for a DocuSign account. Use this endpoint to programmatically submit payments for outstanding invoices, enabling automated accounts payable workflows.

  • Enter the Account ID — the GUID of the DocuSign account for which the billing payment will be posted. This value is appended to the API URL path and identifies the account to which the payment is applied.

  • Prepare your Nexset data to include the payment fields required by the DocuSign Billing Payments API. The request body should include:

  • Data is sent as JSON in the request body. Nexla will automatically serialize each Nexset record as a JSON object for each API call.

Access to billing endpoints typically requires Admin-level permissions in DocuSign. Ensure your credential's user account has the appropriate role before configuring this destination.

Queue Downgrade Billing Plan

Queues a billing plan downgrade request for a DocuSign account. Use this endpoint to programmatically schedule a plan change to a lower-tier DocuSign subscription that will take effect at the end of the current billing period.

  • Enter the Account ID — the GUID of the DocuSign account for which the billing plan downgrade will be queued.

  • Prepare your Nexset data to include the downgrade plan fields required by the DocuSign API. The request body should include:

    • planId: The ID of the billing plan to downgrade to. Available plan IDs can be retrieved using the Get Billing Plan Details source endpoint.
    • Refer to the DocuSign Downgrade Plan API reference for the full list of supported request body fields.

Plan downgrades are queued and take effect at the end of the current billing period — they are not immediate. Use the Get Downgrade Plan Information source endpoint to verify the queued downgrade before it takes effect.

Purchase Additional Envelopes

Reserves and purchases additional envelopes for a DocuSign account. Use this endpoint to programmatically increase the envelope allotment for an account when the current plan's envelope quota is running low.

  • Enter the Account ID — the GUID of the DocuSign account for which additional envelopes will be purchased.

  • Prepare your Nexset data to include the envelope purchase fields required by the DocuSign API. The request body should include:

Create an envelope

Creates a new DocuSign envelope and sends it to recipients for signature. An envelope is the container for documents to be signed and the recipients who will sign them. Use this endpoint to programmatically initiate document signing workflows from your Nexla data flows.

  • Enter the Account ID — the GUID of the DocuSign account in which the envelope will be created.

  • Prepare your Nexset data to include the envelope creation fields required by the DocuSign Envelopes API. Key request body fields include:

    • status: Set to sent to immediately send the envelope for signature, or created to save it as a draft for later sending.
    • documents: An array of document objects containing the files to be signed (as base64-encoded content or template references).
    • recipients: An object defining the signers, carbon copy recipients, and other recipient types, including their names, email addresses, and routing order.
    • emailSubject: The subject line of the email notification sent to recipients.
    • Refer to the DocuSign Create Envelope API reference for the full list of supported request body fields.
  • Optional query parameters can be specified in the endpoint URL to control behavior, such as cdse_mode, merge_roles_on_draft, and tab_label_exact_matches.

DocuSign envelopes consume envelope quota from your DocuSign account plan. Ensure your account has sufficient envelope quota before creating envelopes in bulk.

Update envelope status

Sends, voids, moves, purges, or modifies an existing DocuSign envelope. Use this endpoint to programmatically change the status or properties of an envelope that has already been created — for example, voiding an envelope that was sent in error or resending a reminder to recipients.

  • Enter the Account ID — the GUID of the DocuSign account that owns the envelope.
  • Enter the Envelope ID — the GUID of the envelope to update. Envelope IDs can be retrieved using the List Envelope Status Changes or Get Envelope Status source endpoints.

  • Prepare your Nexset data to include the update fields required by the DocuSign Envelopes API. Common update operations include:

    • Set status to voided and include a voidedReason to void the envelope.
    • Set the optional resend_envelope query parameter to true to resend notification emails to pending recipients.
    • Refer to the DocuSign Update Envelope API reference for the full list of supported fields and operations.

Voiding an envelope is permanent and cannot be undone. Recipients will receive a notification that the envelope has been voided.

Update recipient tabs

Updates the tabs (form fields) for a specific recipient in a DocuSign envelope. Tabs are the interactive elements—such as signature fields, text boxes, checkboxes, and date fields—placed on documents for recipients to complete. Use this endpoint to programmatically pre-populate or modify form field values before recipients sign.

  • Enter the Account ID — the GUID of the DocuSign account that owns the envelope.
  • Enter the Envelope ID — the GUID of the envelope containing the recipient whose tabs will be updated.
  • Enter the Recipient ID — the ID of the specific recipient whose tabs you want to update. Recipient IDs can be obtained from the Get Envelope Recipients source endpoint.

  • Prepare your Nexset data to include the tab update fields required by the DocuSign API. Key request body fields include:

    • textTabs: An array of text field tab objects with updated values.
    • checkboxTabs: An array of checkbox tab objects with updated checked/unchecked state.
    • Refer to the DocuSign Update Recipient Tabs API reference for the full list of supported tab types and fields.

Get recipient view URL

Returns a URL that opens the DocuSign embedded signing interface for a specific recipient. Use this endpoint to embed the signing experience directly into your application, allowing recipients to sign documents within your own web UI without leaving to DocuSign's hosted interface.

  • Enter the Account ID — the GUID of the DocuSign account that owns the envelope.
  • Enter the Envelope ID — the GUID of the envelope for which the recipient view URL will be generated.

  • Prepare your Nexset data to include the recipient view request fields required by the DocuSign API. Key request body fields include:

    • returnUrl: The URL the signer is redirected to after completing or declining to sign. This should be a page within your application.
    • recipientId: The ID of the recipient for whom the signing URL is being generated.
    • email and userName: The recipient's email address and name, used to authenticate the signing session.
    • Refer to the DocuSign Recipient View API reference for the full list of supported request body fields.
  • The API returns a url field in the response containing the time-limited signing URL. This URL is valid for a short period (typically 5 minutes) and should be presented to the recipient promptly.

Embedded signing URLs are single-use and expire quickly. Generate the URL only immediately before presenting it to the recipient. For production embedded signing implementations, review the DocuSign embedded signing guide for best practices.

Create Envelope from Template

Creates a new DocuSign template or creates an envelope using an existing template. DocuSign templates define reusable document structures with predefined recipients and form fields, making it faster to send standard agreement types. Use this endpoint to programmatically send envelopes based on standardized templates.

  • Enter the Account ID — the GUID of the DocuSign account in which the envelope or template will be created.

  • Prepare your Nexset data to include the template-based envelope fields required by the DocuSign Templates API. Key request body fields include:

    • templateId: The GUID of the DocuSign template to use. Template IDs can be found in the DocuSign web application under Templates.
    • templateRoles: An array of objects mapping your recipients to the template's predefined roles, including each recipient's name, email, and role name.
    • status: Set to sent to immediately send for signature, or created to save as a draft.
    • Refer to the DocuSign Templates API reference for the full list of supported request body fields.

Using templates is the most efficient way to send standardized agreements at scale. Templates pre-define documents, signing fields, and recipient roles — reducing the amount of data needed in each API request compared to creating envelopes from scratch.

Create Envelope (Examples)

Creates an envelope with a document and recipients using the API version-parameterized URL format. This template is functionally equivalent to the Create an Envelope endpoint and is provided as a reference implementation example with explicit API version configuration.

  • Enter the API Version — the DocuSign eSignature REST API version to use in the URL (e.g., v2.1).
  • Enter the Account ID — the GUID of the DocuSign account in which the envelope will be created.
  • Prepare your Nexset data with the same envelope creation fields described in the Create an Envelope template above.

Create Envelope in Draft Stage

Creates a DocuSign envelope in draft (created) status with documents and recipients. Draft envelopes are saved but not yet sent to recipients. Use this endpoint when you want to create envelopes for review or modification before sending, or when a human step is required before dispatching agreements.

  • Enter the API Version — the DocuSign eSignature REST API version to use in the URL (e.g., v2.1).
  • Enter the Account ID — the GUID of the DocuSign account in which the draft envelope will be created.

  • Prepare your Nexset data to include the envelope fields required by the DocuSign Envelopes API. Set the status field to created to save the envelope as a draft. Key fields include:

    • documents: An array of document objects to include in the envelope.
    • recipients: An object defining the recipient information and signing order.
    • emailSubject: The subject line of the email notification that will be sent when the envelope is later sent.
    • Refer to the DocuSign Create Envelope API reference for the full list of supported fields.

Draft envelopes do not consume DocuSign envelope quota until they are sent. To send a draft envelope, use the Update Envelope Status endpoint with status: sent.

Send Envelope with Template

Creates and immediately sends an envelope using a DocuSign template. This endpoint is optimized for high-volume template-based sending workflows. Use this endpoint when you want to send standardized agreements to recipients as part of an automated data flow.

  • Enter the API Version — the DocuSign eSignature REST API version to use in the URL (e.g., v2.1).
  • Enter the Account ID — the GUID of the DocuSign account from which the envelope will be sent.

  • Prepare your Nexset data to include the template-based envelope sending fields. Key fields include:

    • templateId: The GUID of the DocuSign template to use.
    • templateRoles: An array of recipient role assignments, each including the recipient's name, email, and role name as defined in the template.
    • status: Set to sent to immediately dispatch the envelope to recipients.
    • Refer to the DocuSign Envelopes API reference for the full list of supported fields.

Send Envelope Using Composite Templates

Creates and sends an envelope using composite templates — a DocuSign feature that allows combining multiple templates and inline documents in a single envelope. Composite templates give you the flexibility to apply different templates to different documents within the same envelope, or to overlay inline document content on top of template-based documents.

  • Enter the API Version — the DocuSign eSignature REST API version to use in the URL (e.g., v2.1).
  • Enter the Account ID — the GUID of the DocuSign account from which the envelope will be sent.

  • Prepare your Nexset data to include the composite template envelope fields. Key fields include:

    • compositeTemplates: An array of composite template objects, each defining a combination of server templates, inline templates, and document content to include in the envelope.
    • status: Set to sent to immediately dispatch the envelope.
    • Refer to the DocuSign Envelopes API reference and the composite templates guide for full details on the composite template structure.

Composite templates are an advanced DocuSign feature suited for complex signing scenarios. Review the DocuSign composite templates documentation before configuring this endpoint to understand the structure and available options.

Create Workspace

Creates a new workspace for a DocuSign account. Workspaces are collaborative environments within DocuSign where teams can share, manage, and collaborate on documents. Use this endpoint to programmatically provision new workspaces as part of onboarding or organizational workflows.

  • Enter the Account ID — the GUID of the DocuSign account in which the workspace will be created.

  • Prepare your Nexset data to include the workspace creation fields required by the DocuSign Workspaces API. Key fields include:

Manual configuration​

DocuSign eSignature destinations can also be manually configured to send data to any valid DocuSign eSignature API endpoint. Using manual configuration, you can also configure Nexla to automatically send the response received from the DocuSign eSignature API after each call to a new Nexla webhook data source. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.

DocuSign's REST API accepts JSON for all write operations — select JSON as the Content Format. DocuSign API URLs follow the pattern https://{your-host}/v2.1/accounts/{accountId}/{resource}, where {your-host} is your account's base URI (e.g., na2.docusign.net or demo.docusign.net). For update operations, include the ID of the object to be updated at the end of the URL.

Most DocuSign API write endpoints accept a single object per call rather than arrays of records — verify that your target endpoint supports batched requests before enabling record batching. Enabling the response webhook option is particularly useful for the Create an Envelope and Create Envelope from Template endpoints, to capture the new envelope ID returned in the response.

Save & activate​

Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured DocuSign eSignature endpoint, open the destination resource menu, and select Activate.

The Nexset data will not be sent to DocuSign eSignature until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.