> 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

# SOAP DSAPI.ASMX and API.ASMX endpoints

## SOAP DSAPI.ASMX and API.ASMX endpoints

Docusign has two SOAP API service endpoints: API.ASMX and DSAPI.ASMX. Docusign recommends using the DSAPI.ASMX endpoint for your integrations.

**Note**: The additional endpoints for credential and account administration are covered later in this guide.

The main advantage of the DSAPI.ASMX endpoint is that it performs authentication using the X-Docusign-Authentication header instead of the WSE3 UsernameToken. This authentication is more straightforward for a caller to implement than the WSE UsernameToken authentication.

The DSAPI.ASMX endpoint is a layered endpoint on top of the API.ASMX endpoint and, calls the API.ASMX WebService public functions after the caller has been authenticated. The DSAPI.ASMX supports X509 message signing, similar to the API.ASMX endpoint.

The DSAPI.ASMX endpoint does not have the following methods that exist in the API.ASMX:

* GetRecipientAuthenticationStatusEx
* RequestEnvelopeHistoryToken

Additionally, the DSAPI.ASMX endpoint does not perform schema validation of input XML. Validation is performed as required for various fields within business logic. The difference in field validation accounts for the differences in behavior between using the API.ASMX and DSAPI.ASMX. The API.ASMX endpoint uses of up-front schema validation, which causes different error messages to be shown to the API caller than the business logic. In some cases (such as the Email subject and blurb) the DSAPI.ASMX endpoint just truncates the fields when they are committed to the database, while the API.ASMX endpoint's schema validation would return an error based on schema validation.