DocuSign

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.

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.

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.

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.

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.

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.

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 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.

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.

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.

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.

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.

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.

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 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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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).

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.