Connect DocuSign to Definable AI

DocuSign provides eSignature and digital agreement solutions, enabling businesses to send, sign, track, and manage documents electronically

About DocuSign

DocuSign is a productivity tool. Connect it to Definable AI with one-click OAuth2 — no API keys or custom code required.

What you can automate with DocuSign

Use Definable AI's agent platform to trigger workflows from DocuSign, process results with 50+ AI models, and sync data across 900+ connected apps.

Tools & Actions (349 available)

Add Email Overrides To Envelope: Adds or modifies email override settings for a specific DocuSign envelope, allowing customization of the reply-to email address and name, as well as BCC email addresses for archiving purposes. This endpoint should be used when you need to change email settings for an individual envelope, overriding the account-level configurations. It's particularly useful for setting up specialized archiving or customizing the reply-to information for specific envelopes. Note that these changes only affect email communications that occur after the addition is made, and the BCC feature is limited to users with appropriate permissions. For security reasons, additional signer authentication is recommended when using the BCC for Email Archive feature.
Add contacts to contacts list: Adds multiple contacts to a user's contacts list in DocuSign. This endpoint allows for bulk addition of contacts with detailed information, including cloud provider details, phone numbers, email addresses, and notary-specific information. It's particularly useful for populating a user's address book efficiently or synchronizing contacts from external sources. The endpoint supports various contact types, including regular contacts, shared contacts, and signing groups. Use this when you need to add or update multiple contacts simultaneously in a DocuSign account. Note that while it can handle a variety of contact information, it does not provide functionality for removing or deactivating contacts.
Add envelope attachments: Adds one or more envelope attachments to a draft or in-process envelope in DocuSign. This endpoint allows developers to include additional files with an envelope that are not converted to PDF and are only accessible through the API. It's useful for attaching supporting documents or metadata files that should not be part of the main signing process. The endpoint supports up to 12 attachments per envelope, with a maximum file size of 50 MB each. Note that these attachments are not visible in the DocuSign web application and are intended for programmatic use only.
Add existing brand to group: This endpoint adds one or more existing brands to a specified group in DocuSign. It allows users to associate multiple brands with a group, enabling customized branding for different groups within an account. The endpoint should be used when there's a need to update the brands associated with a particular group, such as when reorganizing branding strategies or expanding brand options for specific user groups. It's important to note that this endpoint only adds existing brands to a group and does not create new brands or modify brand details.
Add file to workspace: This endpoint adds a file to a specific folder within a DocuSign workspace. It allows users to upload and organize files in their DocuSign account, enabling better document management and collaboration. The method should be used when integrating file upload functionality with DocuSign workspaces, such as when adding new documents to a project or sharing files with team members. It's important to note that this endpoint only handles the file addition process and does not provide functions for file modification or deletion.
Add members to signing group: This endpoint adds one or more new members to a specified signing group within a DocuSign account. Signing groups allow multiple users to act as potential signers for a document, where any member of the group can sign on behalf of the group. This tool should be used when you need to expand or update the membership of an existing signing group. The endpoint allows you to add up to 50 members to a signing group, which is the maximum limit. When adding members, you must provide their email addresses and usernames. It's important to note that DocuSign recommends separating signer recipients and non-signer recipients (such as carbon copy recipients) into different signing groups to maintain clarity in the signing process.
Add new users to a specified account: This endpoint adds new users to a specified DocuSign account, allowing bulk creation of up to 500 users in a single call. It's ideal for quickly setting up multiple users with customized permissions and settings. The endpoint requires at least a username and email for each user, but supports additional configuration options. It returns detailed information about created users, including IDs and status.
Add or update user custom settings: Adds or updates custom user settings for a specified DocuSign user. This endpoint allows for flexible storage and retrieval of user-specific information that can be used in your own system, separate from standard DocuSign account settings. It supports grouping of settings using the X-DocuSign-User-Settings-Key header for more organized management. The endpoint has a 4,000 character limit for all custom settings per user, including XML and JSON structure.
Add part to chunked upload: Adds a chunk or part to an existing chunked upload in DocuSign. This endpoint is used for uploading large files in smaller pieces, allowing for documents that exceed standard file size limits. It should be used after initiating a new chunked upload and uploading the first part. The method is particularly useful for handling large PDFs and other documents. It's important to note that parts should ideally be uploaded in sequential order, and the entire chunked upload must be completed and used within 20 minutes of initialization. This endpoint cannot replace already received parts or add to committed uploads.
Add step to envelope workflow: This endpoint adds a new step to an existing envelope's workflow in DocuSign. It allows for the configuration of complex workflow rules, including delayed routing, conditional recipients, and specific actions based on envelope status or recipient actions. Use this endpoint when you need to modify an envelope's workflow by adding additional steps or rules after the envelope has been created. This is particularly useful for implementing advanced routing logic or adding pauses in the signing process. The endpoint does not modify existing steps in the workflow; it only adds new ones.
Add templates to document in envelope: This endpoint adds pre-configured templates to a specific document within an existing envelope in DocuSign. It allows you to apply standardized content, such as tabs and anchor text, from templates to documents, streamlining the process of preparing documents for signature. Use this when you need to modify an existing envelope by incorporating template content into its documents. The endpoint is particularly useful for maintaining consistency across documents and automating the addition of necessary fields. Note that applying templates may affect envelope recipients, depending on the template content and the 'preserve_template_recipient' parameter setting. This endpoint does not create new envelopes or documents; it only modifies existing ones.
Add templates to envelope: This endpoint adds templates to an existing DocuSign envelope. It's used to apply pre-defined document templates, including content and settings, to standardize workflows. The operation can affect existing recipients based on the 'preserve_template_recipient' parameter. It's suitable for adding comprehensive template changes to an envelope, not for creating new envelopes or minor modifications.
Add user signature and initials images: Add or update a user's signature and initials images in DocuSign. This action creates default signature images based on the user's name and a DocuSign font style. When using JSON content type (as this action does), DocuSign automatically generates signature images based on the signatureName and signatureFont parameters. Supported signature fonts include: 7_DocuSign, 1_DocuSign, 6_DocuSign, 8_DocuSign, 3_DocuSign, Mistral, 4_DocuSign, 2_DocuSign, 5_DocuSign, and Rage Italic. Note: Custom image uploads using base64-encoded data require multipart/form-data content type, which is not supported by this JSON-based action. For custom signature images, you need to use a different method. Important: The userId must match the authenticated user's ID. Users can only modify their own signatures. Each update may generate a new signatureId, so applications should rely on the signature name for consistent identification.
Add users to existing group: Adds one or more existing DocuSign users to an existing group within a specified account. This endpoint is used to manage group memberships by adding users to a predefined group. It requires the account ID and group ID as path parameters, and accepts a list of user information in the request body. The operation returns detailed information about the added users and the result set. Use this endpoint when you need to update group memberships or organize users into specific groups for access control or administrative purposes. Note that this endpoint only adds existing users to a group; it does not create new users or groups.
Addorupdateaccountstamps: Add or update account-level stamps (Japanese Hanko-style stamps) in DocuSign. Stamps are pre-configured signature images that can be applied to documents. This action supports creating new stamps or updating existing ones by including the signatureId. **Common use cases:** - Create name stamps (NameHanko format) for quick document signing - Create name+date stamps (NameDateHanko format) for timestamped signatures - Update stamp properties like size, format, or resize permissions - Manage multiple stamps in bulk operations **Required fields for creating stamps:** - signatureName: Display name for the stamp - stampType: Must be 'stamp' (not 'signature') - stampFormat: Either 'NameHanko' or 'NameDateHanko' **To update existing stamps:** Include the signatureId along with updated fields. Note: This manages stamp definitions only, not the actual signing of documents.
Addorupdateusersignature: This endpoint allows you to add or update a user's signature in DocuSign. It provides comprehensive management of signature properties, including the signature image, font, initials, and stamp details. Use this endpoint when you need to create a new signature for a user or modify an existing one. The endpoint supports various signature types (standard signatures, initials, and stamps) and allows for detailed customization of signature appearance and behavior. It's particularly useful for maintaining up-to-date and personalized signature information for DocuSign users. Note that users can only manage their own signatures; even users with admin rights cannot modify another user's signature settings.
Apply action to bulk send envelopes: This endpoint allows users to apply specific actions (resend, correct, or void) to all envelopes within a specified DocuSign bulk send batch. It's designed for managing large-scale document signing processes efficiently, enabling users to update the status or take action on multiple envelopes simultaneously. This tool is particularly useful when you need to resend failed envelopes, correct errors in a batch of envelopes, or void an entire batch of envelopes. It should be used carefully, as the actions applied will affect all envelopes in the specified batch.
Changeusersinaccount: This endpoint allows you to update information for one or more users within a DocuSign account. It is used to modify various user attributes such as personal information, settings, permissions, and notification preferences. The endpoint is particularly useful for account administrators who need to manage multiple users or update specific user settings en masse. It can handle updates for a single user or batch updates for multiple users in one request. The endpoint provides granular control over user settings, allowing for detailed customization of user profiles and permissions within the DocuSign environment. However, it's important to note that some settings may be limited by the account's plan or the user's role within the organization.
Closeusersinaccount: Closes one or more users in a DocuSign account, preventing them from accessing account features without permanently deleting them. This endpoint is useful for temporarily disabling user access, such as when an employee is on leave or has changed roles. It allows for easy re-activation of users through the Users:update method. The operation affects multiple users in a single request, streamlining bulk user management tasks.
Commit chunked upload for envelopes: This endpoint commits a chunked upload in DocuSign, finalizing the upload process and preparing the uploaded content for use in other API calls. It should be used after all parts of a large document have been uploaded using the chunked upload method. The endpoint performs integrity checks on the uploaded content and, if successful, marks the chunked upload as ready for use. It's crucial to note that once committed, no additional parts can be added to the upload. This method is particularly useful when dealing with large documents that exceed standard upload size limits, allowing for more efficient handling of sizeable files in the DocuSign workflow.
Configure cloud storage redirect url: Configures the OAuth redirect URL for one or more cloud storage providers (Box, Dropbox, GoogleDrive, SkyDrive/OneDrive, Salesforce) for a specific user in DocuSign. This action sets up the authentication flow between DocuSign and cloud storage services by specifying where users should be redirected after authenticating with the cloud storage provider. The redirect URL must be within the docusign.com or docusign.net domains for security. The response includes authentication URLs with the redirect URL appended as a query parameter. Direct users to these URLs to complete the OAuth flow and connect their cloud storage accounts to DocuSign. Use this when integrating cloud storage services to enable users to access documents from external providers within DocuSign workflows.
Create BCC Email Archive Configuration: Creates a BCC email archive configuration for a DocuSign account, enabling automatic archiving of DocuSign-generated emails. This endpoint allows you to set up a BCC email address that will receive copies of all DocuSign notifications for the specified account. It's particularly useful for organizations that need to maintain comprehensive email records for compliance or auditing purposes. **Key Details:** - Only requires the 'email' parameter - the BCC email address to receive archived emails - Supports up to 5 active and pending email archive addresses per account - Each email address must be added one at a time - After creation, an activation email is sent to the BCC address for confirmation **Important:** The BCC Email Archives feature must be enabled for your DocuSign account before using this action. If not enabled, you'll receive a "BCC_EMAIL_ARCHIVES_NOT_ACTIVATED" error. Contact DocuSign support to enable this feature if needed.
Create Document Responsive HTML Preview: Creates a responsive HTML preview for a specific document in an envelope. Generates a mobile-friendly preview showing how the document renders on different devices. Useful for testing smart sections, collapsible content, and responsive tables before sending. **Requirements:** Envelope and document must already exist. Use CREATE_ENVELOPE_FROM_TEMPLATE first. **Optional:** Provide HTML definition settings (displayAnchors, source) to customize display. **Returns:** HTML preview of the responsive document version.
Create Envelope From Template: Creates a signing envelope from a pre-existing DocuSign template. This action maps specific recipients to template roles and creates an envelope, either as a draft (status='created') or sent immediately (status='sent'). Prerequisites: - Use DOCUSIGN_LIST_ALL_TEMPLATES to get template IDs and role names - Role names in template_roles must match template roles exactly (case-sensitive) - Include 'recipients' parameter in list templates to see available role names Common Use Cases: - Send contracts, NDAs, or agreements for electronic signature - Create multi-party approval workflows with sequential signing - Distribute documents to carbon copy recipients Returns envelope_id for tracking and management.
Create Notary Jurisdiction: Registers a notary jurisdiction for the current DocuSign user, enabling electronic notarizations for a specific U.S. state. A user can only have ONE jurisdiction at a time. Required fields: commissionExpiration (MM/DD/YYYY format), commissionId, registeredName, sealType, and jurisdiction details (jurisdictionId, name, county). Seal type must match jurisdiction requirements: some states like California require user-uploaded seals, while others support system-created seals. Supports 24 U.S. jurisdictions (IDs: 5-California, 6-Colorado, 9-Florida, 10-Georgia, 12-Idaho, 13-Illinois, 14-Indiana, 15-Iowa, 17-Kentucky, 23-Minnesota, 25-Missouri, 30-New Jersey, 32-New York, 33-North Carolina, 35-Ohio, 37-Oregon, 38-Pennsylvania, 40-South Carolina, 43-Texas, 44-Utah, 47-Washington, 48-West Virginia, 49-Wisconsin, 62-Florida Commissioner of Deeds).
Create Preview of Responsive HTML: Creates a preview of the responsive HTML version of a specific template document in DocuSign. This endpoint allows users to visualize how a PDF document will be converted to responsive HTML across various device types before sending it for signing. It's particularly useful for ensuring that template documents are properly formatted for responsive signing, enhancing the signing experience across different devices. The preview can be customized using various display settings and anchors, enabling users to create collapsible sections, responsive tables, and other interactive elements in the signing document.
Create Preview of Responsive HTML in Envelope: Creates a preview of the responsive HTML versions of all documents in an envelope, allowing users to review how PDF documents will appear as responsive HTML across different device types before sending. This endpoint is particularly useful for ensuring document compatibility and readability on various screen sizes and devices, enhancing the signing experience for recipients. It leverages smart sections and display anchors to customize document appearance and behavior, including collapsible sections and responsive tables.
Create Recipient Manual Review Link: Creates a URL for manually reviewing a recipient's identity in DocuSign. This endpoint is used when automatic identity verification has failed and manual review is required. It returns a URL that allows the sender to access a page for manually verifying the recipient's ID. This method should only be used for recipients in workflows that support manual review and whose automatic verification has failed with a specific status code. The returned URL is essential for completing the identity verification process in cases where automatic methods were insufficient.
Create Recipient View URL: Creates a URL for embedding the DocuSign recipient view UI within an application, allowing users to sign documents directly in the app. This endpoint is specifically used for envelopes in the 'sent' status and generates a temporary URL that expires after 5 minutes. It provides a seamless way to integrate electronic signature capabilities into your workflow, ensuring a secure and legally binding signing process. The method requires proper authentication of the recipient's identity and offers various customization options for the embedded experience.
Create Template Custom Fields: Creates custom fields on a DocuSign template to capture additional metadata. Custom fields allow you to: - Add dropdown lists (listCustomFields) where senders select from predefined options - Add text fields (textCustomFields) where senders enter free-form text - Set default values and mark fields as required or optional - Control visibility in the envelope creation interface - Integrate with external systems like Salesforce using merge fields These fields are attached to the template and will appear when creating envelopes from that template, allowing senders to provide additional context or metadata before sending documents for signature. Note: You must provide at least one of listCustomFields or textCustomFields.
Create Template Responsive HTML Preview: Creates a preview of the responsive HTML versions of all documents associated with a DocuSign template. This endpoint enables users to generate and customize the HTML preview of PDF documents across various device types before sending them for signing. It is particularly useful for ensuring that documents are easily readable and signable on different screen sizes and devices. The preview allows for fine-tuning of display settings, anchors, and other responsive elements to optimize the signing experience.
Create Template Workflow Step: Adds a new workflow step to an existing DocuSign template. This action enables sophisticated document routing automation within templates, including: - Pausing workflows before specific routing steps - Implementing delayed sending with scheduled resume dates - Setting up conditional recipient routing based on form field values - Creating multi-stage approval or review processes The workflow step controls the timing and conditions for sending documents to recipients. Common use cases include approval chains, compliance reviews, and conditional routing based on document data. Note: Only one workflow step type (delayed routing OR recipient routing) can be configured per step. Workflow steps are triggered based on routing order positions within the template.
Create User Authorization For Agent User: Creates a user authorization in DocuSign, enabling an agent user to perform specific actions on behalf of a principal user within the same account. This endpoint is essential for setting up delegated access, allowing users to share envelope management, signing, or sending capabilities. It's particularly useful for streamlining workflow processes in scenarios where one user needs to act on behalf of another, such as an assistant managing documents for an executive. The authorization can be time-bound and is subject to account-level permissions. Note that only account administrators or the principal user can create these authorizations, and each principal can only share signing permission with one agent user at a time.
Create a collaborative workspace: Creates a new collaborative workspace in DocuSign for document management and team collaboration. A workspace provides a centralized area for file sharing and collaborative work on agreements. Use this when setting up a new project or team workspace. The creator becomes the workspace owner automatically. After creation, you can add members and upload files using separate actions. Minimal required input: accountId and workspaceName. Optional settings include workspaceDescription and commentsAllowed for enabling document comments.
Create account custom field: Creates a new custom field at the account level in DocuSign, making it available for all new envelopes associated with the account. This endpoint enables account administrators to define custom fields for enhanced envelope management and grouping. The created custom field can be of type 'text' or 'list', and can be set as required or optional. It's particularly useful for standardizing data collection across all envelopes within an account and can optionally be applied to existing templates.
Create brand profiles for account: Creates a new brand profile for a DocuSign account to customize the signing and sending experience with your organization's visual identity and branding elements. This action allows you to define brand properties such as company name, brand languages, colors for UI elements (buttons, headers), and custom landing pages. The accountId is automatically populated from authentication credentials. Brand logos must be uploaded separately using the brand logo management endpoints after creating the brand profile. **Requirements:** The DocuSign account must have 'canSelfBrandSign' or 'canSelfBrandSend' settings enabled. Without these permissions, the API will return a 400 error. Contact your DocuSign administrator to enable branding features if needed. **Typical workflow:** 1) Create brand profile with this action, 2) Upload logos via updateLogo endpoint, 3) Apply brand to envelopes during creation.
Create bulk send request: Initiates a bulk send process in DocuSign to send a single template or envelope to multiple recipients in a single batch operation. This is ideal for large-scale document distribution scenarios such as sending contracts to numerous clients or company-wide notices. **Prerequisites:** 1. Create a bulk send list first (using createBulkSendList API) with recipient data 2. Ensure you have a template with recipient roles matching the bulk list's roleNames 3. The bulk send list must contain at least one recipient entry **How it works:** - The bulk send list defines recipient data (names, emails, role assignments) - The template defines the document structure and recipient roles - DocuSign creates one envelope per entry in the bulk send list - All envelopes are queued asynchronously for processing **Important:** Test compatibility using createBulkSendTestRequest before sending. The returned batchId can be used to track the bulk send operation status.
Create bulk send test request: This endpoint creates a Bulk Send Test Request to validate the compatibility between a bulk send list and an envelope or template for DocuSign's bulk sending feature. It performs comprehensive checks on envelope state, recipients, tabs, and custom fields to ensure a successful bulk send operation. Use this endpoint before initiating an actual bulk send to identify and resolve any potential issues. The test returns a boolean indicating whether the send can proceed, along with detailed validation error information if applicable. This endpoint is essential for maintaining the integrity and efficiency of bulk sending processes in DocuSign.
Create connect configuration for account: This endpoint creates a custom Connect configuration for a specified DocuSign account, enabling webhook notifications for envelope and recipient events. It allows users to set up real-time updates for eSignature workflows without the need for polling. The configuration can be customized for different delivery modes, data formats, and event triggers, providing flexibility in how and when notifications are received.
Create custom document fields in envelope: Creates custom document fields in an existing envelope document within DocuSign. This endpoint allows you to add metadata to specific documents in an envelope, which can be used for tracking, sorting, and reporting purposes. It's particularly useful when you need to associate additional information with a document that isn't captured by standard DocuSign fields. The custom fields are not used by DocuSign for processing but are returned in the envelope status. This endpoint should be used after an envelope has been created and when you need to add or update custom metadata for a specific document within that envelope.
Create custom fields for envelope: This endpoint allows you to create or update custom fields for a specific DocuSign envelope. It is used to add or modify additional metadata to envelopes, which can be utilized for sorting, organizing, searching, and other downstream processes. The endpoint supports both list-type custom fields (with predefined options) and text-type custom fields (for free-form entry). This operation is applicable to draft and in-process envelopes only and should not be used for completed envelopes. Custom fields added through this endpoint will be visible in the Envelope Settings section of the DocuSign console but will not be visible to envelope recipients.
Create custom fields in template document: Creates custom document fields in an existing template document within DocuSign. This endpoint allows users to add metadata to specific documents in a template, enhancing document management and workflow customization. It is particularly useful for prepopulating custom data fields that will be applied to all new envelopes created using this template. The endpoint requires the account ID, document ID, and template ID to identify the exact document within a specific template. Custom fields are added as name-value pairs, allowing for flexible metadata structuring within the constraints of DocuSign's field limitations.
Create sender view url for envelope: Creates a URL for the sender view of a DocuSign envelope, enabling the embedding of DocuSign UI within an external application. This endpoint is crucial for integrating envelope sending functionality, allowing users to prepare and send envelopes directly from your application. The returned URL provides a customizable sender view for an envelope in the 'Created' state, with options to tailor the user interface and behavior. It's important to note that the URL must be used immediately after generation and is valid for only one use. The endpoint offers extensive customization options through the 'settings' object, allowing control over UI elements, button behaviors, and access levels. For mobile integrations, especially iOS devices, it's recommended to use a WebView instead of an iframe due to screen space limitations.
Create signing group: Creates one or more signing groups in a DocuSign account. This endpoint allows account administrators to set up predefined groups of recipients for document signing. Multiple signing groups can be created in a single API call, enhancing efficiency in setting up complex signing workflows. Use this when you need to establish teams or departments that can collectively receive and sign documents, with any member able to sign on behalf of the group.
Create template recipient preview url: Generate a preview URL showing how a template will appear to recipients. This action creates an embeddable URL that displays a template from the recipient's perspective, allowing senders to verify the signing experience before sending the actual document. This is particularly useful for: - Previewing tab placement and field positions - Validating the recipient workflow and experience - Testing template configuration before production use - Providing a "preview" feature in template management interfaces The returned URL can be embedded in an iframe or opened in a new window. The preview is read-only and does not affect the actual template. Note: This is for templates only, not for envelopes or sent documents. Use create_recipient_preview_for_envelope for envelope previews.
Createcustomtabwithproperties: Creates a custom tab with pre-defined properties for use in DocuSign envelopes. This endpoint allows users to define reusable tab types with specific configurations such as font styles, validation patterns, and positioning rules. Custom tabs can be created for various field types including text, checkboxes, radio buttons, and signature fields. This tool is particularly useful for standardizing frequently used tab configurations across multiple documents and improving efficiency in envelope creation.
Creategroupsforaccount: Creates one or more groups for a specified DocuSign account. This endpoint is used for managing user access and permissions by organizing users into groups. Groups can be associated with permission profiles to streamline user management for large numbers of users. The endpoint accepts an array of group objects, each containing a group name and optionally a permission profile ID. It's particularly useful for setting up new organizational structures, managing template access, or preparing for bulk user management. Note that only the 'groupName' and 'permissionProfileId' properties are used in the request; all other properties in the group objects are ignored. To associate permission profiles with groups, you need to first obtain the permission profile IDs using the AccountPermissionProfiles: list endpoint.
Createidproofresourcetokenforrecipient: Generates a 2-minute resource token to access recipient identity verification data via DocuSign's ID Evidence API. **Requirements:** Recipient must have completed identity verification (phone auth, ID scan, etc.) during envelope signing. Fails if envelope is draft or verification incomplete. **Usage:** Get token and proof_base_uri, then call ID Evidence API with "Bearer {token}" to retrieve verification details (ID scans, selfies, phone records). **Response:** resource_token (expires 2 min), proof_base_uri (API base URL like https://proof-d.docusign.net). Use for compliance/audit to programmatically verify recipient identity data.
Createnewaccountpermissionprofile: This endpoint creates a new permission profile for a DocuSign account, defining specific sets of permissions for user groups. It allows administrators to establish role-based access control within their DocuSign environment. The profile controls a wide range of user capabilities, from basic envelope sending to advanced account management functions. Use this endpoint when setting up new roles or modifying existing permission structures. Note that creating a profile doesn't automatically assign users to it; separate actions are required for user assignment.
Createorupdateuserauthorizations: Creates or updates user authorizations in DocuSign, allowing an agent user to perform actions on behalf of a principal user. Grants permissions like Send, Manage, Sign, or Edit. Requirements: principal must be authenticated user or caller must be admin; agent users must be active; principal and agent must differ; agentUser.accountId and agentUser.userId are required. Returns HTTP 201 with results array showing success/error for each authorization attempt.
Createrecipientpreviewforenvelope: Creates a URL for previewing the recipient's view of a draft envelope or template. This endpoint allows senders to simulate the recipient's experience by generating an embeddable preview URL. It's useful for verifying the appearance and functionality of an envelope before sending it to recipients. The preview can help identify any issues with document layout, field placements, or signing order, ensuring a smooth signing experience for the recipients.
Createurlfortemplateeditview: Creates a URL for embedding the DocuSign Template Edit view within an application. This endpoint enables developers to integrate DocuSign's template creation and editing functionality directly into their applications, allowing users to manage templates without leaving the app environment. The generated URL provides access to the DocuSign Template UI, where users can create, modify, and save templates. This method is particularly useful for applications that need to offer template management capabilities while maintaining a seamless user experience. It's important to note that this endpoint focuses solely on generating the URL for template editing and does not handle the actual template modifications.
Delete Brand Logo By Type: This endpoint deletes a specific logo from an account brand in DocuSign. It allows users to remove primary, secondary, or email logos associated with their brand, helping maintain brand consistency across DocuSign documents. The endpoint should be used when updating or removing branding elements from a DocuSign account. Note that branding for either signing or sending must be enabled for the account (canSelfBrandSend, canSelfBrandSign, or both must be true) for this endpoint to function properly. This operation is irreversible, so caution should be exercised when using it.
Delete Brand from Group: This endpoint allows users to delete one or more brands from a specified group within a DocuSign account. It is used to manage brand associations with groups, enabling customization of branding for different envelopes and signing experiences. The operation removes the specified brands from the group, updating the group's brand configurations. Use this endpoint when you need to disassociate brands from a particular group, such as during reorganization or brand consolidation processes. Note that this action does not delete the brands from the account entirely, but only removes their association with the specified group.
Delete Connect Log Entries: Deletes Connect log entries for a DocuSign account. This endpoint allows account administrators to manage and clean up Connect event logs, which record webhook delivery attempts and outcomes. **Use Case:** Remove Connect log entries for data management, privacy compliance, or housekeeping purposes. **Requirements:** - Account administrator privileges - Connect must be enabled on the account - Provide a list of log IDs to delete specific entries **Important:** This operation is irreversible. Deleted log entries cannot be recovered. Ensure you have identified the correct log IDs before deletion. Use the list/get Connect logs endpoints first to identify the logs you want to delete. **Note:** The endpoint behavior may vary based on the logIds parameter: - With logIds: Deletes specific log entries - Without logIds: Behavior depends on API implementation (may delete all or return error)
Delete Delayed Routing Rule For Envelope Step: This endpoint deletes the delayed routing object for a specific envelope's workflow step in DocuSign. It allows users to remove scheduled delays in the routing process of an envelope. The endpoint should be used when you need to cancel a planned delay in the envelope's workflow, but it cannot be called once the delay is already in progress. After deletion, the workflow step will still contain a 'pause_before' action, requiring manual unpausing of the envelope when the step is reached. For complete removal of the step, use the deleteEnvelopeWorkflowStepDefinition endpoint instead. This tool is crucial for managing and adjusting envelope workflows in DocuSign, particularly when dealing with time-sensitive documents or when workflow changes are necessary.
Delete Envelope Custom Fields: This endpoint deletes envelope custom fields for draft and in-process envelopes in DocuSign. It allows users to remove both list custom fields (predefined options) and text custom fields (free-form text) associated with a specific envelope. The operation requires the account ID and envelope ID to identify the target envelope. After deletion, the endpoint returns the updated custom fields structure, reflecting the changes made. This functionality is useful for managing and updating envelope metadata, particularly for sorting, organizing, and searching envelopes or integrating with external systems like Salesforce.
Delete Envelope Email Settings: Deletes all existing email override settings for a specific envelope in DocuSign. This endpoint reverts the envelope's email configuration back to the account's default settings, affecting only future email communications. It's useful when you need to remove customized email settings for an envelope, such as reply-to address overrides or BCC recipients. The deletion is permanent and cannot be undone, so use with caution. This operation requires appropriate account permissions and should be used when standardizing email communications for an envelope or removing outdated customizations.
Delete Envelope Lock: Deletes the lock from a specified envelope, allowing it to be modified again. **Important Requirements:** - Only the user who originally locked the envelope can delete the lock - The lock is automatically released when the lock duration expires - Deleting a lock without the X-DocuSign-Edit header will simply unlock the envelope - To save changes made during the lock period, include the X-DocuSign-Edit header with the lockToken **Use Cases:** - Release an envelope lock after completing edits - Allow other users to modify an envelope - Clean up locks that are no longer needed **Note:** You cannot delete a lock created by another user. The authenticated user must be the same user who created the lock.
Delete account brand: This endpoint deletes a specific brand from a DocuSign account. It should be used when you need to permanently remove a brand configuration from an account, such as when a brand is no longer needed or has been replaced. The operation requires that branding for either signing or sending (or both) is enabled for the account. This is indicated by the account settings 'canSelfBrandSend' or 'canSelfBrandSign' being set to true. The deletion is irreversible, so it should be used with caution. If successful, the brand will be completely removed from the account and can no longer be applied to documents or emails. This endpoint does not return the deleted brand details; it only confirms the successful deletion or returns an error if the operation fails.
Delete account custom field: Deletes an existing account custom field from a DocuSign account. This endpoint should be used when you need to remove a custom field that is no longer required or relevant for your account. It permanently removes the custom field, so use with caution. The deletion can optionally be applied to templates as well. This operation is part of the account management functionality and affects how custom metadata can be used in future envelope creations.
Delete account permission profile: This endpoint deletes a specific permission profile from a DocuSign account. It is used to remove outdated or unnecessary permission profiles, helping to streamline account management. The endpoint requires that the profile being deleted has no associated users, unless they are being reassigned to a new profile. It's particularly useful when restructuring account permissions or during account cleanup processes. The method will fail if there are associated users and no reassignment is specified. It's important to note that this action is irreversible, so caution should be exercised when using this endpoint. This endpoint should not be used for temporary permission changes; instead, it's meant for permanent removal of a permission profile.
Delete account stamp: Deletes a specific account stamp (signature) from a DocuSign account. This endpoint should be used when you need to permanently remove a stamp from an account, such as when it's no longer needed or has been replaced. The operation is irreversible, so use it with caution. It's particularly useful for maintaining account hygiene by removing outdated or unused stamps. Note that this endpoint only deletes the stamp; it does not affect any documents that may have already been signed using this stamp.
Delete bcc email archive configuration: This endpoint deletes a BCC (Blind Carbon Copy) email archive configuration from a specified DocuSign account. When invoked, it changes the status of the targeted configuration to 'closed' and immediately stops the archiving of DocuSign-generated email messages to the associated BCC email address. This operation is useful for managing email archiving settings, particularly when an archiving configuration is no longer needed or needs to be replaced. It's important to note that this action is irreversible, and once deleted, the specific configuration cannot be reactivated – a new one would need to be created if archiving is required again in the future. This endpoint should be used cautiously, as it will impact the email archiving process for the account.
Delete brand profiles: This endpoint allows you to delete one or more brand profiles from a DocuSign account. It is used to remove custom branding configurations that are no longer needed. The method requires either the 'canSelfBrandSign' or 'canSelfBrandSend' setting to be enabled for the account. It's important to note that this operation is irreversible, so care should be taken when using this endpoint. The response provides detailed information about the deleted brands, including their IDs, names, and associated resources.
Delete chunked upload: Deletes a chunked upload that has been committed but not yet consumed in the DocuSign system. This endpoint is useful for managing large file uploads and maintaining quota efficiency. It should be used when a chunked upload is no longer needed and hasn't been used in other API calls. The endpoint cannot delete chunked uploads that have already been consumed or those that have expired. It's recommended to explicitly delete unused chunked uploads rather than waiting for automatic expiration to manage your quota effectively. Note that this API is currently in beta status and may be subject to changes.
Delete connect configuration: Deletes a specified DocuSign Connect configuration from the given account. This endpoint should be used when you need to remove an existing Connect integration setup. It requires account administrator privileges and that Connect is enabled on the account. The operation is irreversible, so use with caution. This endpoint doesn't return the deleted configuration details; it only confirms successful deletion or returns an error.
Delete connect failure log entry: Deletes one or all Connect failure log entries for a specified DocuSign account. This endpoint is used for maintenance and cleanup of Connect integration logs, allowing account administrators to remove specific failure records or clear all failure logs. It should be used when troubleshooting Connect integration issues or performing routine log management. The endpoint requires account administrator privileges and Connect must be enabled on the account. It's important to note that this operation is irreversible, so care should be taken when deleting log entries, especially when using the 'all' option.
Delete connect oauth configuration: Deletes the Connect OAuth configuration for a specified DocuSign account. This endpoint is used to remove the OAuth settings that allow DocuSign Connect to securely integrate with other applications and send webhook notifications. It should be used when you need to disable or reconfigure the Connect OAuth integration for an account. This operation is irreversible and will immediately stop any active Connect OAuth-based integrations for the specified account. Only account administrators can perform this action, and Connect must be enabled on the account for this endpoint to work. It's important to note that this deletion only affects the OAuth configuration for Connect and does not impact other DocuSign integrations or the account itself.
Delete contact from account: Deletes a specific contact from a DocuSign account. This endpoint should be used when you need to remove a contact's information from an account's address book. It requires both the account ID and the specific contact ID to be provided. Upon successful deletion, it returns an updated list of contacts for the account. This operation is irreversible, so it should be used with caution. The endpoint does not provide any confirmation or undo functionality, so ensure the correct contact ID is specified before making the call.
Delete custom document fields: Deletes custom document fields from an existing envelope document in DocuSign. This endpoint allows you to remove specific metadata or custom data strings associated with a document within an envelope. It's useful for updating or cleaning up custom information that is no longer relevant or needed. The operation is performed on a specific document within a specific envelope, identified by their respective IDs. Use this endpoint when you need to manage or update the custom fields of a document, ensuring that only necessary and current information is retained.
Delete custom fields in template: Deletes specified custom fields from a DocuSign template. This action removes envelope-level custom fields (both list and text types) that are no longer needed. **How it works:** - Specify which custom fields to delete by providing their fieldId values - You can delete multiple list and/or text custom fields in a single request - The template must not be locked by another user or application - Get field IDs using the retrieve template custom fields endpoint **Response:** Returns the list of deleted custom field IDs (not the remaining fields). **Use case:** Useful for maintaining templates by removing outdated custom fields, simplifying template structure, and keeping only relevant metadata fields for new envelopes created from this template. **Note:** This deletes template-level custom fields. For document-level custom fields within a template, use the delete custom document fields endpoint instead.
Delete custom tab information: Deletes a specified custom tab from a DocuSign account. This endpoint should be used when you need to remove a custom tab that is no longer needed or is obsolete. It permanently removes the custom tab from the account, so it should be used with caution. The operation requires both the account ID and the specific custom tab ID to ensure precise deletion. This endpoint is particularly useful for maintaining a clean and relevant set of custom tabs in your DocuSign account, especially when managing large numbers of custom fields. Note that this operation cannot be undone, so it's advisable to confirm the deletion with the user before proceeding.
Delete custom user settings: Deletes specified custom user settings for a DocuSign user by their names. Custom user settings allow flexible storage and retrieval of user-specific information within DocuSign (separate from standard account settings). This endpoint removes one or more custom settings by specifying their names in the customSettings array. **Key Points:** - Specify which settings to delete by providing their names in the customSettings array - If customSettings is omitted, all ungrouped custom settings are deleted - For grouped settings, include the X-DocuSign-User-Settings-Key header with the group name - Users can only access and modify their own custom settings (even admins cannot access other users' settings) - The userId must be a valid user GUID; the special value "me" is not supported **Common Use Cases:** - Remove obsolete user preferences or configurations - Clean up user-specific data during account maintenance - Reset custom user settings to defaults
Delete delayed routing rules for template: Deletes the delayed routing rules for a specific template workflow step in DocuSign. This endpoint should be used when you need to remove timing or conditional routing logic from a template, allowing for immediate progression to the next step in the workflow. It's particularly useful when updating or simplifying complex template workflows. Use with caution as this operation is irreversible and may impact the behavior of documents generated from this template in the future. This endpoint does not affect already sent envelopes or documents.
Delete draft envelope attachments: Deletes one or more envelope attachments from a draft envelope in DocuSign. This endpoint allows users to remove attachments that are no longer needed or were added in error before the envelope is sent. It's important to note that this operation only works on draft envelopes and is distinct from managing signer attachments. The endpoint supports deleting multiple attachments in a single request, making it efficient for bulk operations. As this is a beta API, it may be subject to changes in future versions.
Delete eNote Configuration: Deletes an existing eNote configuration associated with a specific DocuSign account. This endpoint is part of the ENoteConfigurations API and is currently in beta status. It should be used when you need to remove an eNote configuration that is no longer needed or is incorrect. The operation is irreversible, so caution should be exercised before deletion. This endpoint only deletes the configuration; it does not affect any existing eNotes or other account settings. Be aware that as this is a beta API, it may be subject to changes or instability. Always test thoroughly in a non-production environment before using in critical systems.
Delete envelope scheduled sending rules: Deletes the scheduled sending rules for a specific envelope's workflow in DocuSign. This endpoint should be used when you need to cancel or remove previously set rules for scheduled sending of an envelope. It's particularly useful for managing automated document workflows where timing adjustments are necessary. The operation is irreversible and should be used with caution. Importantly, this endpoint cannot be called once the scheduled sending countdown has begun, limiting its use to the period before the scheduled send time approaches. This tool helps in maintaining flexibility in document scheduling within the DocuSign system.
Delete envelope transfer rule: Deletes a specific envelope transfer rule from a DocuSign account. This endpoint allows account administrators to remove previously created rules that automatically transfer ownership of envelopes between users. It should be used when a transfer rule is no longer needed or requires updating. The operation is permanent and cannot be undone, so caution should be exercised. This endpoint requires administrator privileges and the "Transfer Custody" feature to be enabled for the account. It will not provide information about the deleted rule or affect existing transferred envelopes.
Delete envelope workflow definition: This endpoint deletes the workflow definition for a specified envelope in DocuSign. It's used to remove any scheduled or automated processes associated with the envelope, such as delayed sending or routing. When called, it cancels any scheduled send and resets the envelope status to 'created'. This is useful for modifying envelopes that were set up with automated workflows but now require changes. After deletion, to send the envelope, you must update its status to 'sent' using a separate Envelopes::Update method. Use this endpoint cautiously, as it will remove all workflow settings for the envelope and cannot be undone.
Delete envelope workflow step: Deletes a specific workflow step from an envelope in DocuSign. This endpoint allows you to remove a single step from an envelope's workflow definition, potentially altering the envelope's processing lifecycle. Use this when you need to modify an envelope's workflow by removing unnecessary or outdated steps. It's particularly useful for simplifying complex workflows or correcting mistakenly added steps. Be cautious when using this endpoint, as deleting a workflow step is irreversible and may impact the envelope's processing sequence. Ensure you have the correct workflowStepId before proceeding with the deletion to avoid unintended consequences.
Delete existing workspace logically: Marks a DocuSign workspace as deleted by changing its status to "status_deleted". This is a logical deletion that makes the workspace inaccessible to users but preserves the workspace data in the system. The workspace will no longer appear in active workspace lists and users cannot access its files or collaborate within it. Required: workspaceId (the accountId is automatically populated from auth metadata) Returns: Full workspace details including the updated status "status_deleted", workspace name, description, creation date, last modified date, and account billing info. Use case: Remove a workspace from active use when a project ends or team is dissolved, while retaining the workspace data for potential recovery or compliance purposes. Note: Once deleted, the workspace cannot be accessed through normal operations. Attempting to delete an already deleted workspace will result in a 400 error.
Delete members from signing group: Removes one or more members from a specified DocuSign signing group. This endpoint allows you to manage the composition of your signing groups by deleting users who no longer need access. It should be used when you want to remove specific individuals from a signing group, such as when an employee leaves the organization or changes roles. The endpoint requires the account ID and signing group ID to identify the correct group, and accepts a list of users to be removed. It's important to note that this operation is irreversible, so care should be taken to ensure the correct users are being removed. This endpoint does not provide the ability to add new members or modify existing member information.
Delete notary jurisdiction: Deletes a specified notary jurisdiction from the DocuSign system. This endpoint should be used when you need to remove a notary jurisdiction from your DocuSign account, typically when a notary is no longer active in a particular jurisdiction or when correcting erroneously added jurisdictions. The operation is irreversible, so it should be used with caution. It's important to note that this endpoint only deletes the jurisdiction and does not affect the notary's overall status or their ability to operate in other jurisdictions. The endpoint supports a limited set of jurisdictions, primarily U.S. states, and will return an error if an unsupported jurisdiction ID is provided. After successful deletion, any attempts to use the deleted jurisdiction for notary activities will fail.
Delete one or more signing groups: Deletes one or more signing groups from a specified DocuSign account. This endpoint allows for bulk deletion of signing groups, which are collections of users authorized to sign documents on behalf of the group. It should be used when you need to remove outdated or unnecessary signing groups from your account. The operation is irreversible, so caution should be exercised when using this endpoint. It's important to note that this action does not delete the individual users within the groups, only the group associations.
Delete page from document in envelope: Deletes a specific page from a document within a DocuSign envelope. This endpoint removes a single page from a document based on its page number. The page is permanently deleted and this operation cannot be undone. **Important Requirements:** - The envelope must be in draft status (not yet sent) - The document must have multiple pages (cannot delete the only page) - Page numbers start at 1 for the first page - The specified page number must exist in the document **Use Cases:** - Removing incorrect or unnecessary pages from documents before sending - Cleaning up documents that were added to an envelope in error - Modifying multi-page documents during envelope preparation **Note:** This operation is destructive and permanent. Always verify the correct page number before deletion. Once sent, envelopes typically cannot have pages deleted due to audit trail requirements.
Delete page from template document: Deletes a specific page from a document within a DocuSign template. This endpoint allows you to remove a single page from a template document, which can be useful for updating or refining existing templates. Use this when you need to modify the structure of a template by removing unnecessary or outdated pages. Note that this operation is irreversible, so ensure you have a backup or are certain about deleting the page. This tool only deletes a single page at a time and does not provide options for bulk page deletion or document replacement.
Delete powerform by id: This endpoint deletes a specific PowerForm identified by its unique ID within a DocuSign account. PowerForms are pre-configured document templates that can be accessed via a custom URL, allowing for easy collection of signatures and form data. Use this endpoint when you need to permanently remove a PowerForm from your account, such as when it's no longer needed or has been replaced by a new version. Be cautious when using this endpoint, as the deletion is irreversible and will remove all associated data and access to the PowerForm. Ensure you have the correct PowerForm ID and account context before proceeding with the deletion to avoid unintended data loss. This operation is typically used for maintenance, compliance, or organizational purposes within your DocuSign account management workflow.
Delete request log files: Deletes all request log files for the authenticated user in DocuSign. This endpoint clears the diagnostic log buffer by removing all current request/response log entries. API request logging in DocuSign captures up to 50 request/response pairs for troubleshooting purposes. Use this action to clear the log buffer after downloading logs or when the buffer is full (logging is automatically disabled when the 50-entry limit is reached). Important notes: - Only logs for the authenticated user are deleted (not account-wide logs) - Deleted logs cannot be recovered - download logs first if needed - The operation requires no parameters and returns an empty response on success - Private information (passwords, integration keys) is never logged, even before deletion - Use with the DOCUSIGN_TOGGLE_API_REQUEST_LOGGING action to manage logging settings Returns an HTTP 204 No Content response on successful deletion.
Delete scheduled sending rules: Deletes all scheduled sending rules associated with a specific DocuSign template's workflow. This endpoint should be used when you need to remove automated sending schedules for a template, reverting it to manual sending only. It's particularly useful for updating or removing outdated scheduling configurations. Be cautious when using this endpoint, as it permanently removes all scheduled sending rules for the specified template, and this action cannot be undone. Ensure that you have the correct template ID and that removing the scheduled sending is indeed the intended action, as it may impact automated document workflows within your organization.
Delete signature for captive recipients: Deletes the signature for one or more captive (embedded) recipients in DocuSign. This endpoint is primarily used for testing and development purposes to reset signatures associated with embedded recipients (identified by clientUserId). After deletion, a new signature can be created the next time the clientUserId is used in an embedded signing session. **Use Cases:** - Testing embedded signing workflows repeatedly with the same test user - Resetting test data in development environments - Clearing signature state before re-testing signing ceremonies **Important Notes:** - This operation permanently removes signature data - Not intended for regular production use - use with caution - The recipients must have been created as embedded/captive recipients (with clientUserId set) - The recipientPart parameter must be set to "signature" (lowercase) **Required Information:** - Account ID (automatically populated) - Client User ID of the captive recipient - Email address of the recipient - Full name of the recipient
Delete specific connect log entry: Deletes a specified entry or all entries from the DocuSign Connect log for a given account. This endpoint is crucial for managing and cleaning up Connect logs, which contain records of events and updates in eSignature workflows. It should be used when you need to remove specific log entries, perhaps for data management or privacy reasons, or when you want to clear all logs for an account. The operation requires account administrator privileges and the Connect feature must be enabled on the account. It's important to note that this action is irreversible, so use it with caution, especially when deleting all logs.
Delete specified account: Deletes (closes) a specified DocuSign account. This operation permanently closes the account and can only be performed by an account admin. Once an account is closed, it cannot be reopened by users and must be reactivated by DocuSign support. Use this endpoint with caution as it has significant implications for access to documents and user data associated with the account. The optional redact_user_data parameter allows for additional data privacy measures during deletion. This endpoint should be used when an organization needs to completely shut down their DocuSign account, such as when ceasing operations or consolidating multiple accounts.
Delete stamp image for account: This endpoint deletes a specific stamp image associated with an account signature in DocuSign. It is used to remove the visual representation of a stamp from a user's account, which can be useful for updating or removing outdated stamps. The endpoint requires the account ID, the type of image being deleted (stamp, signature, or initials), and the specific signature ID. It's important to note that this action is irreversible, so it should be used with caution. The endpoint will return detailed information about the signature after deletion, including any remaining associated images and properties. This tool should be used when a user needs to remove a stamp image from their account, but not when they want to modify or update an existing stamp image.
Delete template lock: Deletes the lock from a specified DocuSign template, releasing it for editing by others. **Important Requirements:** - The lock token is required to authenticate ownership of the lock - Only the user/application that created the lock can delete it - The lock is automatically released when the lock duration expires - The lock token is automatically added to the X-DocuSign-Edit header **Use Cases:** - Release a template lock after completing edits - Allow other users to modify a template that you previously locked - Clean up locks that are no longer needed before they expire naturally **Security Note:** You cannot delete a lock created by another user. The authenticated user must be the same user who created the lock, verified via the lock token.
Delete template workflow step: Deletes a specific workflow step from a template's workflow definition in DocuSign. This endpoint allows users to customize and refine their document workflows by removing individual steps from existing templates. It should be used when modifying the structure of a template's workflow, such as removing an unnecessary approval step or simplifying the signing process. The operation is permanent and cannot be undone, so users should exercise caution when deleting workflow steps. This endpoint is particularly useful for maintaining and optimizing document workflows in response to changing business processes or requirements.
Delete user authorization: Deletes a specific user authorization within the DocuSign system. This endpoint is used to revoke or remove permissions previously granted to a user. It requires either account administrator privileges or being the principal user of the specified authorization. The operation is irreversible, so it should be used cautiously. This tool is particularly useful for managing access control and maintaining security by removing outdated or unnecessary user permissions. It does not provide information about existing authorizations or create new ones; it solely focuses on deletion.
Delete user cloud storage authentication: This endpoint deletes the user authentication information for a specified cloud storage provider in DocuSign. It's used to remove the stored credentials that allow a user to access their cloud storage within the DocuSign platform. After deletion, the next time the user attempts to access this cloud storage provider through DocuSign, they will need to go through the full authentication process again. This endpoint is particularly useful for security purposes, such as when you need to revoke access or troubleshoot authentication issues. It's important to note that this operation only affects the specified user and cloud storage provider combination, and does not impact other users or other cloud storage integrations for the same user.
Delete user initials or signature image: This endpoint deletes a specified initials image or signature image for a user in DocuSign. It allows users to remove either their initials image or signature image from their DocuSign account. The endpoint should be used when a user wants to update or remove their existing signature or initials image. It's important to note that this endpoint can only delete one type of image per call - to delete both initials and signature images, the endpoint must be called twice. The endpoint requires user authentication and can only be used to delete the authenticated user's own images. The response includes detailed information about the user's signature, including creation date, image URIs, and signature properties.
Delete user profile image: Deletes the profile image of a specified user within a DocuSign account. This endpoint should be used when a user wants to remove their current profile picture from their DocuSign account. It's important to note that this operation can only be performed by the user on their own profile; even users with admin rights cannot delete another user's profile image. The endpoint requires both the account ID and the user ID to be specified, ensuring that the operation is performed on the correct user within the correct account. After successful deletion, the user's profile will no longer have an associated image. This endpoint does not provide the ability to upload a new image; it only removes the existing one.
Delete users from group: Deletes one or more users from a specified group within a DocuSign account. This endpoint allows for bulk removal of users from a group, streamlining group management operations. It requires the account ID, group ID, and a list of users to be deleted. The endpoint is useful for maintaining group memberships, such as when employees leave a company or change roles. It returns detailed information about the deleted users and the operation's success. Note that this operation permanently removes users from the specified group and should be used cautiously.
Delete workflow definition for template: Deletes the workflow definition associated with a specific template in DocuSign. This endpoint is used to remove any existing workflow settings from a template, such as scheduled sending or delayed routing. It's particularly useful when you need to reset a template's workflow or prepare it for new workflow configurations. The operation is idempotent, meaning it will return a successful response even if the template doesn't have a workflow definition. This feature allows for safe, repeated calls without causing errors.
Delete workspace files or folders: This endpoint allows for the deletion of one or more files or sub-folders from a DocuSign workspace folder or root. It's used to remove unwanted or obsolete items from a workspace, helping to maintain organization and manage storage. The operation can handle bulk deletions, making it efficient for cleaning up multiple items at once. It's important to note that this action is irreversible, so users should exercise caution when selecting items for deletion. The workspace must have an 'active' status for this operation to succeed. This endpoint should not be used for temporary file management or as a means of archiving, as deleted items cannot be recovered through the API.
Deletecustomdocumentfieldsfromtemplate: Deletes specified custom document fields from an existing template document in DocuSign. This endpoint is useful for maintaining and updating templates by removing unnecessary or outdated custom fields. It should be used when you need to clean up or modify the structure of a template document. The operation is irreversible, so caution should be exercised when using it. This endpoint only removes custom fields and does not affect other aspects of the template or document.
Deletemultiplecontactsfromaccount: Deletes multiple contacts associated with a specific DocuSign account. This endpoint allows for bulk removal of contacts from an account's address book, streamlining contact management operations. It's particularly useful for cleaning up outdated or unnecessary contacts, or when reorganizing large contact lists. The endpoint accepts a list of contact IDs and returns details of the deleted contacts or error information if the deletion was unsuccessful for any contact. Note that this operation is irreversible, so it should be used with caution. It's recommended to verify the contacts to be deleted before making the API call.
Deletetemplatefromenvelopedocument: Deletes a template from a document within an envelope. Removes a previously applied template from a specific document. This is useful when: - Replacing one template with another - Reverting a document to its original state - Correcting template application errors ⚠️ This operation is permanent and cannot be undone. Requirements: - The envelope must be in a modifiable state (draft, created, or sent) - The template must have been previously applied to the document - You need the envelope ID, document ID, and template ID
Deleteuserauthforcloudstorageproviders: This endpoint deletes the user authentication information for one or more cloud storage providers associated with a specific DocuSign user account. It's used to revoke access to connected cloud storage services, requiring the user to re-authenticate the next time they attempt to access these providers through DocuSign. This operation is particularly useful for managing security, updating integrations, or removing unused cloud storage connections. The endpoint requires specific account and user identifiers and accepts a list of storage providers to be affected. It's important to note that this action only removes the authentication link within DocuSign and does not affect the user's actual account with the cloud storage provider.
Deleteuserauthorizations: The DeleteUserAuthorizations endpoint is used to remove one or more user authorizations for a specified principal user within a DocuSign account. This tool allows account administrators or the principal user themselves to revoke specific permissions or access rights previously granted to the user. It's particularly useful for managing user access control, updating user roles, or removing outdated permissions. The endpoint requires the account ID and user ID to be specified, along with a list of authorization IDs to be deleted. It returns a detailed response indicating the success or failure of each deletion attempt, including any error messages. This endpoint should be used cautiously as it directly impacts user access within the DocuSign system.
Deleteusergroup: Deletes one or more existing user groups from a specified DocuSign account. This endpoint should be used when you need to remove user groups that are no longer needed or have become obsolete. It requires the account ID and the group ID(s) of the group(s) to be deleted. The operation is irreversible, so use it with caution. This endpoint only deletes the group itself and does not affect the individual users who were members of the group. After deletion, any permissions or settings associated with the group will no longer apply to its former members.
Deprecated endpoint for tab blob: This deprecated endpoint is used to update tab-related data (tab blobs) within a specific envelope in a DocuSign account. It is important to note that this endpoint should not be used in new integrations or applications due to its deprecated status. The endpoint requires both an account identifier and an envelope identifier to target the correct set of tabs for updating. While it can modify tab data, the exact nature of the modifications and the format of the tab blob are not specified in the provided schema. The endpoint returns a simple success response or an error response with details if the operation fails. Developers should seek alternative, supported methods for managing tabs in DocuSign envelopes.
Exportbrandtoxmlfile: Exports a DocuSign brand's configuration as an XML string. Use this action to retrieve comprehensive brand data including brand ID, name, company name, color scheme (background/text colors), logos (Base64-encoded), language settings, and custom links/landing pages. The XML format makes it suitable for backup, analysis, migration, or integration with other systems. Note: This operation requires branding to be enabled for the account (canSelfBrandSend or canSelfBrandSign must be true). Not all brands can be successfully exported - if a brand returns a 400 error, it may lack the necessary configuration or permissions for export.
Fetch Recipient Names For Email: Retrieves a list of all names associated with a specified email address in DocuSign. This endpoint is useful for identifying multiple recipients or name variants linked to a single email. It can be used to verify recipient information before sending documents for signature or to manage recipient data in your DocuSign integration. The endpoint returns not only the names but also indicates if the email is used by multiple users and if new names can be added to it. This information is valuable for maintaining accurate recipient records and ensuring proper document routing in complex signing scenarios.
Generate Recipient Shared View URL: Generates a URL for embedding the DocuSign recipient view of a shared envelope in your application. IMPORTANT: This endpoint requires the envelope to be explicitly shared with users on the same DocuSign account. The envelope must be shared first using DocuSign's envelope sharing feature. Required: envelopeId (shared envelope), recipientId (from envelope), userId (account member with shared access), authenticationMethod (default: 'None'). Use for team collaboration, delegation, and administrative support workflows. Not recommended for mobile iframes; use WebView on iOS instead.
Generateeditviewurlforenvelope: Generates a URL for accessing and editing an existing envelope within the DocuSign UI, allowing for embedded editing functionality in external applications. This endpoint is identical to the createSender endpoint and is recommended to be replaced by it. The generated URL provides a customizable view for editing envelope details, recipients, and documents.
Generateenvelopecorrectionurl: Generates a URL that allows embedding the envelope correction view of the DocuSign UI within an application. This endpoint enables customization of the correction view appearance and functionality through query parameters. The returned URL provides temporary, one-time access to the envelope correction interface, allowing users to modify and update envelope details securely within your application. **Important Requirements:** - The envelope must be in 'sent' or 'delivered' status (not draft/created) - The user must have permission to correct envelopes (sender or shared access) - A returnUrl is required to redirect users after completing corrections - The correction view is used for envelopes already in the signing workflow **Note:** For draft envelopes, use the sender view or edit view instead.
Get Account Templates: Gets the definition of a template or templates in the specified account. Note: If the count parameter is not used, listTemplates has a default limit of 2,000 templates. If the account has more than 2,000 templates, listTemplates will return the first 2,000 templates. To retrieve more than 2,000 templates, repeat the API call, specifying start_position and count to control the number of templates retrieved.
Get Agent User Authorizations: Returns the authorizations for which the specified user is the agent user. An agent user can act on behalf of other users (principal users) in the account. This endpoint retrieves the list of principal users and their authorization details, including permissions like Send, Manage, Sign, and Edit. Supports filtering by permission level, active status, and pagination for large result sets.
Get BCC Email Archive History: Retrieves the history of changes made to a specific BCC email archive configuration for a DocuSign account. This endpoint allows users to track modifications, including creation, updates, and closure of email addresses used for archiving DocuSign-generated emails. It provides detailed information about each change, including who made the change, when it was made, and the nature of the change. The endpoint supports pagination for efficient retrieval of large result sets.
Get Default Consumer Disclosure: Retrieves the default HTML-formatted Electronic Record and Signature Disclosure (ERSD) associated with a DocuSign account. This endpoint is used to obtain the standard disclosure provided by DocuSign for U.S.-based customers, which is valid only for transactions between U.S.-based parties. It allows retrieval of the disclosure in multiple languages and provides comprehensive details about the ERSD, including company information, withdrawal methods, and the full text of the eSign agreement.
Get Downgrade Plan Info For Account: Retrieves detailed billing information related to a downgrade request for a specific DocuSign account. This endpoint provides essential data about the requested downgrade plan, including the new plan details, payment method, effective date, and current status of the downgrade request. It should be used when managing account billing changes, specifically when an account holder has initiated or is considering a plan downgrade. The tool is particularly useful for account administrators or billing departments to review and process downgrade requests. Note that this endpoint only provides information about existing downgrade requests and does not initiate new downgrades or make changes to the account's current plan.
Get Electronic Disclosure for Recipient: Retrieves the HTML-formatted Electronic Record and Signature Disclosure (ERSD) for a specific envelope recipient in DocuSign. This endpoint allows you to obtain the customized disclosure that may differ from the account-level disclosure based on the signing brand applied to the envelope and the recipient's language settings. It is particularly useful when you need to present the exact disclosure that a recipient will see before they sign a document, ensuring compliance with electronic signature regulations and providing transparency in the signing process.
Get Envelope: Gets the status and basic information about an envelope from DocuSign. This action retrieves detailed information about a specific envelope, including: - Envelope status (created, sent, delivered, completed, declined, voided) - Creation and sent timestamps - Subject and message - Recipient information and their status - Document details - Envelope metadata
Get Envelope DocGen Form Fields: Retrieves document generation form fields from an envelope's documents. DocGen form fields are placeholder fields (tags) in template documents that can be dynamically populated with data before sending. This action returns the list of available form fields including their names, types, validation rules, and current values. Use this to discover which fields can be populated via the UPDATE_ENVELOPE_DOC_GEN_FORM_FIELDS action. Common use cases: - Retrieve form field definitions before populating them with data - Inspect field types and validation requirements - Check current values of form fields in a draft envelope Note: Returns an empty response if the envelope has no DocGen form fields.
Get Envelope Document Fields: Retrieves custom document fields from a specific document within a DocuSign envelope. Custom document fields are metadata key-value pairs attached to individual documents in an envelope. They are different from: - Envelope custom fields (which apply to the entire envelope) - Tabs/fields (which are fillable form fields for recipients) Use this action to retrieve metadata associated with a specific document, such as department codes, project IDs, or other custom categorization data. Prerequisites: - A valid envelope_id (create using DOCUSIGN_CREATE_ENVELOPE_FROM_TEMPLATE) - A valid document_id (obtain from DOCUSIGN_GET_ENVELOPE) - The document must exist in the specified envelope The document_id must be a string representation of a positive integer (1-2147483647). Typically documents are numbered sequentially starting from '1'. Returns a dictionary containing the 'documentFields' array with field objects.
Get Envelope Notification Defaults: Retrieves the default email notification settings for envelopes at the account level. This endpoint returns account-wide defaults for envelope notifications including: - Reminder settings (frequency, email subject/body for reminders) - Expiration settings (days until expiration, warning days) - Delivery preferences and notification triggers - Default behaviors for various envelope lifecycle events These settings are applied to new envelopes unless explicitly overridden at the envelope level. Useful for understanding account notification configuration, auditing settings, or as a reference when customizing envelope-specific notifications. Note: Requires appropriate account permissions to access notification settings.
Get Envelope Scheduled Sending Rules: Get the scheduled sending configuration for a DocuSign envelope. Returns when and how an envelope is scheduled to be sent, including: - Send date/time (resumeDate): When the envelope will be sent - Delay rules: Time to wait before sending (format: d.hh:mm:ss) - Status: Whether sending is pending, started, or completed - Bulk list ID: If used with bulk sending Use this to check if an envelope has scheduled sending enabled and when it will be sent. Requires a valid envelope ID that has scheduled sending configured. Important: Returns 404 if the envelope doesn't have scheduled sending rules. You must first set up scheduled sending using UPDATE_ENVELOPE_SCHEDULED_SENDING_RULES before you can retrieve the configuration. Example use cases: - Check when a draft envelope is scheduled to send - Verify scheduled sending configuration before envelope goes out - Monitor the status of delayed envelope sending
Get Notary Jurisdiction Object: Retrieves detailed information about a specific notary jurisdiction for the authenticated user. This endpoint should be used when a notary needs to access information about their registered jurisdiction, including commission details, seal requirements, and jurisdiction-specific rules. It provides crucial data for notaries to understand their authority and limitations within a particular area. The endpoint can only be accessed by authenticated users who are registered notaries, and the requested jurisdiction must be one that the notary is authorized for. It does not provide information about jurisdictions the notary is not registered for or allow modifications to the jurisdiction data.
Get Notary User Settings: Retrieves notary settings and configuration for the currently authenticated user. This endpoint returns comprehensive notary account information including personal details (name, email, userId), notary status (enabled/disabled), and optionally jurisdiction details when include_jurisdictions is set to "true". **Important**: This endpoint requires: - The authenticated user must be registered as a notary in DocuSign - Appropriate OAuth scopes for notary operations - The account must have notary features enabled Returns information such as: userId, firstName, lastName, email, enabled status, creation/modification timestamps, and jurisdiction details (if requested). Use this when you need to verify a user's notary status, check their enabled jurisdictions, or retrieve notary account configuration details.
Get OAuth User Info: Tool to retrieve authenticated user's account information from DocuSign OAuth. Use this to validate the OAuth access token and obtain essential account details including user ID (sub), name, email, and the list of DocuSign accounts with their base URIs and account IDs for subsequent API calls.
Get Original HTML Definition for Template: Retrieves the original HTML definition for a specified DocuSign template. This endpoint is used to obtain the properties that define how to generate the responsive-formatted HTML for the template's documents. It provides detailed information about display settings, anchors, and collapsible sections that control the appearance and behavior of the template during signing. This tool is essential for developers who need to understand or modify the responsive signing experience for a specific template.
Get PDF Transcript of Envelope Comments: Retrieves a PDF transcript containing all comments added by senders and recipients to documents within a specific envelope in a DocuSign account. This endpoint is useful for obtaining a comprehensive record of all discussions and annotations related to the documents in an envelope. It should be used when a consolidated view of all comments is needed, such as for review, auditing, or record-keeping purposes. The response is a PDF file returned as a byte stream, which can be saved or processed as needed. Note that the comments feature must be enabled in the account settings (set 'enableSigningExtensionComments' to true in accountSettingsInformation) for this endpoint to function. This tool does not provide individual comments or allow for adding or modifying comments.
Get Permission Profile for Account: This endpoint retrieves detailed information about a specific permission profile in a DocuSign account. It provides a comprehensive view of permissions, settings, and capabilities assigned to a profile. Useful for auditing or reviewing permissions granted to user groups, it returns data on account role settings, user settings, API access levels, and other configuration options. Note that this endpoint is read-only and cannot modify profile settings.
Get Recipient Document Visibility: Retrieves document visibility settings for a specific recipient within a DocuSign envelope. This endpoint allows you to check which documents are visible to a particular recipient and their access rights (editable or read-only). Use this method when you need to verify or audit the document access configuration for a recipient in an envelope. It's particularly useful in workflows where different recipients may have varying levels of access to documents within the same envelope. The method returns detailed visibility information but does not modify any settings.
Get Request Log Settings: Tool to retrieve current API request logging settings for the authenticated user. Use when you need to check logging configuration or remaining log entries.
Get Request Logs: Retrieves a list of API request log entries as a JSON object. Use when you need to view diagnostic information about API requests made to DocuSign.
Get Resource Information: Retrieves the base resources available for the DocuSign eSignature REST API. Use when you need to discover available API endpoints and resources.
Get Service Information: Gets the current version and other information about the DocuSign eSignature REST API. Use this to retrieve service information including API versions and build details. This returns the available REST API versions (v1, v2, v2.1) with their endpoint URLs, the current build version string, and linked DocuSign sites.
Get Template: Gets a template definition from the specified account. You can include additional template attributes in the response by using the include parameter: - powerforms: Includes information about PowerForms - tabs: Includes information about tabs - documents: Includes information about documents - favorite_template_status: Includes the template favoritedByMe property
Get Template Document HTML Definition: Retrieves the HTML definition for a specific document within a DocuSign template. This endpoint is used to obtain the properties that define how to generate responsive-formatted HTML for the document, including display anchors, collapsible sections, and other formatting settings. It's particularly useful when implementing responsive signing features or when you need to understand the structure and display properties of a template document. The response includes detailed information about HTML definitions, such as display settings, anchors, and formatting options, which can be used to render the document in a responsive manner across different devices and screen sizes.
Get URL for Embedding DocuSign UI: Generate a URL to embed the DocuSign console view within your application. This action creates a URL that provides access to the DocuSign web interface, allowing users to interact with DocuSign features directly from your application without leaving your UI. **Use Cases:** - Display DocuSign console home page (when no envelopeId provided) - View specific sent envelope documents (with sent envelope ID) - Edit and send draft envelopes via sender view (with draft envelope ID) **Security Note:** This provides full access to the DocuSign account's console interface. Use appropriate access controls in your application when exposing these URLs to users. **Best Practice:** When using with draft envelopes, provide a returnUrl to give users a way to navigate back to your application after completing their task.
Get Watermark Details for Account: Retrieves and previews the watermark details for a specific DocuSign account. This endpoint allows users to view the current watermark configuration, including its visual properties and enabled status. It's useful for verifying existing watermark settings or preparing to update them. The endpoint returns comprehensive information about the watermark but does not modify any settings. Use this when you need to inspect or audit the current watermark configuration for an account.
Get Workflow Step for Envelope: Retrieves detailed information about a specific workflow step for a DocuSign envelope. This endpoint allows you to fetch comprehensive data about a single step in an envelope's workflow, including its action, status, delayed routing settings, and recipient routing rules. It's particularly useful when you need to examine or troubleshoot the configuration of a specific workflow step within an envelope. The endpoint provides insights into how the step is triggered, its current status, and any conditional routing or delay rules applied to it. Use this when you need to understand the exact behavior and settings of a particular workflow step in your DocuSign envelope.
Get account billing charges list: Retrieves a detailed list of recurring and usage charges for a specified DocuSign account. This endpoint provides comprehensive information about the account's billing structure, including charge names, types, pricing, and usage quantities for various DocuSign services. It's particularly useful for account administrators to analyze current usage, understand the pricing structure, and make informed decisions about service utilization. The response includes data on charges such as envelope usage, seat allocations, and additional services like ID checks or in-person signings. Note that this endpoint requires account administrator privileges and does not provide historical billing data or future projections.
Get account password rules: Retrieves the current password rules and security settings for a specified DocuSign account. This endpoint provides detailed information about password expiration policies, lockout durations, password strength requirements, and security question configurations. It is useful for account administrators to review and understand the current security posture of their DocuSign account. The retrieved information can be used to ensure compliance with organizational security policies or to plan password policy updates. This endpoint does not modify any settings; it is for informational purposes only.
Get account stamp image: Retrieves the image file for a specific account stamp, signature, or initials in DocuSign. This endpoint allows users to obtain the visual representation of stamps or signatures associated with their DocuSign account. It's particularly useful when you need to display or embed these images in other documents or applications. The endpoint returns the actual image file in GIF format, not just metadata. It supports retrieving different types of images (stamp, signature, or initials) and offers an option to include or exclude the chrome (frame) around the image.
Get api request log settings: Retrieves the current API request logging settings for the authenticated user in DocuSign. This endpoint provides information about whether API request logging is enabled, the maximum number of log entries allowed, and the remaining number of entries that can be logged. It is useful for developers and administrators who need to monitor or troubleshoot API usage, manage log storage, or ensure compliance with logging policies. The endpoint should be used when you need to check the current state of API request logging or verify remaining log capacity. It does not modify any settings or create new log entries.
Get bcc email archive configurations: Retrieves a list of BCC (Blind Carbon Copy) email archive configurations associated with a specified DocuSign account. This endpoint allows users to fetch details about email addresses used for archiving DocuSign-generated emails. It supports pagination for large result sets and provides comprehensive information about each BCC email archive configuration, including its status, creation date, and associated user details. This tool is useful for auditing or managing BCC email archiving settings within a DocuSign account.
Get brand logo by type: Retrieves a specific logo used in a brand for a DocuSign account. This endpoint allows you to fetch the image file for a primary, secondary, or email logo associated with a particular brand in your DocuSign account. It's useful for maintaining consistent branding across DocuSign documents and communications. The endpoint requires branding to be enabled for the account (either for signing, sending, or both). Use this when you need to display or verify the current logo for a specific brand and logo type within your DocuSign integration.
Get brands information for group: Retrieves detailed brand information associated with a specific group within a DocuSign account. This endpoint provides a comprehensive view of the brand settings, including default brands for recipients and senders, as well as a list of all available brands with their properties. It's particularly useful for administrators managing multiple brands across different groups within an organization. The endpoint should be used when there's a need to review or audit brand assignments, customize group-specific branding, or prepare for brand updates within a group context. It does not modify any brand settings but offers a read-only view of the current brand configuration for the specified group.
Get bulk send batch status: Get the status and progress of a DocuSign bulk send batch operation. This action retrieves comprehensive status information for a bulk send batch, including counts of sent, queued, and failed envelopes. Use this to monitor the progress of large-scale document distribution operations. **Key Response Fields:** - batchSize: Total envelopes in the batch - sent: Successfully sent envelopes - queued: Envelopes still being processed - failed: Failed envelope count - bulkErrors: Details about any failures **Usage Notes:** - Bulk send processing is asynchronous; poll this endpoint to check progress - The batch is complete when batchSize equals (sent + failed) - Recommended polling interval: 30-60 minutes for large batches - Use the bulkSendBatchId returned from creating a bulk send request
Get bulk send lists information: Retrieves a list of Bulk Send Lists belonging to the current user in a specified DocuSign account. This endpoint provides basic information about each Bulk Send List, including its unique identifier, creator, creation date, and name. It is particularly useful for managing and tracking bulk send operations, allowing users to get an overview of their available Bulk Send Lists. This tool should be used when you need to inventory or manage Bulk Send Lists for high-volume document distribution. It does not provide detailed information about the contents of each list or allow for modification of the lists. The response is limited to basic summary information and does not include the actual recipients or documents associated with each list.
Get docusign account contacts: Retrieves detailed information about a specific contact from a DocuSign account's address book. Use this action when you need to look up a contact's details including their name, email addresses, phone numbers, organization, notary certifications, and signing group associations. Requires the contact's unique ID which can be obtained from listing contacts or previous operations. The contact data can be sourced from the default DocuSign address book or connected cloud storage providers like DocuSign Rooms. Note: Phone numbers for shared contacts may have limited visibility to users other than the contact creator.
Get envelope lock information: Retrieves general information about an envelope lock in DocuSign. This endpoint is used to obtain details about the lock on a specific envelope, including the lock token, duration, owner, and expiration time. It's particularly useful for recovering lock information when managing concurrent access to envelopes. The caller must be the same user who initially locked the envelope. Use this endpoint when you need to verify the lock status of an envelope or retrieve the lock token for subsequent operations. It does not modify the lock itself but provides essential information for lock management.
Get members of a signing group: Retrieves the list of members in a specified DocuSign Signing Group. This endpoint provides detailed information about users in a particular Signing Group, including their email addresses and usernames. Use this tool to audit or manage Signing Group composition, which is crucial for maintaining proper document routing and signing workflows. Note that this endpoint only provides information and does not allow group modification.
Get notary journals: Tool to retrieve notary journal entries for the current user. Use when you need to access a user's notary journal records, which contain information about notarized documents including signer names, document names, jurisdictions, and timestamps.
Get notary jurisdictions for user: Retrieves a list of registered notary jurisdictions for the current user. The user must be a registered notary. This endpoint provides information about each jurisdiction where the notary is registered, including commission details, seal settings, and jurisdiction-specific configurations. It is useful for notaries who need to view their registered jurisdictions or for applications that need to display a notary's registration information. The endpoint returns a paginated list of jurisdiction objects with details such as jurisdiction ID, name, commission expiration dates, and seal requirements.
Get powerform senders: Retrieves a list of users who have sent PowerForms within a specified DocuSign account. This endpoint is useful for monitoring PowerForm usage, tracking sender activity, and gathering insights on user engagement with PowerForms. It returns detailed information about each sender, including their account details, email, and login status. The response is paginated, allowing for efficient retrieval of large datasets. This tool should be used when you need to audit PowerForm sender activity or generate reports on PowerForm usage within an account.
Get request logging log file: Downloads the complete log file for a specific API request from DocuSign's Diagnostics service. This action is essential for debugging and troubleshooting API interactions by providing detailed request/response information. The log file contains: - Full HTTP request details (method, URL, headers, body) - Complete HTTP response (status, headers, body) - Timing information - Other diagnostic metadata Note: API request logging must be enabled in your DocuSign account to generate log entries. You can enable it using the 'toggle_api_request_logging' action. After logging is enabled, use 'retrieve_apirequest_log_files' to get a list of available log IDs, then use this action to download specific log files. The log helps you: - Debug API integration issues - Verify request/response data - Troubleshoot authentication problems - Investigate unexpected API behavior
Get signature information for recipient: Retrieves signature information for a specific recipient in a DocuSign envelope. Returns signature metadata including: signature ID, name, type, initials, adoption and modification timestamps, signature image URI, base64-encoded image data, and stamp properties if applicable. **Use when you need to:** - Verify or audit recipient signature details after signing - Display signature images or metadata in your application - Retrieve current signature state within an envelope **Required parameters:** - envelopeId: The envelope ID containing the recipient - recipientId: The recipient's ID (often "1" for first signer) - accountId: Auto-populated from authentication (optional) Note: Returns signature data only, not general recipient status. Recipient must be a signer or sign-in-person recipient type.
Get signing group information: Retrieves detailed information about a specific signing group in a DocuSign account. Returns comprehensive data including the group's name, type (sharedSigningGroup, privateSigningGroup, or systemSigningGroup), email address, creation/modification timestamps, and a complete list of member users with their names and email addresses. This is a read-only operation useful for: - Auditing signing group composition and membership - Verifying group configuration before using in envelope workflows - Administrative tasks and troubleshooting - Integrating signing group data into custom applications The accountId parameter is optional - if not provided, it will be automatically derived from your authentication context. Only the signingGroupId is required.
Get specific brand resource file: Retrieves a specific branding resource file (XML format) for customizing DocuSign experiences. Brand resource files control text and visual elements for sending, signing, email, and captive signing experiences. IMPORTANT: Resource files must be pre-configured for the brand. This is an advanced feature enabled through DocuSign admin or account manager. Use the "return_brand_resource_metadata_for_account" action first to verify which resource types are available before calling this action. Supports localization via language codes and can return either the full master resource file or only modified elements.
Get template delayed routing rules: Retrieves the delayed routing rules for a specific workflow step within a DocuSign template. This endpoint allows users to fetch the scheduled sending and routing information for a particular step in a template's workflow. It's useful for understanding when and how an envelope will be sent to recipients associated with the workflow step. The endpoint should be used when you need to review or verify the delayed routing settings for a template, particularly in automated document workflows. Note that if the specified workflow step does not have a delayed routing object, this method will return a 404 error.
Get template lock information: Retrieves lock information for a DocuSign template. Returns details about an existing template lock including the lock token, duration, expiration time, and information about the user who locked the template. The lock token is required in the X-DocuSign-Edit header for subsequent update operations. Note: Only the user who locked the template (with the same integrator key) can retrieve the lock token. Other users will receive lock information without the token. Use this action to: - Verify if a template is currently locked - Recover lock information after interruption - Get the lock token for making updates to a locked template
Get template notification information: Retrieves the envelope notification, reminders, and expiration information for an existing template in DocuSign. This endpoint allows users to get detailed settings about how notifications are configured for envelopes created from the specified template. It provides information on expiration settings, reminder configurations, and whether account default settings are being used. This tool is useful for reviewing and auditing template notification settings before creating envelopes or when troubleshooting notification-related issues with template-based envelopes. The response includes complex objects for expirations and reminders, giving a comprehensive view of the template's notification setup.
Get template recipient document visibility: Retrieves document visibility settings for a specific recipient in a DocuSign template. Returns which documents are visible to a recipient and their access rights (view/edit). Document visibility controls show or hide specific documents from recipients in multi-document templates, ensuring sensitive information is only shared with authorized parties. **Important:** Document Visibility must be enabled for your account by an administrator. Documents cannot be hidden from recipients if they have tabs assigned to them. Carbon Copy, Certified Delivery, Editor, and Agent recipients can always see all documents. Returns a list of documentVisibility objects with: documentId, visible ("true"/"false"), rights (access level), and recipientId.
Get template scheduled sending settings: Retrieves the scheduled sending settings for a specified DocuSign template. This endpoint allows developers to access and review the configuration that determines when and how envelopes based on the template will be sent. It's particularly useful for automating document workflows and managing the timing of envelope distribution. The endpoint returns detailed information about the scheduled sending rules, including any delays or specific send dates, as well as the current status of the scheduled sending job. It should be used when you need to inspect or verify the scheduled sending configuration of a template, especially in scenarios involving automated or timed document processing. Note that this endpoint will return a 404 error if the template's workflow does not have a scheduled sending object, indicating that no scheduled sending has been configured for the template.
Get templates for envelope document: Retrieves the templates associated with a specific document within a DocuSign envelope. This endpoint is useful for identifying and managing templates linked to individual documents in an envelope, which can be beneficial for template management and document processing workflows. It should be used when you need to retrieve template information for a particular document in an existing envelope, such as for template auditing or document-specific template applications. The endpoint returns detailed information about each associated template, including its ID, name, and matching details, but does not provide the actual template content or allow for template modifications.
Get templates used in envelope: This endpoint retrieves a list of server-side templates used in a specific DocuSign envelope. It provides detailed information about each template, including its name, ID, and other relevant attributes. The endpoint is particularly useful for understanding which templates have been applied to an envelope or finding matching templates for an existing envelope. It can be used to audit envelope contents, analyze template usage, or prepare for envelope modifications. The response includes an array of template summaries, offering a comprehensive view of how templates are utilized within the specified envelope.
Get unsupported file types list: Retrieves the list of file types (extensions and MIME types) that DocuSign does not support for upload. Use this to validate file types before upload or to display supported formats to users. The list may change as DocuSign updates its supported file types.
Get user authorization details: Retrieves detailed information about a specific user authorization in DocuSign. This endpoint allows account administrators or the principal user to fetch comprehensive data about an authorization, including the agent user, principal user, permission levels, and relevant timestamps. It's particularly useful for auditing purposes, reviewing access grants, and managing user permissions within the DocuSign system. The endpoint requires specific identifiers to ensure the correct authorization is accessed and that the requester has the necessary permissions to view the data.
Get user cloud storage provider configuration: Retrieves the cloud storage provider configuration for a specific cloud storage service (identified by serviceId) for a user within a DocuSign account. This endpoint returns configuration details for the specified provider, such as service name and serviceId. Note: This endpoint primarily works with DocuSign-native cloud storage providers (like Rooms). External OAuth-based providers (Box, Dropbox, GoogleDrive, Salesforce, OneDrive) typically return 400 errors even with valid serviceIds, likely because they require authentication flow completion first. For retrieving all cloud storage providers, use the 'Retrieve Cloud Storage Provider Configuration' action instead (GET without serviceId). Users can only access their own cloud storage configuration, even with admin rights.
Get user information by id: Retrieves detailed information about a specific user within a DocuSign account. This endpoint provides comprehensive data about the user, including personal details, account settings, and permissions. It's useful for account administrators and system integrations needing to verify or sync user configurations. Note that users can only access their own information, even with admin rights.
Get users in group: Retrieves a paginated list of users belonging to a specific group within a DocuSign account. This endpoint is useful for managing and auditing group memberships, allowing administrators to view detailed information about users associated with a particular group. It supports pagination to handle large groups efficiently, making it suitable for applications that need to display or process user data in manageable chunks. The endpoint returns comprehensive user information, including account details, email, user status, and membership specifics.
Get workspace file: Retrieves a binary version of a file from a DocuSign workspace. This endpoint allows you to access and download files stored within a specific workspace, folder, and account. It's particularly useful for retrieving document content for further processing or viewing outside the DocuSign platform. The endpoint offers options to download the file as an attachment or convert it to PDF format. Use this when you need to extract file content from a DocuSign workspace, either for backup purposes, local editing, or integration with other systems. Note that this endpoint retrieves the raw file content and does not provide metadata about the file or its signing status.
Get workspace folder contents: Retrieves the contents of a specific workspace folder in DocuSign, including sub-folders and files. This endpoint provides detailed information about the items within the folder, such as metadata, user permissions, and hierarchical structure. It can be used to navigate and explore the contents of a workspace, allowing for efficient management of documents and folders. The endpoint offers various optional parameters to customize the response, enabling users to include or exclude specific types of information based on their needs.
Getelectronicrecordandsignaturedisclosure: Retrieves the HTML-formatted Electronic Record and Signature Disclosure (ERSD) associated with a specific DocuSign account. This endpoint allows you to fetch the current version of the ERSD, which is crucial for obtaining a consumer's consent to receive notices and disclosures electronically. It supports multiple languages through the 'langCode' parameter, enabling you to retrieve the disclosure in various supported languages or automatically detect the user's browser language. This tool is particularly useful when setting up new accounts, updating disclosures, or ensuring compliance with multi-language requirements. Note that while it retrieves the default English disclosure by default, custom disclosures in different languages can be accessed if they have been created for the account. The response includes comprehensive details about the disclosure, including withdrawal options, company information, and the full HTML-formatted ERSD text.
Getenoteintegrationsettings: Retrieves the eNote integration settings for a specified DocuSign account. This endpoint provides crucial information about the eNote configuration status, Connect configuration status, and necessary credentials for eNote functionality. It should be used when setting up or verifying the eNote integration for an account. The endpoint returns details such as API key, organization name, and user credentials, which are essential for configuring the eNote feature. Note that this endpoint is in beta, so its behavior or response structure may change in future updates. It's important to ensure that the account has the "Allow eNote for eOriginal" plan item enabled for full functionality.
Getenvelopeworkflowdefinition: Retrieves the workflow definition for a specified envelope in DocuSign. This endpoint provides detailed information about the envelope's workflow steps, scheduled sending settings, and delayed routing configurations. It is useful for developers who need to understand or analyze the current state and progression of an envelope's workflow. The endpoint returns a comprehensive workflow object, including the current step, scheduled resume date, and an array of all workflow steps with their respective statuses and configurations.
Getenvelopeworkflowdelayedroutingdefinition: Retrieves the delayed routing rules for a specific workflow step within a DocuSign envelope. This endpoint allows users to access information about when and how an envelope is scheduled to be sent to recipients associated with a particular workflow step. It's useful for checking the current delay settings, scheduled send time, and status of a delayed routing step. The endpoint returns detailed information about the resume date, delay rules, and current status of the delayed routing. It should be used when you need to verify or inspect the delayed routing configuration for a specific envelope and workflow step. Note that this endpoint will return a 404 error if the specified workflow step does not have a delayed routing object associated with it.
Getgroupsinformationforaccount: Retrieves detailed information about groups associated with a specific DocuSign account. This endpoint allows users to fetch a list of groups, including their IDs, names, types, and user counts. It's particularly useful for account administrators who need to manage user access, set permissions, or organize users within their DocuSign environment. The endpoint supports pagination, filtering by group type, and text-based searching, making it versatile for various group management tasks. Note that while it provides group information, it does not directly return the list of users within each group; a separate API call is required for that purpose.
Getlistofaccountpermissionprofiles: This endpoint retrieves a comprehensive list of permission profiles associated with a specified DocuSign account. It provides detailed information about each profile, including its unique identifier, name, last modification timestamp, and an extensive set of permission settings. This tool is essential for account administrators who need to review, audit, or manage user access levels and capabilities within their DocuSign environment. It can be used to understand the current permission structure, identify profiles that may need updates, or verify that the appropriate access levels are set for different user groups.
Getpageimagefromenvelope: Retrieves an image of a specific page from a document within a DocuSign envelope. This endpoint is used to fetch a visual representation of a document page, which can be useful for previewing or displaying document contents without accessing the full document. The returned image is in PNG format and can be customized in terms of resolution and dimensions. This tool is ideal for applications that need to show document previews or allow users to view specific pages of a document without downloading the entire file. It should not be used for document modification or to extract text content from the document.
Getspecifiedaccountstampinfo: Retrieves detailed information about a specific account stamp (signature) in DocuSign. This endpoint allows users to fetch comprehensive data about a signature, including its creation and modification dates, image URIs, associated users, and formatting details. It's particularly useful when you need to access or verify the properties of a specific signature within an account. The endpoint provides a wealth of information but requires both the account ID and the specific signature ID to function.
Getsupportedlanguagesforrecipients: Retrieves a comprehensive list of supported languages that can be set for individual recipients when creating a DocuSign envelope. This endpoint allows developers to access the available language options for customizing the standard email format and signing view for each recipient. It's particularly useful when implementing localization features or providing language choices to users in multi-lingual environments. The endpoint returns both the human-readable language names and their corresponding language codes, which can be used in subsequent API calls to set recipient languages. Note that this only affects DocuSign's standard text elements and does not translate custom email content.
Gettabsblobforenvelope: This deprecated endpoint retrieves the tabs blob associated with a specific envelope in DocuSign. It allows developers to access detailed information about the tabs (such as signature fields, text fields, etc.) within a document envelope. However, as this endpoint is no longer recommended for use, developers should seek alternative methods for accessing tab information in new implementations. The endpoint requires both an account ID and an envelope ID to identify the specific envelope and account for which to retrieve the tabs blob. Use this endpoint cautiously and only if absolutely necessary for legacy systems, as it may be removed in future API versions.
Gettabsettingsforaccount: Retrieves the current tab settings and functionality enabled for a specific DocuSign account. This endpoint provides detailed information about various tab types (such as checkbox, radio, text) and related features (like tab order, data labels, text formatting) that are currently active or inactive for the account. It's particularly useful for administrators or developers who need to understand the available tab options before creating or modifying documents within the account. The response includes both the enabled/disabled status of each setting and associated metadata, offering insights into compliance requirements and editability of these settings. This tool should be used when there's a need to audit or verify the account's tab configuration, especially before implementing new document workflows or integrations that rely on specific tab functionalities.
Getuserauthorizationsforprincipal: Retrieves user authorizations for a specified principal user within a DocuSign account. This endpoint allows account administrators or the principal user themselves to view and manage user access and permissions. It provides detailed information about each authorization, including the agent user, permission levels, and validity periods. Use this endpoint when you need to audit user access, manage permissions, or review the authorization history for a specific user. The response includes pagination support for handling large sets of authorizations.
Initiate new chunked upload: Initiates a new chunked upload in DocuSign by sending the first part of the content. This endpoint is designed to handle large file uploads by breaking them into smaller, manageable pieces. It's particularly useful for adding documents to envelopes in DocuSign's electronic signature workflow. The method returns a response with the chunked upload ID, URI, and other metadata, which can be used to add more parts to the upload. Note that this API is currently in beta status and subject to change.
List Account Custom Fields: Retrieves all account-level custom fields defined for a DocuSign account. Account custom fields are envelope custom fields that can be applied across multiple envelopes, enabling account administrators to group, track, and manage envelopes consistently. The response includes two types of custom fields: - Text custom fields: Free-form text input fields - List custom fields: Dropdown fields with predefined options Each custom field contains metadata such as field ID, name, visibility settings, required status, and current values. This is useful for: - Auditing existing custom field configurations - Reviewing available custom fields before creating envelopes - Preparing for custom field updates or migrations - Understanding envelope metadata structure for reporting Note: This endpoint retrieves account-level custom field definitions, not the values set on individual envelopes. To get custom field values for a specific envelope, use the envelope custom fields endpoint instead.
List Envelope Attachments By Envelope Id: Retrieves a list of envelope attachments associated with a specified envelope in DocuSign. This endpoint is used to fetch developer-only files attached to an envelope, providing details such as attachment IDs, types, and access controls. It's important to note that this operation returns envelope attachments, which are different from signer attachments (user-visible documents). Use this endpoint when you need to manage or review administrative files linked to an envelope. The API is currently in beta status, so it may be subject to changes in future versions. The response includes an array of attachment objects, each containing information like accessControl, attachmentId, and attachmentType. Error details are provided for both successful and failed requests.
List REST API Resources: Lists available REST API v2.1 resources for DocuSign eSignature API. This endpoint provides API discovery by returning the base resources available in the DocuSign eSignature REST API v2.1. It returns a list of resource names and their corresponding API endpoint URLs, including: - accounts: Account management endpoints - billing_plans: Billing and subscription endpoints - login_information: Login and authentication info endpoints - oauth2: OAuth 2.0 authentication endpoints This is useful for understanding the API structure and available capabilities. Authentication is required and handled automatically. Note: This endpoint returns API v2.1 resources. The actual API base URL is determined from your DocuSign account configuration.
List billing invoices: Retrieves a list of billing invoices for a specified DocuSign account. This endpoint allows account administrators to fetch detailed invoice information, including total amounts, due dates, and itemized charges. It supports optional date range filtering and provides a paginated response for efficient handling of large datasets. Use this endpoint to review billing history, verify charges, or gather financial data for accounting purposes. The response includes comprehensive invoice details, making it valuable for financial reconciliation and reporting.
List brands for account: Retrieves a comprehensive list of brands associated with a DocuSign account, including default brand profiles. This endpoint provides detailed information about each brand, such as visual elements, language settings, and resource URLs for customizing various DocuSign experiences. It's particularly useful for managing and reviewing account-level branding options. The endpoint requires either the 'canSelfBrandSign' or 'canSelfBrandSend' setting to be enabled for the account. Use this when you need to audit, manage, or implement brand customizations across your DocuSign account.
List notary journals: Gets notary journals for the current user. This is a legacy endpoint that returns journal information for notaries. Use when you need to retrieve notary journal data.
List past due invoices: Retrieves a list of past due invoices for a specified DocuSign account and indicates if payment can be made through the REST API. This endpoint is designed for account administrators to manage outstanding financial obligations. It provides comprehensive invoice details including total amounts, balances, due dates, and itemized charges. Use this when you need to review overdue payments, assess the account's financial status, or determine if immediate action is required for outstanding invoices. The endpoint does not process payments directly but informs if payment through the API is possible. Note that this tool requires account administrator privileges to access sensitive billing information.
List registered notary jurisdictions: Retrieves a paginated list of registered notary jurisdictions for the current user, who must be a notary. This endpoint provides detailed information about each jurisdiction where the notary is registered, including commission details, seal settings, and supported features. It is useful for managing and reviewing a notary's registrations across multiple states. The response includes navigation URIs for handling pagination, allowing for efficient retrieval of large result sets. This endpoint should be used when a notary needs to review their registered jurisdictions or when an application needs to display or process a notary's registration information across multiple states.
List users for account: Retrieves a list of users for a specified DocuSign account. This endpoint allows for detailed querying of user information, including their account status, email addresses, and various account settings. It's particularly useful for account administrators who need to manage users or gather information about the account's user base. The endpoint supports pagination and filtering, enabling efficient retrieval of specific subsets of users. When called with the 'additional_info' parameter set to true, it provides comprehensive user data, including granular permissions and custom settings. This makes it valuable for auditing user access levels or preparing for bulk updates to user configurations. Keep in mind that the response can be quite large, especially for accounts with many users or when requesting additional info. It's recommended to use pagination parameters (count and start_position) for large accounts to manage response sizes and API performance.
List workspaces: Retrieves a list of DocuSign workspaces and their associated information for a specified account. This endpoint allows users to get a comprehensive view of all workspaces they have access to, including details such as workspace IDs, names, descriptions, creation dates, and user information. It's particularly useful for applications that need to display or manage multiple workspaces, or for auditing purposes to review workspace configurations and user access. The endpoint provides paginated results, allowing for efficient retrieval of large numbers of workspaces.
Listbulksendbatchsummaries: Retrieves a summary of bulk send batches for a DocuSign account. This endpoint allows users to query and filter bulk send batch information, providing details such as batch status, size, and processing information. It's particularly useful for monitoring the progress of large-scale document sending operations and managing bulk send workflows. The endpoint supports pagination and various filtering options to customize the result set according to specific needs.
Listcloudstorageitems: Retrieves a list of items (files and folders) from a specific folder in a cloud storage provider integrated with DocuSign. This endpoint enables browsing and searching cloud storage contents directly within DocuSign, making it easier to select documents for signing workflows. Prerequisites: - The cloud storage provider must be connected and authenticated for the user - Valid serviceId and folderId must be provided from the connected storage Supported cloud storage providers include: Box, Dropbox, Google Drive, OneDrive, Salesforce, and DocuSign Rooms. The endpoint supports pagination, sorting, and text-based filtering of results. Users can only access their own cloud storage items, ensuring data privacy and security.
Listpaymentgatewayaccountsinfo: Retrieves a list of all payment gateway accounts associated with a specific DocuSign account, along with detailed information about each account. This endpoint is useful for obtaining an overview of the payment gateways configured for an account, including their status, supported currencies, and payment methods. It should be used when you need to manage or review payment gateway configurations within a DocuSign account. As this is a beta endpoint, be aware that its structure or behavior may change in future updates.
Listsignatureprovidersforaccount: Retrieves a list of signature providers available for a specified DocuSign account. This endpoint allows users to obtain detailed information about electronic and digital signature providers, including standards-based signatures, that can be used within the account. It's particularly useful when setting up or managing signature workflows, especially those involving identity verification. The endpoint returns provider names, display names, IDs, and any required options, enabling developers to integrate various signature providers into their DocuSign-based applications or workflows.
Listworkspacefilepages: Retrieves a workspace file as rasterized pages from a DocuSign workspace. This endpoint allows users to fetch file pages as images with customizable resolution and dimensions. It supports pagination for handling large files efficiently. Use this method when you need to view or process workspace files as images, such as for preview generation or image-based analysis. The endpoint is particularly useful for viewing documents without downloading the entire file, enabling faster loading and reduced bandwidth usage. Note that this method does not provide text extraction or document editing capabilities; it's purely for image-based representation of file pages.
Lock Template for Editing: Locks a specified DocuSign template for editing to prevent concurrent modifications. This endpoint acquires an exclusive lock on a template, ensuring that only the lock holder can make changes during the lock period. The response includes a lockToken that must be included in the X-DocuSign-Edit header for all subsequent update operations on the locked template. Key features: - Returns a lockToken for exclusive editing access - Prevents race conditions in collaborative environments - Lock automatically expires after the specified duration - Default lock duration is typically 300 seconds (5 minutes) Use this action before modifying a template to ensure data integrity and prevent conflicts with other users attempting to edit the same template simultaneously.
Lock an envelope for editing: This endpoint locks an envelope for editing, preventing other users or recipients from changing it. It's used to ensure exclusive access to an envelope during updates. The method returns a lock token that must be included in subsequent PUT requests to modify the locked envelope. Use this endpoint when you need to make changes to an envelope and want to prevent concurrent edits. The lock has a limited duration and can be extended if needed. It's particularly useful for complex envelope modifications or when coordinating changes among multiple users. Note that template passwords may be required for certain locked envelopes, and there's a maximum lock duration of 30 minutes.
Modify Account Notification Settings: Updates the default email notification settings for envelope senders and signers in a DocuSign account. This endpoint allows customization of when and what type of notifications users receive regarding envelope status changes (e.g., signed, declined, completed), comments, and other events. Use this action when you need to: - Configure when senders receive notifications (e.g., when signers change, delivery fails) - Configure when signers receive notifications (e.g., envelope activation, completion) - Set comment notification preferences - Update notification settings for specific events like document purges or offline signing Note: These are account-level default settings. Individual envelope notification settings can override these defaults when sending specific envelopes.
Modify tab settings for account: This endpoint modifies the tab types and tab functionality that are enabled for a DocuSign account. It allows administrators to configure various tab-related settings, such as enabling or disabling specific tab types, controlling tab order, and managing compliance with FDA regulations. The endpoint is primarily used to customize the tab experience for users within an account, affecting how they interact with documents during the signing process.
Post payment to invoice: Posts a payment to past due invoices for a DocuSign account. This action applies a payment amount to settle outstanding invoice balances and creates a payment transaction record. Before using this action, retrieve past due invoice information using the 'List Past Due Invoices' action to get the total balance due and verify that 'paymentAllowed' is true. The payment amount must exactly match the 'pastDueBalance' value from that response. This action requires account administrator privileges and the 'billing:write' OAuth scope. It is only available for production accounts with billing features enabled - demo accounts will return a 400 Bad Request error with 'BILLING_PLAN_ERROR' indicating the payment manager is blocked. Use this when you need to programmatically settle overdue DocuSign account invoices through the REST API.
Purchase additional envelopes: This endpoint completes the purchase of additional envelopes for a DocuSign account through an internal workflow interaction with an envelope vendor. It is designed to handle the financial transaction and update the account's envelope quota. This tool should be used when there's a need to increase the number of available envelopes for document signing within a DocuSign account. However, it's important to note that this endpoint is currently limited to DocuSign internal use only and is not available for public API consumers. The endpoint requires detailed information about the purchase, including the amount, currency, quantity, and app store-related data for tracking and processing the transaction.
Queue downgrade billing plan request: Queues a downgrade request for a DocuSign account's billing plan. This action initiates the process of changing an account to a lower-tier or less expensive billing plan without immediately applying the change. Use this action when an account administrator needs to: - Downgrade from a paid plan to a free or lower-tier plan - Reduce subscription costs by moving to a plan with fewer features - Apply promotional pricing or discounts during the downgrade The downgrade is queued for processing and typically takes effect at the end of the current billing period. The response includes the new plan details, effective date, and remaining days in the current billing cycle. Note that billing plan management operations typically require administrator-level permissions and may not be available on demo or restricted accounts.
Registercurrentuserasnotary: This endpoint registers the current user as a notary in DocuSign, enabling remote online notarization capabilities. It configures the user's notary profile, settings, and permissions. Use this when setting up a new notary within the DocuSign system. Note that this does not replace legal notary certification requirements.
Remove Templates From Favorites: Removes one or more templates from an account's list of favorite templates in DocuSign. This endpoint allows users to manage their favorite templates by specifying which templates should no longer be marked as favorites. It accepts an account identifier and a list of template IDs to be removed from favorites. The API returns information about the templates that were successfully removed and any errors encountered during the process. This endpoint is particularly useful for maintaining an organized and relevant list of favorite templates, especially when templates are no longer frequently used or needed. Note that this API is currently in beta status, which means it may not be fully stable and could be subject to changes in the future.
Remove bulk send list: This endpoint deletes a specific bulk send list from a DocuSign account. It is used to permanently remove a bulk send list that is no longer needed or was created in error. The operation requires both the account identifier and the specific bulk send list ID to ensure precise targeting of the list to be deleted. Upon successful deletion, it returns a summary of the remaining bulk send lists associated with the account. This endpoint should be used with caution as the deletion is irreversible. It's particularly useful for maintaining a clean and organized set of bulk send lists, especially in environments where list management is crucial for compliance or efficiency reasons. Note that this operation does not affect any envelopes that may have already been sent using the deleted list.
Remove user signature information: Removes the signature information for a specific user in DocuSign. This endpoint should be used when a user wants to delete their existing signature from their DocuSign account. It's particularly useful for updating or refreshing signature information. The operation is restricted to the authenticated user's own signatures and cannot be used to modify other users' data, even with admin rights. It's important to note that this action is irreversible, so it should be used with caution. The endpoint accepts either a signature ID or a signature name, but using the signature ID is recommended to avoid URL encoding issues.
Removegroupsharingpermissionsfortemplate: Removes sharing permissions for specified member groups from a DocuSign template. This endpoint is used to revoke access to a template for one or more groups, enhancing template security and access control. It's particularly useful when reorganizing team structures, updating project access, or when certain groups no longer require access to a specific template. The operation affects only the specified template and groups, allowing for granular permission management within the DocuSign environment.
Republish connect data for envelope: Republishes Connect information for a specified envelope in DocuSign. This endpoint is used to retry sending Connect event data that may have failed to deliver previously. It's particularly useful for ensuring that all relevant updates about an envelope are successfully communicated to integrated systems. The function requires account administrator privileges and Connect must be enabled on the account. Use this when you need to manually trigger a resend of Connect data for a specific envelope, typically in response to failed deliveries or system synchronization issues.
Republish connect info for envelopes: Republishes Connect webhook information for multiple DocuSign envelopes. Queues envelopes for Connect webhook republishing to retry failed webhook deliveries. When DocuSign Connect fails to deliver webhook events to your endpoint, envelopes are added to a failure queue. This action manually triggers republishing attempts. Use cases: Retry webhook delivery after temporary endpoint issues, resend envelope events after fixing your webhook endpoint, or recover from missed notifications. Note: Only envelopes in the Connect failure queue can be republished. Envelopes not in the failure queue return status 'Fail' with 'Envelope Id not found in failure queue' (expected behavior). Use Connect failure logs API to identify envelopes needing republishing. Requires: Connect enabled on account, administrator access with connect:read and connect:write scopes.
Retrieve Account Billing Plan: Retrieves detailed billing plan information for a specified DocuSign account. This endpoint provides comprehensive data about the current billing plan, successor plans, billing address, and credit card information associated with the account. It is particularly useful for obtaining an overview of an account's billing status, available plan options, and payment details. The endpoint allows customization of the response through optional query parameters, enabling users to include or exclude specific information such as credit card details, downgrade options, metadata, and successor plans. This tool should be used when a detailed view of an account's billing configuration is required, especially for account management, billing inquiries, or planning potential plan changes.
Retrieve Account Envelope Purge Config: Retrieves the current envelope purge configuration for a specified DocuSign account. This endpoint allows account administrators to view the settings that control how and when documents are permanently removed from completed and voided envelopes after a specified retention period. It provides crucial information for managing document lifecycle, data privacy, and storage optimization within the DocuSign platform. The configuration includes settings for enabling purging, redacting personally identifiable information (PII), removing associated tabs and attachments, and specifying the retention period in days. This method should be used when auditing or reviewing an account's document retention policies, or before making changes to the purge configuration. Note that this endpoint is in beta status and requires account administrator privileges to access.
Retrieve Account Favorite Templates: Retrieves the list of favorite templates for a DocuSign account. Returns an array of template IDs and the dates they were marked as favorites. This is useful for identifying which templates a user has marked for quick access. Note: This endpoint only returns template IDs and favorited dates, not the full template details. Use the List All Templates or Get Template actions to retrieve complete template information. Beta API: May be subject to changes in future versions.
Retrieve Account Password Rules: Retrieves the current password rules and security settings for a specified DocuSign account. This endpoint provides detailed information about password expiration policies, lockout durations, password strength requirements, and security question configurations. It is useful for account administrators to review and understand the current security posture of their DocuSign account. The retrieved information can be used to ensure compliance with organizational security policies or to plan password policy updates. **Important**: This endpoint requires administrator privileges. The access token must come from a user with administrator permissions, as these settings are account-wide. Standard users will receive a 401 Unauthorized error. This endpoint does not modify any settings; it is for informational purposes only. For actually changing or updating password rules, use the update password rules endpoint instead.
Retrieve Account Provisioning Info: Retrieves the account provisioning information for a DocuSign account. This endpoint returns crucial setup and configuration details including default connection IDs, billing plan identifiers, distributor codes, password policy rules, and promotional information. Use this action when you need to: - Verify account provisioning configuration - Retrieve default billing plan information - Check password policy requirements - Get distributor-related settings The account ID is automatically populated from your authentication credentials. This is a read-only endpoint that retrieves configuration data without making any modifications to the account. Returns provisioning details such as defaultConnectionId, defaultPlanId, distributorCode, passwordRuleText, and planPromotionText.
Retrieve Account Seal Providers: Retrieves electronic seal providers (eSeals) available for a DocuSign account. Electronic seals certify document origin and integrity using a legal entity identity rather than an individual signature. Returns seal identifiers and names for all configured seals in the account. Use this to display available seal options or implement automated seal application workflows. IMPORTANT: Electronic Seals is a premium feature requiring provisioning by DocuSign Sales. Not available in standard developer sandboxes. A 401 error indicates the feature is not enabled. Contact DocuSign Sales to enable. Note: This retrieves seal information only; applying seals requires separate API calls.
Retrieve Billing Plan Details: Retrieves comprehensive billing plan information for a DocuSign account, including plan details, billing address, payment information, and available upgrade options (successor plans). **Use Cases:** - Review current billing plan and pricing details - Analyze costs for budgeting and financial planning - Identify available upgrade paths - Audit billing and payment information - Generate billing reports with detailed plan data **Returns:** Plan details (name, ID, pricing), billing address, credit card info (masked), successor plans, payment processor info, and referral/discount details. **Note:** Requires admin privileges. Read-only operation. Account ID auto-populated if not specified.
Retrieve Connect OAuth Configuration: Retrieves the Connect OAuth configuration for a specified DocuSign account. This endpoint allows account administrators to access the OAuth settings used for DocuSign Connect, which is crucial for webhook integrations and automated notifications. The retrieved configuration includes essential details such as the authorization server URL, client ID, client secret, and scope settings. This tool should be used when setting up or troubleshooting Connect integrations, or when verifying the current OAuth configuration for an account. It's important to note that this endpoint requires account administrator privileges and Connect must be enabled on the account to access this information. The tool does not modify any settings; it only retrieves the existing configuration.
Retrieve Credit Card Info: This endpoint retrieves detailed credit card information associated with a specific DocuSign account. It provides comprehensive details about the credit card on file, including the card number (partially masked), type, expiration date, cardholder name, and associated billing address. This tool should be used when there's a need to access or verify the current credit card information for billing purposes within the DocuSign system. It's particularly useful for account management, billing inquiries, or updating payment information. However, due to the sensitive nature of the data returned, this endpoint should be used judiciously and with appropriate security measures in place. The tool does not allow for updating or modifying the credit card information; it is read-only. Be aware that accessing this information may be subject to strict access controls and compliance requirements due to the sensitive financial data involved.
Retrieve Envelope Attachment: Downloads a developer-only envelope attachment file from a DocuSign envelope. This retrieves attachments that were added programmatically to an envelope (not signer attachments). These are files associated with the envelope that are only accessible via the API and not visible to signers in the DocuSign UI. The attachment is returned as a downloadable file that can be saved or processed. To get the attachmentId, first use the "List Envelope Attachments" action. Note: This endpoint is currently in beta and may undergo changes.
Retrieve Envelope Audit Events: Retrieves the audit events for a specified envelope in DocuSign. This endpoint allows users to access a detailed history of all actions and changes made to a particular envelope, providing a comprehensive audit trail. It is particularly useful for compliance, security, and tracking purposes, allowing users to monitor the lifecycle of important documents. The endpoint should be used when detailed information about an envelope's history is required, such as verifying signatures, tracking changes, or investigating discrepancies. Note that this endpoint only provides audit events for a single envelope at a time and does not offer filtering or sorting options for the returned events.
Retrieve Envelope Document Fields: Retrieves custom document field information from an existing envelope document in DocuSign. This endpoint allows users to access name-value pairs of custom data strings associated with a specific document within an envelope. It's particularly useful for retrieving metadata or additional information attached to documents that are not used in DocuSign's standard processing. The function returns both current and original values of these custom fields, enabling tracking of any changes made to the fields over time.
Retrieve Envelope Document HTML Definition: Retrieves the original HTML definition used to generate the responsive HTML for a specific document within an envelope in a DocuSign account. This endpoint is crucial for developers working with DocuSign's responsive signing feature, as it provides detailed information about how the document is formatted and displayed in a responsive manner. The tool returns properties that define the responsive HTML generation, including display anchors, collapsible sections, and responsive table settings. Use this when you need to inspect or troubleshoot the HTML definition of a document in an envelope, particularly for documents using smart sections or responsive signing features. This endpoint does not modify any data and is purely for retrieval purposes.
Retrieve Envelope Email Overrides: Retrieves custom email settings for a specific DocuSign envelope. Use this action to get the envelope-specific email configuration overrides including: - Reply-to email address and display name - BCC email addresses for archiving (up to 5 addresses) These settings override the account-level defaults for this specific envelope only. **Important:** This information is NOT included in standard envelope status requests (GET /envelopes/{envelopeId}), so you must use this dedicated endpoint to retrieve email override settings. **Use cases:** - Verify custom reply-to addresses set for specific envelopes - Audit BCC configuration for compliance/archiving purposes - Troubleshoot email delivery issues by checking envelope-specific overrides
Retrieve Envelope Notification Details: Retrieves the notification, reminder, and expiration settings for an existing envelope in DocuSign. This endpoint allows developers to access and review the current notification configuration for a specific envelope, including expiration timelines and reminder schedules. It's particularly useful when you need to verify or audit the notification settings for an envelope, especially in workflows where timely responses are critical. The endpoint does not modify any settings; it only provides read-only access to the current configuration.
Retrieve HTML Definition for Responsive Document: This endpoint retrieves the HTML definition used to generate a dynamically sized responsive document within a DocuSign envelope. It is specifically designed for documents created as signable HTML and provides detailed information about responsive signing and smart sections. The endpoint returns properties that define how to generate the responsive-formatted HTML for the document, including display settings, anchors, and styling options. It's particularly useful when implementing responsive signing across different devices or customizing the appearance of HTML documents in the signing process. Note that for non-HTML documents or invalid document IDs, the endpoint will return a 200 OK response with an empty JSON body, rather than an error.
Retrieve REST API versions: Retrieves the available REST API versions for DocuSign's service. Returns a list of available API versions (v1, v2, v2.1) with their endpoint URLs, the current build version string, and linked DocuSign sites. This diagnostic endpoint is useful for checking API compatibility, version availability, and system status. The response includes serviceVersions (array of version and versionUrl), buildVersion (internal build identifier), and linkedSites (array of DocuSign domain URLs). Authentication is required to access this endpoint.
Retrieve Template Document Page Images: Retrieves and returns images of pages from a specified template document in DocuSign. This endpoint allows users to fetch visual representations of template pages with customizable image properties such as resolution and dimensions. It's particularly useful for previewing or displaying template content within applications, enabling users to view document layouts and content without needing to download the entire document. The endpoint supports pagination for efficient handling of multi-page documents and offers options for showing changes and bypassing cache for up-to-date results.
Retrieve User Profile Image: Retrieves the user profile picture for a specified user within a DocuSign account. This endpoint allows users to fetch their own profile image, which is returned in the same format as it was originally uploaded. It's particularly useful for applications that need to display user avatars or profile pictures within the DocuSign ecosystem. The endpoint ensures that users can only access their own profile image, maintaining privacy and security. If no profile image exists for the user, the endpoint will indicate this with a 404 Not Found response.
Retrieve billing invoice: Retrieves a specific billing invoice for a DocuSign account, providing detailed information about charges and payment details. This endpoint allows account administrators to access invoice data in both JSON format and, when available, as a downloadable PDF. It's particularly useful for financial reconciliation, audit purposes, or when detailed billing information is required. The endpoint returns comprehensive invoice data, including total amount, balance, due date, and itemized charges, with amounts shown in the account's set currency.
Retrieve billing payment info: Retrieves detailed information for a specific billing payment in a DocuSign account. Returns payment details including ID, number, amount, description, and date. Useful for auditing, reconciliation, and reviewing payment records. **Production Account Required:** This endpoint ONLY works with production accounts that have billing features enabled. Demo/developer accounts will return 400 Bad Request errors. **Requirements:** Production account with billing features, account administrator privileges, OAuth scope: signature or billing:read. **To get payment ID:** Call 'Retrieve payment information list' to see available payments, or 'Post payment to invoice' to create a payment that returns its ID.
Retrieve chunked upload metadata: Retrieves metadata for a specific chunked upload in DocuSign. This endpoint allows users to check the status, parts, and other details of a large file upload that has been split into chunks. It's particularly useful for verifying the integrity and completeness of an upload before committing it for use in other DocuSign operations, such as adding documents to envelopes. The endpoint does not return the actual content of the upload, only its metadata. It cannot retrieve information about expired, deleted, or already consumed chunked uploads. This tool is essential for managing and troubleshooting large file uploads in DocuSign, ensuring that all parts are present and the upload is ready for use.
Retrieve cloud storage provider configuration: Retrieves the list of cloud storage providers enabled for a specific user in a DocuSign account, along with their configuration information. This endpoint is essential for integrating external cloud storage services with DocuSign, allowing users to access and manage documents from various providers. It provides details such as authentication URLs and service IDs for each enabled provider. Use this endpoint when you need to display available cloud storage options to a user or initiate the authentication process for a specific provider. Note that users can only access their own cloud storage information, and the endpoint does not modify any existing configurations.
Retrieve connect failure logs: Retrieves the Connect failure log information for a specified DocuSign account. This endpoint is specifically designed for account administrators to identify which envelopes failed to post during Connect events. It provides detailed information about each failure, including error messages, retry counts, and URIs for potential republishing attempts. The endpoint supports optional date range filtering to narrow down the search results. Use this method when troubleshooting Connect integration issues or when you need to analyze and potentially retry failed envelope postings. Note that Connect must be enabled on the account for this endpoint to function properly.
Retrieve connect log entry: Retrieves a specific Connect log entry for a DocuSign account. This endpoint provides detailed information about a Connect event, including account details, configuration information, envelope data, and potential error details. It is particularly useful for troubleshooting Connect integrations, auditing Connect events, and monitoring the overall health of your Connect service. The endpoint requires Connect to be enabled on the account and logging to be activated in the Connect configuration. Only account administrators can access this information.
Retrieve connect logs: Retrieves the 100 most recent Connect log entries for a specified DocuSign account. This endpoint is essential for monitoring and troubleshooting DocuSign Connect integrations, providing detailed information about both successful and failed Connect events. It allows administrators to review recent activities, identify issues, and ensure proper functioning of their Connect configurations. The endpoint supports date-based filtering to narrow down the log entries within a specific time range. Note that this endpoint requires administrator access and Connect must be enabled on the account with logging turned on. Log entries are only retained for 15 days.
Retrieve custom fields for envelope: Retrieves custom field metadata for a specified envelope. Custom fields are additional data points attached to envelopes that are NOT visible to document recipients. They're used for: - Organizing and categorizing envelopes internally - Tracking workflow stages or approval statuses - Storing reference IDs for integration with other systems (CRM, ERP, etc.) - Filtering and searching envelopes in reports Returns two types of custom fields: 1. List fields: Fields with predefined dropdown options 2. Text fields: Free-form text fields for custom values Supports Salesforce merge fields for CRM integrations. The fields returned are set at envelope creation or modification time and remain with the envelope for its entire lifecycle.
Retrieve default disclosure for envelope: Retrieves the default HTML-formatted Electronic Record and Signature Disclosure (ERSD) for a specified envelope in DocuSign. This endpoint is used to obtain the standard disclosure text that recipients must agree to before signing documents electronically. It is particularly useful for retrieving language-specific versions of the disclosure and for ensuring compliance with electronic signature regulations.
Retrieve payment information list: Retrieves a list of payment information for a specific DocuSign account. This endpoint allows you to fetch detailed payment data, including amounts, descriptions, payment dates, and IDs. It's particularly useful for accounting purposes, reconciliation, or generating financial reports. By default, it returns payment information for the last 365 days, but you can specify a custom date range using query parameters. The response is paginated, allowing you to handle large datasets efficiently. Note that this endpoint requires account administrator privileges and should be used cautiously to protect sensitive financial information.
Retrieve pdf from specified template: Retrieves one or more PDF documents from a specified DocuSign template. This endpoint allows you to fetch individual documents or combine all documents in the template into a single PDF file. It's particularly useful when you need to access template documents for review, processing, or to create new envelopes based on existing templates. The retrieved PDFs can be customized to show recipient changes and can be encrypted for enhanced security. Use this endpoint when you need to work with template documents outside of the DocuSign system or when you want to verify the content of a template before using it.
Retrieve signer signature image information: Retrieves the specified user's signature image from a DocuSign envelope. This endpoint allows developers to access the electronic signature image of a specific recipient within an envelope, which can be useful for verification, display, or record-keeping purposes. The image is returned in its original uploaded format, with an option to include or exclude the chrome (added line and identifier around the initial image). This tool is particularly useful when you need to extract or display a user's signature from a completed or in-progress DocuSign transaction. It should be used cautiously, respecting privacy concerns and ensuring proper authorization. Note that older envelopes may only have chromed images available, so a fallback strategy might be necessary in some cases.
Retrieve template page image: Retrieves a specific page image from a template document for display purposes. This endpoint is part of the DocuSign Templates API and allows developers to fetch and display individual pages from template documents. It's particularly useful when you need to preview or display a specific page of a template without retrieving the entire document. The endpoint supports customization of the returned image through resolution (DPI) and dimension parameters, enabling optimized image delivery for various display requirements. It should be used when building interfaces that require visual representation of template pages, such as template preview features or document review systems. Note that this endpoint retrieves static images and does not provide interactive elements or real-time template modifications.
Retrieve user account settings: Retrieves a comprehensive list of account settings and email notification preferences for a specified user within a DocuSign account. This endpoint provides detailed information about the user's configuration, including locale settings, email notification preferences, account management capabilities, and various other user-specific settings. It's particularly useful for understanding a user's current configuration or for troubleshooting user-specific issues. The endpoint is limited to retrieving settings for the authenticated user only, even for admin users, ensuring privacy and security of individual user settings. The response includes a wide range of settings, from basic preferences to advanced features like vaulting and template management, offering a complete view of the user's DocuSign environment configuration.
Retrieve user initials image for envelopes: Retrieves the initials image that a recipient used when signing a DocuSign envelope. This endpoint allows you to fetch the recipient's initials image in its original format (GIF, PNG, JPEG, or BMP), with an option to include or exclude the chrome (added line and identifier around the image). The initials image is only available after the recipient has signed the envelope and used initials on the document. If the recipient hasn't signed yet or didn't use initials, the API will return a 404 error. This is particularly useful when you need to display or audit the actual initials that were stamped on documents during the signing process. Note that for older envelopes, only chromed images might be available.
Retrieve user profile information: This endpoint retrieves comprehensive user profile information for a specified user within a DocuSign account. It provides detailed data about the user's personal information, settings, preferences, and permissions. The endpoint is particularly useful for obtaining an in-depth view of a user's configuration within the DocuSign system, including their authentication methods, email notification settings, and locale preferences. It should be used when detailed user information is required for account management, user customization, or auditing purposes. Note that users can only access their own information, and the userId parameter must match the authenticated user's ID. The endpoint does not allow for modification of user settings; it is strictly for retrieval of existing information.
Retrieve user signature definitions: This endpoint retrieves the signature definitions for a specified user within a DocuSign account. It allows users to access their own signature information, including details about signature images, stamps, and associated metadata. The endpoint is useful for applications that need to display or manage user signatures within the DocuSign ecosystem. It supports retrieving different types of signatures based on the optional stamp_type parameter. The response includes comprehensive information about each signature, such as creation date, image data, and various properties related to the signature's appearance and usage.
Retrieve user signature information: This endpoint retrieves the detailed structure and information of a single user signature within a DocuSign account. It provides comprehensive details about the signature, including its creation date, image URIs, stamp properties, and associated rights. The endpoint is designed for users to access and review their own signature information, ensuring data privacy and security. It's particularly useful when users need to verify their signature settings or retrieve signature images for use in other contexts.
Retrieveaccountbrandinformation: Retrieves detailed information about a specific brand associated with a DocuSign account. This endpoint allows users to access comprehensive brand settings, including company name, languages, colors, logos, and resource URLs for customizing various DocuSign experiences such as email, sending, and signing. It should be used when detailed brand information is needed for display, management, or customization purposes. The endpoint requires account branding to be enabled (either for signing, sending, or both) to function properly.
Retrieveaccountinformationforspecifiedaccount: Retrieves comprehensive information for a specified DocuSign account, including account details, billing information, plan specifics, and optionally detailed account settings. This endpoint is used to gather extensive data about an account's configuration, status, and capabilities within the DocuSign platform. It's particularly useful for account management, auditing, or when needing to review or update account settings. The response includes critical information such as the account's GUID, name, creation date, current plan details, and various feature enablements. When account settings are included, it provides a deep dive into the account's configuration, covering aspects like authentication requirements, branding options, envelope settings, and compliance-related configurations.
Retrieveaccountsettingsinformation: Retrieves the comprehensive account settings information for a specified DocuSign account. This endpoint provides a detailed view of the account's configuration, including access code formats, account-wide preferences, feature toggles, security settings, UI customization options, and compliance-related configurations. It is particularly useful for administrators or integration developers who need to audit, review, or programmatically access the full range of account settings. The retrieved information can be used to understand the current state of the account, verify specific configurations, or as a basis for updating settings through other API calls. Note that this endpoint returns a large amount of data and should be used judiciously to avoid unnecessary load on the system. It does not modify any settings; it only retrieves the current configuration.
Retrieveaccountsigninggroups: Retrieves a comprehensive list of all signing groups within a specified DocuSign account. This endpoint allows you to obtain detailed information about each signing group, including group names, types, IDs, and optionally, member details. It's particularly useful for managing and auditing signing groups across an organization. The endpoint supports filtering by group type and can include or exclude user information based on your needs. Use this when you need to review, manage, or audit the signing groups in your DocuSign account. Note that while it provides extensive group information, it does not modify any group settings or memberships.
Retrieveaccountverificationworkflows: Retrieves a list of Identity Verification workflows available for a DocuSign account. This endpoint allows account administrators or senders to fetch details about the verification methods that can be applied to signers during the document signing process. It provides information about active, deactivated, or all workflows, depending on the query parameter. Use this endpoint to understand the available identity verification options for your account, which can help in implementing secure signing processes.
Retrieveallaccounttabs: Retrieves a comprehensive list of all tabs associated with a specified DocuSign account. It returns detailed information about each tab, including type, label, validation rules, and formatting settings. Use this endpoint for auditing tab configurations, managing account-wide tab settings, or integrating tab information into external systems. Can be filtered to return only custom tabs if needed.
Retrieveapirequestlogfiles: Retrieves a list of API request log entries from DocuSign, providing diagnostic information for developers. Offers flexible response formats (JSON, XML, or zip file). Returns key data about each API request, including timestamps, endpoints called, and request status. Useful for troubleshooting, monitoring, and auditing API usage. Note: May not provide real-time logs and time range of returned logs is unspecified.
Retrieveavailableaccountstamps: Retrieves a list of stamps available in a DocuSign account. This endpoint allows users to fetch detailed information about various types of stamps, signatures, and related properties associated with the specified account. It's particularly useful for applications that need to display or manage available stamps for document signing processes. The endpoint returns comprehensive data including adoption dates, creation dates, image URIs, and specific properties of each stamp or signature. Use this when you need to present users with stamp options or when managing stamp resources within a DocuSign integration.
Retrieveconnectconfigurationdetails: Retrieves detailed information for a specific DocuSign Connect configuration. This endpoint allows account administrators to access and review the settings of a custom Connect configuration, including event triggers, delivery modes, and integration details. It's particularly useful for auditing existing configurations or gathering information before making updates. The endpoint requires Connect to be enabled on the account and is limited to account administrators only.
Retrieveconnectconfigurations: Retrieves all Docusign Custom Connect definitions for a specified account. This endpoint allows account administrators to fetch detailed information about existing Connect configurations, including webhook settings, event triggers, and delivery modes. It provides a comprehensive view of how the account is set up to send notifications for various Docusign events. This tool is essential for managing and auditing Connect integrations, but should only be used by authorized account administrators with Connect enabled on their account.
Retrievecustomfieldsfortemplate: This endpoint retrieves the custom document fields for an existing template document in DocuSign. It allows users to access name-value pairs of custom data strings associated with a specific document within a template. This tool is useful for retrieving metadata or custom information that has been added to template documents, which can be used for populating or customizing new envelopes based on the template. It should be used when you need to view or work with the custom fields of a particular document in a DocuSign template. Note that this endpoint only retrieves existing custom fields and does not allow for creation or modification of these fields.
Retrievecustomtabinformation: Retrieves detailed information about a specific custom tab associated with a DocuSign account. This endpoint allows users to access the properties and settings of a custom tab, including its anchor information, formatting options, merge field details, and locale settings. It is particularly useful when you need to review or verify the configuration of a custom tab within an account. The endpoint requires both the account ID and the specific custom tab ID to fetch the relevant information. Note that this endpoint only retrieves information and does not modify any existing custom tab settings.
Retrievecustomusersettings: Retrieves a list of custom user settings for a single user in DocuSign. This endpoint allows flexible storage and retrieval of user-specific information that can be used in your own system, separate from standard user account settings. It supports both grouped and ungrouped custom settings, with the ability to filter by group using an optional header. Use this endpoint when you need to access user-specific configurations, preferences, or any custom data stored for a particular user in your DocuSign integration. Note that users can only access their own custom settings, and this endpoint does not provide access to standard DocuSign account settings.
Retrieveenvelopedocuments: Retrieves one or more documents from a DocuSign envelope. This endpoint allows users to fetch a single document, all documents combined, or specific document sets in various formats (PDF, ZIP, PDF portfolio). It's particularly useful for accessing signed documents, certificates of completion, or entire envelope contents. The endpoint offers flexibility in document retrieval, supporting features like language customization, watermarking, and data change highlighting. Use this when you need to download or access documents after they've been processed through DocuSign's electronic signature workflow.
Retrieveitemsincloudstoragefolder: Retrieves a list of items (files and folders) from a specified folder in an integrated cloud storage provider. This endpoint allows users to browse and search their cloud storage contents directly within the DocuSign application, facilitating document selection for e-signature workflows. It supports pagination, sorting, and filtering options to efficiently manage large folders. Use this endpoint when you need to list, locate, or select files from a user's cloud storage for DocuSign operations. Note that this endpoint only provides metadata about the items and does not download the actual file contents.
Retrievelistofbillingplans: Retrieves a comprehensive list of billing plans associated with a distributor in the DocuSign system. This endpoint provides detailed information about each billing plan, including plan names, IDs, payment cycles, methods, and pricing details in various currencies. It is particularly useful for administrators or financial teams who need to review or manage billing options for their organization. The endpoint returns all available plans without requiring any input parameters, making it ideal for generating a complete overview of billing options. Note that some fields in the response are reserved for DocuSign internal use and may not be relevant for all users.
Retrievepowerformdataentries: This endpoint retrieves data entries for a specific PowerForm within a DocuSign account. It allows PowerForm Administrators or the PowerForm sender to download the information entered by recipients into a PowerForm. The data can be retrieved in various formats (JSON, XML, or CSV) and can be filtered by date range. This endpoint is essential for collecting and analyzing form submissions, enabling businesses to efficiently process and manage data gathered through PowerForms. It should be used when there's a need to extract and analyze PowerForm submission data, but not for real-time form submission tracking. The endpoint provides comprehensive form data, including envelope and recipient details, but does not offer real-time updates or notifications for new submissions.
Retrievepropertiesaboutworkspace: Retrieves detailed properties and information about a specific DocuSign workspace. This endpoint allows you to fetch comprehensive data about a workspace, including its settings, user details, and various metadata. It's particularly useful when you need to access or verify workspace information, such as its current status, description, or associated users. The endpoint requires both an account identifier and the specific workspace ID to retrieve the correct information. Note that some details, like caller information, are only returned for user-specific GET calls. This endpoint should be used when detailed workspace information is needed, but it does not provide document contents or allow modifications to the workspace.
Retrieveshareditemstatusforusers: Retrieves shared item status for one or more users and types of items within a DocuSign account. This endpoint provides detailed information about how envelopes, templates, and folders are shared among users and groups. It can be used to audit sharing permissions, track shared resources, or gather information for access management. The endpoint offers various filtering options to customize the response based on item types, user statuses, and sharing directions. Note that this endpoint returns information for the legacy Shared Envelopes feature; for the new Shared Access feature, use the Authorizations resource instead.
Retrievetemplatecustomfields: Retrieves the custom document field information from an existing template in DocuSign. This endpoint allows users to fetch both list and text custom fields associated with a specific template. It's particularly useful when you need to view or work with the custom fields that have been set up for a template, enabling you to understand the additional data that can be collected or pre-filled when using this template to create envelopes. The retrieved information includes details such as field IDs, names, required status, and possible values for list fields. This endpoint should be used when you need to inspect or validate the custom fields of a template before using it to create an envelope or when you want to display the available custom fields to users in your application.
Retrieveusersignatureimage: Retrieves a specified user's signature or initials image from DocuSign. This endpoint allows you to fetch the image in its original upload format, with an option to include or exclude the chrome (frame) around the image. It's useful for applications that need to display or process user signatures. The endpoint requires specific user authentication and is limited to retrieving the authenticated user's own signature images. It supports various image types including stamps, signatures, and initials, making it versatile for different signature requirements in document workflows.
Retrieveworkflowstepfortemplate: Retrieves detailed information about a specific workflow step for a DocuSign template. This endpoint allows users to access the configuration and status of a single step within a template's workflow, including delayed routing settings and conditional recipient rules. It's particularly useful for monitoring the progress of complex, multi-step template processes or for troubleshooting issues with specific workflow steps. The endpoint provides read-only access to step details and should be used when you need to inspect or verify the current state and rules of a particular workflow step within a template. Note that this endpoint does not allow modification of the workflow step; it is for retrieval purposes only.
Return Brand Resource Metadata For Account: Retrieves metadata about the branding resources associated with a specific DocuSign account and brand. This endpoint returns detailed information about various brand resource types, including those used for sending, signing, email, and captive (embedded) signing experiences. It's particularly useful for developers who need to inspect or manage custom branding elements within a DocuSign integration. The endpoint should be used when you need to audit brand resources, prepare for updates, or gather information about the current branding configuration. Note that this endpoint only returns metadata and URIs for the resources, not the actual resource content. Also, branding must be enabled for the account (either for signing, sending, or both) for this endpoint to return meaningful data.
Return Envelope Tab Data For Existing Envelope: Retrieves detailed form data from a DocuSign envelope, including the current values of form fields, recipient information, and envelope status. This endpoint is used to download envelope and tab data from in-process, completed, or canceled envelopes that the user has sent or that are shared with them. It's particularly useful for analyzing form submissions, tracking recipient interactions, and integrating DocuSign data with external systems. The method requires the "Allow sender to download form data" setting to be enabled for the account.
Return Template Workflow Definition: Retrieves the workflow definition for a specified DocuSign template. This endpoint returns detailed information about the template's workflow, including scheduled sending settings, workflow status, and individual workflow steps. It's useful for understanding and managing the automated process flow of a template. The endpoint should be used when you need to examine or troubleshoot a template's workflow configuration. Note that if the specified template does not have a workflow object, this method will return a 404 error. The response includes comprehensive data about the workflow, but does not modify the template or its workflow in any way.
Return all connect service users: Retrieves all users from the configured Connect service for a specific DocuSign account and Connect configuration. This endpoint allows account administrators to fetch user information, including email addresses, user IDs, and inclusion status in the Connect service. It supports filtering by email, username, and status, as well as pagination for large result sets. This tool should be used when you need to obtain a comprehensive list of users associated with a particular Connect configuration, which is useful for auditing, user management, or integration purposes. Note that this endpoint requires Connect to be enabled on the account and can only be accessed by account administrators.
Return users from connect service: Retrieves users associated with a specific DocuSign Connect configuration. This endpoint returns information about which users are linked to a Connect configuration, indicating either that all users are selected (allUsersSelected) or providing a list of specific users. Connect configurations define webhook settings for receiving real-time event notifications from DocuSign. The response indicates user selection for the Connect configuration: - When allUsersSelected is "True", the configuration applies to all account users - When specific users are configured, they are returned in the users array - Supports pagination for large user lists via count and start_position parameters Requires account administrator privileges and an active Connect configuration.
Returns document page images based on input: Retrieves images of document pages from a specific envelope in a DocuSign account. This endpoint allows users to fetch page images with customizable parameters such as resolution (DPI), image dimensions, and pagination options. It's particularly useful when you need to display or process document pages without downloading the entire document. The endpoint supports showing changes made to the document and can bypass caching for the most up-to-date images. It's ideal for applications that need to render document previews, perform image analysis, or create custom document viewers.
Revokeenvelopecorrectionurl: This endpoint revokes the correction view URL for a specific envelope in DocuSign, effectively disabling the ability to make further corrections to the envelope. It should be used when you want to prevent any additional modifications to an envelope that was previously available for correction. This is particularly useful in scenarios where the correction period has ended or when you need to lock an envelope's content for compliance or business process reasons. The endpoint requires the account ID and envelope ID to identify the specific envelope for which the correction view should be revoked. It's important to note that once revoked, the correction view cannot be reinstated without creating a new correction view URL. This operation does not affect the envelope's content or status; it only restricts access to the correction interface.
Rotate Template Page Image: Rotates a page image within a DocuSign template for display purposes. This endpoint allows users to adjust the orientation of a specific page image to either the left or right within a template. It is particularly useful when preparing templates for use in electronic signature processes, ensuring that page images are correctly oriented for optimal viewing and signing. This operation only affects the display of the page image and does not alter the actual content of the document. Use this endpoint when you need to correct or adjust the orientation of page images in your DocuSign templates before sending them out for signatures.
Rotate page image for envelope: This endpoint rotates a page image within a specific document of an envelope in DocuSign. It allows users to change the orientation of a page to either left or right for improved display and readability. This function is particularly useful when dealing with documents that may have been scanned or uploaded in an incorrect orientation. The rotation is applied only to the display of the image and does not permanently alter the original document. Use this endpoint when you need to adjust the viewing angle of a specific page within an envelope, especially before sending it for signatures or during the review process.
Send Envelope: Sends a draft envelope by updating its status to 'sent'. Example envelope_id format: '93be49ab-xxxx-xxxx-xxxx-f752070d71ec'
Set User Signature Image: Sets or updates a user's signature image, initials, or stamp in their DocuSign account. This endpoint uploads an image file to replace or create a signature element. Use this action to: - Upload a signature image for electronic document signing - Set initials image for a user - Add custom stamp images The image is uploaded using multipart/form-data format. Supported image formats include PNG, JPG, GIF, and BMP. Transparent PNG is recommended for best visual results when overlaying on documents. Note: You must first retrieve the signatureId using RETRIEVE_USER_SIGNATURE_DEFINITIONS action, or create a new signature using ADD_OR_UPDATE_USER_SIGNATURE action.
Set envelope purge config for account: Configures automatic envelope purge settings for a DocuSign account. This action allows account administrators to set up policies for automatically removing envelope documents after a specified retention period. The configuration includes options for: - Enabling/disabling automatic purging - Setting the retention period (0-999 days) - Removing tabs and attachments during purge - Redacting personally identifiable information (PII) **Important:** This endpoint requires account administrator privileges. PII redaction can only be enabled when `removeTabsAndEnvelopeAttachments` is also enabled. **Use Cases:** - Set up automated document retention policies for compliance - Configure PII redaction for privacy requirements - Manage storage costs by purging old envelopes **Beta Feature:** This functionality is currently in beta status.
Set initials image for accountless signer: This endpoint allows you to update the initials image for a signer who does not have a DocuSign account within a specific envelope. It's used to customize the appearance of a signer's initials on documents, enhancing the personalization of the signing process. The endpoint supports various image formats (gif, png, jpeg, and bmp) with a file size limit of 200K. It's particularly useful for maintaining brand consistency or adding a personal touch to documents for signers without DocuSign accounts. Note that this operation can only be performed by the envelope sender and is subject to specific account permissions.
Set shared access for users and templates: This endpoint sets shared access for users and templates in DocuSign. It manages collaboration and access control within an organization for envelopes, templates, and folders. Only users with admin privileges can set envelope access, while template access requires ownership or admin rights. Changes replace current status, not add to it. Use 'item_type=templates' for template access. It's an improved version of Update Group Share, offering more granular control.
Set signature image for no account signer: This endpoint updates the signature image for an accountless signer in a DocuSign envelope. It allows you to set a custom signature image for recipients who don't have a DocuSign account, enhancing the flexibility of the signing process. The endpoint supports gif, png, jpeg, and bmp image formats, with a file size limit of less than 200K. It's specifically designed for use with accountless signers or in-person signers, providing a way to personalize their signature appearance. This function is useful when you need to customize the signature image for recipients who are not DocuSign account holders, such as one-time signers or in-person signing scenarios.
Set templates as account favorites: This endpoint allows users to set one or more templates as account favorites in DocuSign. It's used to mark specific templates for quick access within a user's account. The endpoint can handle multiple templates in a single request, making it efficient for bulk operations. It's particularly useful for users who frequently work with the same set of templates and want to streamline their workflow. Note that this is a beta API and may be subject to changes in future versions.
Set up connect oauth configuration: Sets up Connect OAuth configuration for a specified DocuSign account using a custom authorization server. This endpoint enables secure, OAuth-based communication for DocuSign Connect, allowing real-time notifications about envelope status changes. It should be used when integrating DocuSign Connect with your own authorization server for enhanced security and control over webhook notifications. This tool is essential for account administrators setting up or updating Connect OAuth configurations, but requires Connect to be enabled on the account.
Share template with group: This endpoint allows you to share a DocuSign template with a specified members group. It's used to grant access to templates for collaboration and reuse within an organization. Note that this endpoint is deprecated, and for newer functionality, it's recommended to use the 'Accounts: Update Shared Access' endpoint instead. The operation updates the sharing settings for a specific template, enabling administrators to control template access across different groups efficiently.
Submit batch historical envelopes to webhook: This endpoint submits a batch of existing envelopes to a specified webhook for historical publishing. It allows you to retroactively send envelope data to your systems for completed transactions, which is useful for data synchronization, auditing, or recovering missed notifications. The endpoint uses an ad hoc configuration provided in the request, rather than relying on existing Connect configurations. Unlike regular Connect listeners that monitor new activity, this endpoint is specifically designed for publishing historical data on demand. It only supports JSON format for data transmission and allows fine-grained control over which envelope data and events are included in the webhook payload. The endpoint is particularly useful when you need to backfill data, synchronize systems after downtime, or perform bulk operations on historical envelopes.
Toggle api request logging: This endpoint enables or disables API request logging for troubleshooting purposes in DocuSign. It allows users to toggle the logging of REST API requests and responses, set the maximum number of log entries, and view the remaining log capacity. The tool is crucial for debugging API integrations by providing detailed request/response information while ensuring sensitive data is omitted from the logs. It should be used when investigating API-related issues or monitoring API usage patterns. The endpoint has a limit of 50 log entries and automatically disables logging when this limit is reached. Only requests from authenticated users are captured, and the logs can be retrieved or cleared using separate API calls.
Update Account Watermark Preview: Updates and previews watermark settings for a DocuSign account before applying them. This endpoint allows you to test watermark appearance settings including text, font, color, size, display angle, and transparency without permanently saving the configuration. Use this action when you want to preview how watermark customizations will look on documents before committing to the changes. The watermark preview shows how the settings will appear on in-progress documents. Note: All parameters are optional. If not specified, existing watermark settings will be preserved. Parameters with specific valid values (fonts, colors, angles, etc.) will use defaults if invalid values are provided.
Update Bulk Send Batch Name: Updates the name of an existing DocuSign bulk send batch. This action allows you to rename a specific bulk send batch for better organization and identification. Use this when you need to update the batch name after creation, for example to reflect the batch purpose or processing status. Key points: - Only updates the batch name; other batch properties remain unchanged - The batch name can be up to 500 characters long - Returns the updated batch status including sent/failed envelope counts - Requires a valid bulkSendBatchId from a previously created bulk send batch Note: Bulk Send is an advanced DocuSign feature available on Business Pro and Enterprise Pro plans. Ensure your account has bulk send permissions enabled.
Update Envelope DocGen Form Fields: This method dynamically generates an envelope's documents by populating its sender fields. The envelope must be in a draft state. Use the DocumentGeneration::getEnvelopeDocGenFormFields response to retrieve the list of sender fields for your envelope. Use that list to build the request for this method. For each field, specify the field name and the value to populate. Important notes: - If update_docgen_formfields_only is false (the default), the documentId changes after the update. - This endpoint does not validate number, date, or select data field values. The request can succeed even if a number or date field value is not a valid number or date, or if a select field value is not one of the allowed values.
Update Template Delayed Routing Rules: This endpoint updates the scheduled sending rules for a specific workflow step in a DocuSign template. It allows users to set up delayed routing for envelopes, controlling when documents are sent to recipients associated with the workflow step. The function can be used to implement time-based workflows, such as sending documents after a specified delay or at a future date. It's particularly useful for managing complex document processes that require timed releases or staged approvals. The endpoint supports setting either a relative delay or an exact send date, but not both simultaneously. Note that the maximum allowed delay is 30 days from the time of the request.
Update Template Doc Visibility: This endpoint updates document visibility settings for one or more recipients in a DocuSign template. It allows fine-grained control over which documents are visible to specific recipients, enhancing document security and workflow customization. The method is particularly useful when you need to restrict access to certain documents for some recipients while maintaining full visibility for others. However, it's important to note that some recipient types (Carbon Copy, Certified Delivery, Editor, and Agent) will always have full document visibility, and documents with assigned tabs cannot be hidden from their respective recipients.
Update Template Recipient Document Visibility: Updates document visibility settings for a specific recipient in a DocuSign template. This endpoint allows you to control which documents a particular recipient can see in a template with multiple documents. Use this when you need to: - Restrict certain documents from specific recipients for security or privacy - Customize the signing experience by showing only relevant documents to each recipient - Modify document access after a template has been created **Important Constraints:** - Documents with tabs assigned to a recipient cannot be hidden from that recipient - Carbon Copy, Certified Delivery, Editor, and Agent recipients always see all documents - The recipientId must exist in the template before updating visibility **Use Case Example:** In a multi-document employment contract template, you might want to hide salary details from HR coordinators while showing them to the hiring manager and the candidate.
Update User Authorization Dates: Updates the start and/or end dates for a specified user authorization in DocuSign. This endpoint allows account administrators or the principal user to modify the duration of an existing authorization, enabling precise control over when an agent can act on behalf of the principal user. It's particularly useful for extending or shortening authorization periods, ensuring that access rights are aligned with business needs and security policies. The endpoint returns detailed information about the updated authorization, including user details and permission levels. Use this when you need to adjust the timeframe of an existing user authorization without changing other authorization parameters.
Update account password rules: This endpoint updates the password rules for a DocuSign account. It allows account administrators to modify various password policy settings, including expiration, complexity requirements, lockout durations, and security question requirements. Use this endpoint to enhance account security, comply with organizational policies, or adapt to changing security needs. The endpoint provides extensive customization options, from basic password requirements to complex, multi-factor authentication setups. Note that changes made through this endpoint will affect all users within the specified account, so it should be used carefully and in accordance with your organization's security policies.
Update account stamp by id: This endpoint allows you to update an existing account stamp (signature) in DocuSign. It provides extensive customization options for the stamp's appearance, associated users, and properties. Use this when you need to modify an existing stamp's details, such as its image, font, size, or user permissions. The endpoint is particularly useful for maintaining up-to-date and personalized stamps for document signing. Note that this operation will overwrite the existing stamp properties, so ensure all desired properties are included in the request, even if they haven't changed.
Update account watermark information: This endpoint updates the watermark settings for a specified DocuSign account. It allows customization of various watermark properties such as display angle, font, color, size, and transparency. The endpoint can be used to enable or disable the watermark feature, change the watermark text, or modify its appearance on documents. It's particularly useful for maintaining brand consistency, indicating document status, or adding security features to in-progress documents. The endpoint returns the updated watermark information, allowing immediate confirmation of changes. Note that while most properties can be modified, the imageBase64 property is read-only and cannot be set through this call.
Update billing plan for account: Updates billing plan information, address, and payment details for a DocuSign account. Allows comprehensive modifications to billing setup, including payment methods, plan features, and promotional offers. Offers a preview mode for reviewing changes before applying. Use for significant billing configuration changes or plan transitions. Exercise caution as it may trigger immediate billing changes.
Update connect oauth configuration: This endpoint updates an existing Connect OAuth Configuration for a DocuSign account. Use it to modify OAuth settings for DocuSign Connect integrations, such as updating authorization URLs, client credentials, or scopes. It's crucial for maintaining secure data exchange between DocuSign and integrated systems. Exercise caution when using this endpoint, as incorrect changes may disrupt existing integrations.
Update contacts information: This endpoint updates one or more contacts associated with a DocuSign account. It allows for comprehensive modifications to contact information, including personal details, communication methods, and notary-specific data. The endpoint supports bulk updates, enabling efficient management of multiple contacts in a single API call. It's particularly useful for maintaining up-to-date contact records, especially in scenarios involving shared contacts or notary services. The endpoint returns the updated contact details upon successful execution, providing immediate confirmation of the changes made.
Update custom fields in envelope document: This endpoint allows you to update existing custom document fields in a specific document within an envelope in DocuSign. Custom document fields are name-value pairs that can be used to store additional metadata or information about the document. This function is useful when you need to modify or add custom data to a document that is already part of an envelope. It's important to note that while DocuSign returns this custom field information in the status, it does not use this data for any internal processes. This endpoint should be used when you need to update or add custom metadata to a document in an existing envelope, but not for modifying the actual content of the document or the envelope's core properties.
Update custom tab information for account: This endpoint updates the information for a custom tab associated with a specific DocuSign account. It allows for extensive customization of tab properties, including appearance, behavior, and positioning within documents. The endpoint is used when modifying existing custom tabs to change their characteristics or functionality. It provides granular control over tab settings but requires careful consideration of the numerous optional parameters to avoid unintended changes.
Update docusign connect configuration: This endpoint updates an existing DocuSign Connect configuration for a specified account. It allows you to modify various settings such as the events that trigger notifications, the endpoint URL for receiving webhooks, data format preferences, and integration details with Salesforce. Use this endpoint when you need to change the behavior of your Connect configuration, such as enabling or disabling it, updating the notification URL, or modifying the events that trigger updates. It's particularly useful for adjusting your integration as your application's needs evolve or when troubleshooting issues with your webhook setup. Note that this endpoint requires account administrator privileges and Connect must be enabled on the account. Be cautious when updating critical settings like 'requiresAcknowledgement' or 'useSoapInterface', as they can significantly impact how your application receives and processes DocuSign notifications.
Update electronic record disclosure: Updates the Electronic Record and Signature Disclosure (ERSD) for a DocuSign account. Allows administrators to customize the default disclosure, switch to a custom one, or update existing custom disclosures in multiple languages. Only account administrators can use this method. Changes may require unsigned recipients to accept a new disclosure version before signing documents.
Update envelope attachment: Updates an existing attachment for a draft or in-process envelope in DocuSign. This endpoint allows you to modify attachment properties such as access control, type, content, label, and name. It supports file attachments up to 50 MB and provides options for chunked uploads of large files. Use this endpoint when you need to update or replace an attachment that has already been added to an envelope, before it has been sent for signing. Note that this endpoint is specifically for envelope attachments (developer-only files) and should not be confused with signer attachments.
Update envelope custom fields: This endpoint allows users to update custom fields for draft and in-process envelopes in DocuSign. It enables the modification of both list-based and text-based custom fields, which can be used for sorting, organizing, searching, and other downstream processes. This tool is particularly useful when you need to add or modify envelope-specific data that is not captured by standard DocuSign fields. It should be used when customizing envelopes with additional metadata or when implementing specialized workflows, such as eVaulting for eOriginal customers. Note that these custom fields are visible to envelope creators and senders in the Envelope Settings section but are not visible to envelope recipients.
Update envelope notification settings: Updates the notification settings for a specific DocuSign envelope, including reminders and expirations. This endpoint allows you to customize when and how often recipients receive reminder emails, as well as set the expiration period for the envelope. It can either apply custom settings or use the account's default notification settings. The method only updates the settings and does not trigger the sending of any notifications. Use this when you need to modify the reminder or expiration behavior for an existing envelope, such as extending the expiration date or adjusting the frequency of reminders.
Update envelope scheduled sending rules: Updates the scheduled sending rules for an envelope's workflow in DocuSign. This endpoint allows users to set or modify when an envelope will be sent, providing precise control over document delivery timing. It can be used to delay sending, schedule future sends, or manage bulk send operations with specific timing. The endpoint is particularly useful for automating complex document workflows or coordinating large-scale document distributions.
Update envelope workflow definition: Updates the workflow definition for a specified envelope in DocuSign. It allows modification of scheduled sending, delayed routing, and conditional recipient rules. Use this endpoint to add or update scheduling for draft or in-progress envelopes, or to add delayed routing to envelopes not yet in workflow processing. The tool supports complex document workflows with timed actions, conditional processing, and staged approvals.
Update envelope workflow step: Updates a specific workflow step for a DocuSign envelope, allowing for customization of envelope processing, including delayed routing and conditional recipients. This endpoint can be used to modify workflow steps for both draft envelopes and sent envelopes (as long as the previous step hasn't been completed). It enables features like scheduled sending and complex routing rules based on recipient actions or document content. The endpoint is particularly useful for implementing advanced document workflows, such as time-based routing or conditional approval processes.
Update group information: Updates group information for one or more user groups in a DocuSign account. This action allows you to modify group properties such as group name and permission profile assignments. **Required Parameters:** - groups: A list of group objects to update. Each group must include: - groupId: The DocuSign group ID identifying which group to update - At least one field to update (e.g., groupName or permissionProfileId) **Common Use Cases:** - Rename one or more groups - Change the permission profile assigned to a group - Update multiple groups in a single API call **Note:** The accountId parameter is automatically populated from authentication metadata. To get group IDs, first use the GET_GROUPS_INFORMATION_FOR_ACCOUNT action to list existing groups.
Update notary jurisdiction info: Updates the jurisdiction information for a notary in the DocuSign system. This endpoint allows for modification of various details related to a notary's commission and jurisdiction settings. It should be used when there are changes to a notary's information, such as their registered name, commission expiration date, or seal type. The endpoint requires a full jurisdiction object in the request body, even when updating only specific fields. It's important to note that this endpoint can only be used by authenticated users who are registered notaries and for jurisdictions they are authorized for.
Update signing group details: Updates the details of a specified signing group within a DocuSign account, including the group name, email, and member information. This endpoint allows for modifying existing group data and adding new members to the signing group, with a maximum limit of 50 members per group. It's particularly useful for managing and maintaining up-to-date signing group information, ensuring efficient document routing and signing processes. The endpoint requires the account ID and signing group ID for identification, and returns comprehensive details about the updated signing group, including creation and modification timestamps. Use this when you need to modify signing group properties or adjust its membership, but be aware of the 50-member limit per group.
Update template custom fields: Updates the custom fields in a DocuSign template. This endpoint allows you to modify both list and text custom fields associated with a specific template, ensuring each field has a unique name. It's used to customize templates for specific use cases, enabling prepopulation of metadata for envelopes created from the template. The endpoint supports updating multiple custom fields in a single request, making it efficient for batch updates. However, it does not create new custom fields; it only modifies existing ones.
Update template document custom fields: This endpoint updates existing custom document fields in a specific document within a DocuSign template. It allows you to modify metadata associated with a template document without changing the document's content or structure. Use this when you need to update or add custom information to a template document, such as internal reference numbers, project codes, or any other metadata relevant to your document workflow. The endpoint is particularly useful for maintaining up-to-date metadata in frequently used templates without recreating them. Note that while DocuSign stores and returns these custom fields, it does not process or use them for any internal operations. The update is specific to a single document within a template, identified by the documentId parameter.
Update template lock information: This endpoint allows you to update the lock information for an already locked template in DocuSign. It is used to modify the duration of an existing lock or change the name of the application that has locked the template. This operation is crucial for managing access to templates that are currently being edited, ensuring that multiple users don't make conflicting changes simultaneously. The endpoint requires the X-DocuSign-Edit header for authorization and can update specific lock properties without affecting others. It should be used when you need to extend a lock duration or update the locking application's identifier, but not for creating new locks or unlocking templates.
Update template notification settings: This endpoint updates the notification structure for an existing DocuSign template. It allows users to customize reminder and expiration notifications for a specific template, which can then be used to create envelopes with these predefined settings. The endpoint is particularly useful when you need to modify the notification behavior for a frequently used template without changing the template's core content. It provides granular control over when and how often recipients are reminded about pending signatures, as well as when the envelope will expire. This functionality helps in managing document workflows more efficiently by reducing the need for manual follow-ups and ensuring timely completion of signing processes.
Update user account settings: This endpoint updates the account settings and email notification types for a specified user in DocuSign. It allows for comprehensive customization of a user's experience within the DocuSign platform, including locale preferences, timezone settings, email notifications, account management capabilities, and template management options. The endpoint is particularly useful when administrators need to modify user settings en masse or when users require specific configuration changes to align with their workflow or organizational requirements. It's important to note that while this endpoint offers extensive customization, some settings may be restricted based on the user's permissions or account type. Additionally, changes made through this endpoint may have immediate effects on the user's DocuSign experience and should be used judiciously.
Update user information for specified user: The User_PutUser endpoint allows updating user information for a specified user within a DocuSign account. It provides comprehensive control over user settings, including personal information, permissions, notification preferences, and locale settings. This endpoint should be used when modifying user profiles, adjusting user permissions, or updating user-specific configurations within a DocuSign account. The operation requires the account ID and user ID as path parameters, and accepts a complex JSON object in the request body containing the updated user information. Note that users can only access and modify their own information, even if they have administrative privileges. The endpoint returns the updated user information upon successful modification.
Update user profile image: Updates the user's profile image in DocuSign by uploading a new image file. This action allows users to personalize their DocuSign account by uploading a profile picture. Supported formats include GIF, PNG, JPEG, and BMP. The image file must be less than 200KB, and for optimal display, DocuSign recommends dimensions of no more than 79x79 pixels. Note: Users can only update their own profile image. The userId is automatically set to the authenticated user.
Update user signature by id: Updates or creates a user's signature and initials for a specified DocuSign account. This endpoint allows for customization of signature appearance, including font, stamp format, and date stamp properties. It can be used to modify an existing signature or create a default signature if one doesn't exist. The endpoint requires the user to be authenticated and a member of the specified account, with the userId matching the authenticated user's ID. It's particularly useful for personalizing signature appearance or creating new signatures for users within an organization's DocuSign account.
Update workflow step for template: This endpoint updates a specified workflow step for a DocuSign template. It allows users to modify various aspects of the workflow step, including delayed routing settings, recipient routing rules, and conditional recipient configurations. The endpoint is used to fine-tune the automation and customization of document workflows within DocuSign templates. It's particularly useful for implementing complex routing scenarios, adding delays in document processing, or setting up conditional recipient rules based on form field values or other criteria. This tool should be used when there's a need to modify existing workflow steps in a template to adjust the document routing process or recipient handling.
Update workspace item metadata: Updates the metadata for a specific file in a DocuSign workspace. This endpoint allows you to modify file properties such as name, content type, extension, and visibility settings without changing the actual file content. Use this action when you need to rename a file, update its MIME type, or change its public/private access settings. The file content itself remains unchanged; only its metadata attributes are modified. This is particularly useful for organizing and managing workspace files, correcting metadata, or adjusting file visibility.
Updateaccountbrandsettings: The UpdateAccountBrandSettings endpoint modifies or replaces an existing brand configuration for a DocuSign account. It customizes various brand aspects like company name, languages, colors, and landing pages. Use this tool to update branding elements for consistency across DocuSign interactions. It can update specific fields or replace the entire brand configuration. Note that branding must be enabled for the account, and resource file modifications require separate API calls.
Updateaccountcustomfield: This endpoint updates an existing account custom field in DocuSign. It allows you to modify the properties of a custom field, such as its name, type, required status, visibility, and value. The endpoint supports both list and text custom fields, enabling account administrators to refine and adjust custom metadata used for grouping and managing envelopes. Use this endpoint when you need to change the configuration or content of an existing account-level custom field. Note that this operation affects the custom field at the account level, potentially impacting all envelopes and templates that use this custom field.
Updateaccountsettings: Updates various settings for a specified DocuSign account. This endpoint allows administrators to configure a wide range of account-level options, including security settings, compliance features, and user interface preferences. Use this when you need to modify your DocuSign account configuration to align with organizational needs and policies. Note that many settings require administrative privileges, and some may have interdependencies with other features.
Updateaccountstamps: Update existing account stamps (signatures) in a DocuSign account. Modifies properties of existing stamps by referencing their signatureId. Supports updating names, sizes, formats (NameHanko/NameDateHanko), resize permissions, phonetic names, and external IDs. Supports batch updates of multiple stamps in one request. Note: The signatureId changes after each update. Use DOCUSIGN_ADD_OR_UPDATE_ACCOUNT_STAMPS to create new stamps. At least one stamp must be included in the request.
Updatedocumentvisibilityrecipients: Updates document visibility settings for multiple recipients in a DocuSign envelope. Use this action to control which documents each recipient can see and their access level (read-only or editable). This is essential for managing multi-document envelopes where different recipients should only access specific documents. Key features: - Set visibility for multiple document-recipient pairs in one request - Control access rights: read-only or editable - Hide documents from specific recipients (if no tabs assigned) Important limitations: - Documents with tabs assigned to a recipient cannot be hidden from that recipient - Some recipient types (Carbon Copy, Certified Delivery, Editor, Agent) always see all documents - The envelope must be in a state that allows modifications (typically 'created' status) Example use case: In a purchase agreement with financial disclosures, you might want the buyer to see the main agreement and their financial documents, while hiding the seller's confidential financial information.
Updateenoteintegrationconfig: Updates the eNote integration configuration for a specific DocuSign account. This endpoint allows users to modify settings related to eNote functionality, including API key, Connect configuration, eNote configuration, organization details, and user credentials. It should be used when setting up or modifying the eNote and eOriginal integration for secure electronic document management. The endpoint requires the account to have the 'Allow eNote for eOriginal' plan item enabled. Note that this is a beta API and may be subject to changes. Ensure that both Connect and eOriginal are properly configured for the integration to work correctly.
Updateenvelopedelayedroutingrules: Updates the delayed routing rules for a specific workflow step in a DocuSign envelope. This endpoint allows you to add or modify delayed routing settings for both draft and sent envelopes, as long as the previous workflow step has not been completed. It enables you to control when the envelope will be sent to the recipients associated with the workflow step, either by specifying a relative delay or an exact future date and time. The endpoint can be used to implement timed workflows, schedule future sendings, or adjust existing delay rules. Note that updating an in-progress delay will reset the countdown.
Updateenvelopeemailsettings: Updates the existing email override settings for a specified envelope in DocuSign. This endpoint allows customization of the Reply To email address and name, as well as BCC email addresses for a specific envelope. It's particularly useful when you need to modify email settings for an individual envelope without affecting account-level settings. Note that changes only apply to future email communications related to the envelope. This endpoint can also be used to remove individual email override settings by providing an empty string for the value to be deleted.
Updatelockforenvelope: Updates lock settings for an already-locked envelope in DocuSign to extend duration or modify the locking application identifier. Use this to extend lock time during long editing sessions (max 1800 seconds/30 minutes) or update the lockedByApp identifier. Returns updated lock information including the new lock token, expiration time, and duration. Prerequisites: Envelope must already be locked using DOCUSIGN_LOCK_AN_ENVELOPE_FOR_EDITING. Only the user/application that created the lock can update it. X-DocuSign-Edit header with valid lock token is handled automatically. Common scenarios: Extending locks to prevent expiration during lengthy edits, refreshing lock tokens after interruptions, or updating application identifiers.
Updatepermissionprofilesettings: This endpoint updates an existing account permission profile in DocuSign. It allows administrators to modify various settings and permissions for users associated with the profile, providing granular control over user capabilities within the DocuSign platform. The endpoint is used to customize user access rights, configure notification preferences, and set other account-specific options. It's particularly useful for maintaining security and tailoring user experiences based on roles or departments within an organization. Note that this endpoint requires administrative access and should be used cautiously, as changes can significantly impact user abilities and workflow processes.
Updaterecipientdocumentvisibility: This endpoint updates the document visibility settings for a specific recipient within a DocuSign envelope. It allows fine-grained control over which documents a recipient can see and whether they have read-only or edit access. Use this when you need to modify document access for a particular recipient after an envelope has been created. This is particularly useful for managing complex workflows where different recipients need access to different sets of documents. Note that you cannot hide documents from recipients who have tabs assigned to them, and certain recipient types always have full document visibility.
Updatesigninggroupnames: Updates the names of one or more existing signing groups in DocuSign. This endpoint allows you to modify the names of signing groups, which are collections of users grouped together for document signing purposes. It's useful when you need to rename signing groups to reflect organizational changes or improve clarity. The endpoint updates only the group names and doesn't modify other group properties or memberships. Use this when you need to maintain accurate and up-to-date naming conventions for your signing groups.
Updatetemplatescheduledsendingrules: Updates the scheduled sending rules for a DocuSign template, controlling when envelopes created from this template are automatically sent. Use this to set up either a relative delay (e.g., send 2 days after creation) or an absolute future date/time. This is useful for: - Automating timed document delivery workflows - Coordinating envelope sending with business events - Allowing review periods before automatic sending - Managing bulk send operations with scheduled timing Note: Maximum delay is 30 days. Requires Standard plan or higher. Only one rule (either delay or resumeDate) can be specified per template.
Updatetemplateworkflowdefinition: Updates the workflow definition for a specified template in DocuSign, allowing for customization of the document signing process. This endpoint enables users to modify the sequence of steps, set up conditional routing, schedule envelope sending, and define recipient rules for a template. It's particularly useful for complex signing workflows that require precise control over the timing and conditions of each step in the process. The updated workflow can include features such as delayed sending, conditional recipients, and paused steps, providing flexibility in managing the document lifecycle. This tool should be used when there's a need to modify or refine the existing workflow of a template to accommodate specific business processes or compliance requirements. It's important to note that this update affects only the workflow definition and does not modify other aspects of the template such as document content or basic recipient information.
Updateusernotaryinformation: The UpdateUserNotaryInformation endpoint modifies a notary's profile and settings in DocuSign. It manages account details, preferences, and operational parameters. Use this to update a notary's visibility, capabilities, or personal settings. It's crucial for maintaining accurate records and ensuring compliance with regulations. Note that all required fields must be provided, even for partial updates.
Updateuserprofileinformation: Updates a user's profile in DocuSign, including personal details, privacy settings, and user ID card information. It allows modifications to name, address, locale preferences, and various account settings. Users can only update their own information. Some settings may require admin rights to modify. Use for keeping user profiles current and adjusting preferences.
Updateworkspaceinformation: Updates information about a specific DocuSign workspace. This endpoint allows you to modify various aspects of a workspace, including its name, description, settings, and status. It's used when you need to change workspace details or adjust collaboration settings. The endpoint requires both the account ID and workspace ID to identify the specific workspace to update. You can update multiple properties of the workspace in a single request by including them in the request body. Note that this operation may affect all users with access to the workspace, so use it carefully. The endpoint returns the full updated workspace object, allowing you to confirm the changes made.

How to connect DocuSign

Sign in to Definable AI and go to Apps
Search for DocuSign and click Connect
Authorize via OAuth2 — takes under 30 seconds
Use DocuSign actions in your AI agents and workflows