DocuSeal is an open-source document signing platform for creating, sending, filling, and signing documents online. It supports the full e-signature workflow — reusable templates, multi-party signature requests, and legally binding eSignatures (ESIGN, UETA, eIDAS) — across cloud-hosted or self-hosted deployments. Its REST API automates document workflows and manages submissions and templates.
Power end-to-end data operations for your Docuseal API with Nexla. Our bi-directional Docuseal connector is purpose-built for Docuseal, 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 Docuseal or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Docuseal 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
To connect Nexla to DocuSeal, you need an active DocuSeal account and an API key. DocuSeal supports cloud-hosted deployments in the Global region (https://api.docuseal.com) and the EU region (https://api.docuseal.eu), as well as self-hosted on-premises installations at a custom URL.
The DocuSeal API is available as part of the Pro Plan. A Pro seat (starting at $20/month) is required to enable API access. For self-hosted (on-premises) installations, API access is available according to your license.
Select the API or API Keys section within Settings.
Click Generate API Key (or Create API Key) to create a new key.
Copy the generated API key and store it securely. The key will be used as the API Key Value when creating your Nexla credential.
For Self-Hosted (On-Premises) Installations:
Sign in to your self-hosted DocuSeal instance (e.g., https://yourdocuseal.example.com).
Navigate to Settings > API (accessible at https://yourdocuseal.example.com/settings/api).
Generate or copy your API key from this page.
Important
DocuSeal API keys provide full access to your account's document submissions, templates, and submitter data. Store your API key securely and avoid sharing it in publicly accessible locations.
Docuseal API base URL. Defaults to the hosted instance at https://api.docuseal.com. Override for self-hosted deployments (e.g. https://yourdocuseal.example.com/api). Allowed values: DocuSeal Cloud (Global); DocuSeal Cloud (EU)
API Key Value
Yes
Yes
An encoded string value used as a secret token to authenticate API requests
After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
DocuSeal uses API key authentication—all API requests are authenticated by passing your API key in the X-Auth-Token request header, which Nexla handles automatically once the credential is configured. Select or confirm the Base URL for your DocuSeal deployment from the Base URL field. The following pre-configured options are available:
DocuSeal Cloud (Global) — https://api.docuseal.com: Use this option for the standard DocuSeal cloud service available globally.
DocuSeal Cloud (EU) — https://api.docuseal.eu: Use this option if your DocuSeal account is hosted in the EU region for data residency compliance.
For self-hosted deployments, enter your custom instance API URL directly in the Base URL field (e.g., https://yourdocuseal.example.com/api).
The Base URL must match the region or instance where your DocuSeal account is hosted. Using the wrong Base URL will result in authentication failures. For self-hosted installations, ensure the URL points to the API endpoint of your deployed instance, not the web UI.
Enter your DocuSeal API key in the API Key Value field. This is the key you generated in Prerequisites from your DocuSeal account's Settings > API section. The key is sent as the X-Auth-Token header with every request Nexla makes to the DocuSeal API.
The API Key Value field is a secured (password-type) field. The key will be masked after entry to protect its value. Ensure you paste the complete key without any leading or trailing spaces.
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.
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Docuseal connector tile, then select the credential that will be used to connect to the Docuseal instance, and click Next; or, create a new Docuseal credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Docuseal endpoints. Each template is designed specifically for the corresponding DocuSeal API resource, making data source setup easy and efficient. 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.
List Submissions
Returns a paginated list of all document submissions in your DocuSeal account. Use this endpoint to retrieve an up-to-date inventory of all signature requests, including their statuses, submitters, and associated templates. This is the most common endpoint for building submission monitoring dashboards and audit workflows.
This endpoint automatically paginates through all available submissions using DocuSeal's cursor-based pagination. Nexla fetches up to 100 submissions per page and continues retrieving additional pages until all records have been ingested.
No additional configuration is required beyond selecting this endpoint template. The endpoint fetches all submissions accessible to the authenticated account.
Each submission record includes the submission ID, status (pending, completed, expired, etc.), creation and completion timestamps, associated template information, and the list of submitters with their individual completion statuses.
The List Submissions endpoint supports date-based filtering in the DocuSeal API. For incremental or time-bounded ingestion, consider using the manual configuration option to add date filter query parameters to the endpoint URL. Refer to the DocuSeal API Reference for supported query parameters.
Get Submission
Retrieves the full details of a single document submission by its unique ID, including the submission status, all submitter records, field values provided by each submitter, and the audit log URL. Use this endpoint when you need comprehensive details about a specific submission.
Enter the unique identifier of the submission you want to retrieve in the Submission ID field. This is a required field.
Submission IDs are numeric identifiers assigned by DocuSeal when a submission is created. They can be obtained from the List Submissions endpoint, from DocuSeal's web dashboard, or from submission creation API responses.
The response includes the full submission object: status, created and completed timestamps, template ID and name, submitter details (name, email, role, completion status, field values), and a URL to the audit log PDF.
Use this endpoint to build detailed submission tracking or compliance workflows where complete submitter field values and the audit trail are required. The audit log URL in the response provides access to a tamper-evident PDF record of the signing process.
Get Submission Documents
Returns the partially-filled or fully completed signed documents associated with a specific submission. Use this endpoint to retrieve metadata and download URLs for the signed PDF documents produced by a submission.
Enter the unique identifier of the submission whose documents you want to retrieve in the Submission ID field. This is a required field.
Submission IDs can be found using the List Submissions endpoint or from the DocuSeal dashboard. Documents are available for both in-progress (partially filled) and completed submissions.
The response returns an array of document objects under the documents key, with each object including the document name, download URL, and content type.
Completed signed documents are available immediately after all required submitters have signed. For submissions still in progress, partially completed documents reflecting the fields filled so far are returned.
List Templates
Returns a paginated list of all document templates in your DocuSeal account. Templates are reusable document structures that define the fields, roles, and signing order for a document signing workflow. Use this endpoint to audit available templates, sync template metadata to downstream systems, or build template selection interfaces.
This endpoint automatically paginates through all available templates using cursor-based pagination, fetching up to 100 templates per page until all records have been retrieved.
No additional configuration is required. The endpoint retrieves all templates accessible to the authenticated API key.
Each template record includes the template ID, name, folder, creation and update timestamps, the list of defined roles (submitter roles), and the number of submissions created from the template.
Template IDs returned by this endpoint are the values required when creating new submissions via the Create Submission destination endpoint. Use List Templates to look up the correct template ID for a given document type.
Get Template
Retrieves the full details of a single document template by its unique ID, including its defined fields, submitter roles, schema, and metadata. Use this endpoint when you need the complete field structure of a specific template—for example, to understand which fields are available for pre-filling when creating submissions.
Enter the unique identifier of the template you want to retrieve in the Template ID field. This is a required field.
Template IDs are numeric identifiers assigned by DocuSeal. They can be found using the List Templates endpoint or in the DocuSeal web dashboard under the template details.
The response includes the complete template object: name, folder, creation/update timestamps, defined submitter roles, and the full list of fields with their types, names, positions, and validation settings.
List Submitters
Returns a paginated list of all submitters (signers) associated with submissions in your DocuSeal account. Submitters are the individuals who receive, fill, and sign documents. Use this endpoint to retrieve a complete record of all signing parties across all submissions—useful for compliance reporting, contact management, and audit workflows.
This endpoint automatically paginates through all available submitter records using cursor-based pagination, fetching up to 100 records per page until all submitters have been retrieved.
No additional configuration is required. All submitters accessible to the authenticated account are returned.
Each submitter record includes the submitter ID, name, email address, phone number (if provided), role, completion status, the submission it belongs to, and the values provided for each form field.
The List Submitters endpoint can be filtered by submission ID or email address in the DocuSeal API. For filtered ingestion, use the manual configuration option to append query parameters such as submission_id or q (email search) to the endpoint URL.
Get Submitter
Retrieves the full details of a single submitter record by their unique ID, including their provided field values, submitted documents, and completion status. Use this endpoint when you need comprehensive information about a specific signer within a submission.
Enter the unique identifier of the submitter you want to retrieve in the Submitter ID field. This is a required field.
Submitter IDs are numeric identifiers assigned by DocuSeal when a submission is created. They can be found using the List Submitters endpoint or in the Get Submission response, which includes the IDs of all submitters associated with a submission.
The response includes the submitter's ID, name, email, role, completion status, the values they entered for each field, and URLs to the documents they signed.
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.
Docuseal data sources can also be manually configured to ingest data from any valid DocuSeal API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters such as filtering by date range, status, or other criteria supported by the DocuSeal API. 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.
DocuSeal API base URLs: Global Cloud — https://api.docuseal.com; EU Cloud — https://api.docuseal.eu; Self-Hosted — your custom instance API URL (e.g., https://yourdocuseal.example.com/api). Example endpoint URLs: list all submissions at https://api.docuseal.com/submissions, get a single submission at https://api.docuseal.com/submissions/12345, list templates at https://api.docuseal.com/templates, or list submitters with a filter at https://api.docuseal.com/submitters?submission_id=12345. The API supports query parameters such as limit (page size), after (pagination cursor), and q (email search for submitters); refer to the DocuSeal API Reference for the full list of supported parameters per endpoint.
DocuSeal list endpoints (submissions, templates, submitters) return a top-level data array containing the records—set Path to Data in Response to $.data[*] to extract each record, or use $ for single-object endpoints such as Get Submission or Get Template. List responses also include a pagination object with the next-page cursor; specify its location in Path to Metadata in Response if you want to preserve it alongside each record. You do not need to include the X-Auth-Token header in Request Headers—this is handled automatically based on your Docuseal credential configuration.
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 Docuseal 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.
Click the + icon on the Nexset that will be sent to the Docuseal destination, and select the Send to Destination option from the menu. Select the Docuseal connector from the list of available destination connectors, then select the credential that will be used to connect to the Docuseal account, and click Next; or, create a new Docuseal credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Docuseal endpoints. Each template is designed specifically for the corresponding DocuSeal API endpoint, making destination configuration easy and efficient. 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 Submission
Creates a new signature request (submission) for an existing DocuSeal document template and sends it to one or more specified submitters (signers) via email or SMS. Use this endpoint to automate the initiation of document signing workflows from your data pipelines—for example, triggering an NDA or contract signature request when a new customer record is created in your CRM.
The request body must include the template_id of the DocuSeal template to use and a submitters array specifying each signing party. Each submitter object requires at minimum an email address and a role value matching one of the roles defined in the template.
The Nexset data sent to this endpoint should be structured as a JSON payload with the required fields. A minimal example payload looks like this:
template_id: The numeric ID of the DocuSeal template to use (obtainable from the List Templates source endpoint or the DocuSeal dashboard).
submitters: An array of submitter objects, each with email, role, and optionally name, phone, and pre-filled fields values.
Submitters will receive an email invitation with a link to the signing form. Upon completion, all parties receive a copy of the signed document.
Optional fields in the request body include message (custom email subject and body), send_email (set to false to suppress invitation emails), expire_at (submission expiration date), and order (sequential or parallel signing order).
Template IDs can be retrieved using the Docuseal List Templates or Get Template source endpoints. Submitter roles must exactly match the role names defined in the selected template. Refer to the DocuSeal API Reference for the complete list of supported request body fields.
Create Submission from PDF
Creates a one-off submission request directly from a PDF file, without requiring a pre-existing DocuSeal template. Use this endpoint when you need to send a unique document for signing that does not have a corresponding reusable template in DocuSeal—for example, generating a custom agreement from a PDF stored in your data pipeline.
Fields within the PDF can be defined using text tags embedded in the document content. Text tags follow the format {{Field Name;role=Signer1;type=date}}, where each tag specifies the field name, the submitter role it belongs to, and the field type.
Alternatively, field positions can be specified explicitly via the fields parameter using exact pixel coordinates on the document pages, which is useful for PDFs where text tags cannot be embedded.
The request body must include the PDF file (as a Base64-encoded string or a URL) and the submitters array with at least one submitter's email and role.
PDF-based submissions are one-off requests and do not create reusable templates in DocuSeal. For recurring document types, consider using the Create Template from PDF endpoint to create a reusable template first, then use the Create Submission endpoint. Refer to the DocuSeal API Reference for supported field types and coordinate-based field configuration.
Create Submission from DOCX
Creates a one-off submission request from a DOCX file with dynamic content variables. Use this endpoint to generate personalized documents from a Word template with variable data substituted at submission creation time—for example, inserting a recipient's name, address, or contract terms from your data pipeline into a standard agreement document.
Dynamic content variables are defined in the DOCX file using double-bracket tags (e.g., [[variable_name]]). The values for these variables are provided in the request body's submitters[].values object, allowing each submission to be personalized with data-driven content.
The request body must include the DOCX file (as a Base64-encoded string or a URL) and the submitters array specifying each signing party's email, role, and any variable values to substitute into the document.
Variable tags in the DOCX file use double square brackets (e.g., [[customer_name]]), which is distinct from the text field tags used in PDF submissions. Ensure variable names in the request body exactly match the tag names in the document. Refer to the DocuSeal API Reference for additional details on DOCX variable substitution.
Create Submission from HTML
Creates a one-off submission request from HTML content, which DocuSeal renders into a fillable and signable document. Use this endpoint to dynamically generate documents from HTML content built or templated in your data pipeline—for example, creating a formatted contract or disclosure form from structured data.
Fillable and signable fields are embedded in the HTML using special DocuSeal field tags. The HTML is rendered server-side into a PDF document that recipients can sign in the DocuSeal signing interface.
The request body must include the html content string and the submitters array specifying each signing party's email and role.
HTML-based submissions allow flexible, programmatically generated document content. Refer to the DocuSeal API Reference for the supported HTML field tag syntax and any CSS or formatting limitations.
Create Submissions from Emails
A simplified API endpoint designed to create submissions for a document template and send them to a list of email addresses in a single request. This endpoint is optimized for automation use cases where each recipient signs an independent copy of the same template—for example, sending a policy acknowledgment or annual disclosure to a list of employees or customers.
The request body must include the template_id of the DocuSeal template to use and an emails array containing the email addresses of all recipients. Each recipient will receive their own independent submission.
Unlike the standard Create Submission endpoint, this simplified endpoint does not require specifying submitter roles or additional submitter metadata—making it ideal for single-signer templates distributed to many recipients.
This endpoint is designed for single-role templates where the same document is sent to multiple recipients independently. For multi-party signing workflows or submissions requiring role assignments or pre-filled fields, use the standard Create Submission endpoint. Refer to the DocuSeal API Reference for complete request body specifications.
Archive Submission
Archives (soft-deletes) a submission by its unique ID. Archived submissions are removed from the active submissions list in DocuSeal but are not permanently deleted. Use this endpoint to automate the archival of expired, cancelled, or superseded submissions as part of a document lifecycle management workflow.
Enter the unique identifier of the submission to archive in the Submission ID field. This is a required field.
Submission IDs can be sourced from the List Submissions or Get Submission source endpoints, or from other data in your Nexla pipeline that tracks submission lifecycle events.
Archiving a submission does not notify submitters. Any pending signing requests associated with the submission will become inaccessible to submitters after archival.
Archived submissions can typically be restored or viewed in DocuSeal's archived submissions view. This operation is a soft delete—it does not permanently remove the submission or its associated signed documents. Refer to the DocuSeal API Reference for details on archival behavior.
Create Template from PDF
Creates a new reusable document template in DocuSeal from a PDF file with embedded field tags. Use this endpoint to programmatically build DocuSeal templates from PDF documents stored in your data pipeline, enabling automated template management as part of a document operations workflow.
The request body must include the PDF file (as a Base64-encoded string or a URL) and a name for the new template.
Fields within the template are defined using text tags embedded in the PDF, following the same syntax as the Create Submission from PDF endpoint.
Once created, the template is available in DocuSeal for use with the Create Submission endpoint. The API response includes the new template's ID, which can be used in subsequent submission creation requests.
Programmatically created templates appear in the DocuSeal dashboard alongside manually created templates. Refer to the DocuSeal API Reference for the full list of supported request body fields and field tag syntax.
Create Template from DOCX
Creates a new document template in DocuSeal from a DOCX file with dynamic variable tags for content substitution at submission time. Use this endpoint to build reusable, data-driven document templates from Word files stored in your pipeline.
Dynamic variable tags are defined in the DOCX file using double-bracket syntax (e.g., [[variable_name]]). The values for these variables are supplied when submissions are created from the template.
The request body must include the DOCX file (as a Base64-encoded string or a URL) and a name for the new template.
The API response includes the new template's ID, which can be passed to the Create Submission endpoint to initiate signature requests from the new template.
Create Template from HTML
Generates a new reusable PDF document template in DocuSeal from HTML content, with pre-defined fillable and signable fields embedded via special HTML tags. Use this endpoint to programmatically create templates from dynamically generated HTML, allowing your data pipeline to produce fully structured e-signature templates without manually building them in the DocuSeal UI.
The request body must include the html string containing the document content and field tags, as well as a name for the new template.
Once created, the template is stored in DocuSeal and can be used with the Create Submission endpoint to initiate signing workflows. The API response includes the new template's ID.
Merge Templates
Merges two or more existing DocuSeal templates (including their documents and fields) into a single new combined template. Use this endpoint to programmatically combine related document templates—for example, merging a cover page template with a main agreement template to create a unified multi-document signing package.
The request body must include a template_ids array containing the IDs of the templates to merge (in the desired order) and a name for the resulting combined template.
Template IDs can be retrieved using the List Templates or Get Template source endpoints. The templates are merged in the order specified in the template_ids array.
The API response includes the new merged template's ID, which can be used to create submissions from the combined document.
Update Template
Updates an existing DocuSeal template's name or folder assignment by its unique ID. Use this endpoint to automate template organization—for example, renaming templates or moving them into specific folders as part of a document management workflow.
Enter the unique identifier of the template to update in the Template ID field. This is a required field.
The request body can include a new name for the template and/or a folder_name to move the template to a different folder in DocuSeal.
Template IDs can be retrieved using the List Templates or Get Template source endpoints.
Update Template Documents
Adds, removes, or replaces the documents within an existing DocuSeal template with new PDF, DOCX, or HTML content. Use this endpoint to programmatically update the document content of a template without recreating it from scratch—for example, refreshing the underlying PDF of a contract template when terms change.
Enter the unique identifier of the template whose documents should be updated in the Template ID field. This is a required field.
The request body must include the new document content (as a PDF, DOCX, or HTML file) and specify the update operation (add, replace, or remove documents). Existing field definitions may be affected depending on the documents being replaced.
Template IDs can be retrieved using the List Templates or Get Template source endpoints.
Updating template documents may alter or remove existing field definitions if the new documents have different content or structure. Review the template in the DocuSeal dashboard after updating to verify that all fields are correctly positioned. Refer to the DocuSeal API Reference for the full specification of supported update operations.
Archive Template
Archives a DocuSeal document template by its unique ID, removing it from the active templates list. Use this endpoint to automate the retirement of outdated or superseded templates as part of a document lifecycle management workflow.
Enter the unique identifier of the template to archive in the Template ID field. This is a required field.
Archiving a template does not delete it permanently and does not affect submissions that were already created from the template. New submissions cannot be created from an archived template.
Template IDs can be retrieved using the List Templates or Get Template source endpoints.
Clone Template
Creates an exact copy of an existing DocuSeal template, including all its documents and field definitions. Use this endpoint to programmatically duplicate templates as a starting point for creating similar document types, or to create environment-specific copies of a template (e.g., a staging copy of a production template).
Enter the unique identifier of the template to clone in the Template ID field. This is a required field.
The API response includes the new cloned template's ID. The clone is created as a new independent template; changes to the clone do not affect the original.
Template IDs can be retrieved using the List Templates or Get Template source endpoints.
Update Submitter
Updates the details of an existing submitter record, pre-fills form field values on their behalf, and/or re-sends the signing invitation email. Use this endpoint to automate submitter management workflows—for example, updating a signer's email address, pre-populating fields with data from your pipeline, or re-sending an invitation that expired or was missed.
Enter the unique identifier of the submitter to update in the Submitter ID field. This is a required field.
The request body can include any combination of the following updatable fields:
email: Updated email address for the submitter.
name: Updated display name for the submitter.
phone: Updated phone number (used for SMS-based signing invitations).
fields: An array of field objects with pre-filled values to populate the submitter's form fields before they sign.
send_email: Set to true to re-send the signing invitation email to the submitter's current (or updated) email address.
Submitter IDs can be retrieved using the List Submitters or Get Submission source endpoints.
Pre-filling field values via the Update Submitter endpoint is particularly useful for automating document workflows where some fields can be populated from upstream data (e.g., customer name, address, or account number) before the signer reviews and signs the document. Refer to the DocuSeal API Reference for the field object structure required for pre-filling.
Docuseal destinations can also be manually configured to send data to any valid DocuSeal API endpoint. 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.
DocuSeal's REST API expects data in JSON format for all write operations. DocuSeal API base URLs are the same as for data sources—Global Cloudhttps://api.docuseal.com, EU Cloudhttps://api.docuseal.eu, or your self-hosted instance's API URL. Most create endpoints (submissions, templates) use POST; use PUT to fully replace an existing template or submitter, and DELETE to archive a submission or template. For update or archive operations, include the resource ID at the end of the URL (e.g., https://api.docuseal.com/submissions/12345 to archive submission 12345).
You do not need to include the X-Auth-Token header in Request Headers—this is handled automatically based on your Docuseal credential configuration. The response webhook option is useful for tracking the status of each API call—for example, capturing the submission ID and status returned by DocuSeal after each Create Submission request.
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 begin sending data to DocuSeal, open the destination resource menu, and select Activate.
The Nexset data will not be sent to DocuSeal until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.
