> You are reading the Docusign Developer Documentation. For clean Markdown of any page, append .md to the page URL. > > Documentation indexes by section: > - APIs and SDKs: https://docusign.docs.buildwithfern.com/docs/llms.txt > - Platform 101: https://docusign.docs.buildwithfern.com/platform/llms.txt > - Extension Apps: https://docusign.docs.buildwithfern.com/extension-apps/llms.txt > - Docusign CLI: https://docusign.docs.buildwithfern.com/docusign-cli/llms.txt > > Authentication (OAuth, JWT Grant, M2M): https://docusign.docs.buildwithfern.com/platform/auth > Webhooks and Connect: https://docusign.docs.buildwithfern.com/platform/webhooks > > OpenAPI specifications: https://docusign.docs.buildwithfern.com/openapi.json > MCP server: https://docusign.docs.buildwithfern.com/_mcp/server # AccountSignatureProviders Resource Standards-Based Signatures (SBS) is the label used to describe the suite of signatures provided by Docusign that comply with regional and industry regulations, such as the electronic IDentification, Authentication and trust Services (eIDAS) regulation in Europe. ## Feature Differences When Using Standards-Based Signatures Some Docusign features are not compatible with Standards-Based Signatures, while others work somewhat differently. It's important to understand these key differences. ### Docusign Features Not Compatible with SBS * Attachment by fax * Concatenation of signer attachments * Legacy digital signatures * Markup * Notary ### Docusign Features That Change with SBS The following features work slightly differently with SBS: * **Advanced Correct:** After the first signature, adding or deleting a field is not allowed. This behavior occurs because SBS does not allow adding or removing form fields after a digital signature has already been applied to a PDF. * **Downloading Combined Envelopes:** A combined PDF is not digitally signed. This behavior occurs because concatenating digitally signed PDFs breaks the digital signatures on the PDFs. * **Freeform Signing:** After someone has signed, allows only signature and initials on free-form. This behavior occurs because if another signer has already signed the document, adding fields other than signature fields will break the existing digital signatures on the document. * **Watermarks:** All watermarks are added as PDF annotations. This behavior occurs because burning the watermark into the PDF will break the digital signatures on the document. * **Wet Signing:** Wet-signed documents are added as new documents to envelopes. This behavior results in the uploaded or faxed, physically signed document being added as a new document to the envelope. This new document gets only a platform seal. For more information, see [Standards Based Signatures](/docs/esign-rest-api/esign101/concepts/standards-based-signatures). ## Methods supported | Method | Description | | ------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------ | | [list](/docs/esign-rest-api/reference/accounts/accountsignatureproviders/list) | GET `/restapi/v2.1/accounts/{accountId}/signatureProviders` Gets the available signature providers for an account. | ## AccountSignatureProviders properties | Property | Type | Description | | -------------------- | ----- | -------------------------------------------------------------------- | | `signatureProviders` | array | Names of electronic or digital signature providers that can be used. | ## API Docs - AccountSignatureProviders [Get available signature providers](https://developers.docusign.com/docs/esign-rest-api/reference/accounts/accountsignatureproviders/list.md) ## OpenAPI Specification The raw OpenAPI 3.1 specification for this API is available at: - [OpenAPI JSON](https://developers.docusign.com/openapi.json) - [OpenAPI YAML](https://developers.docusign.com/openapi.yaml)