> 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

# Single-page applications and CORS

> The eSignature REST API supports apps that send API requests directly from a browser using CORS.

eSignature REST API 2.1 only

The eSignature REST API supports single-page applications (SPAs) that send API requests directly from a browser using Cross-Origin Resource Sharing (CORS).

For additional information, see:

* The [Single-page applications and CORS](/platform/single-page-applications-cors) overview page in the Developer Center Platform 101 section
* [Enable or disable CORS for apps](/platform/single-page-applications-cors/enable-disable-cors)
* The [CORS configuration](/platform/configure-app#cors-configuration) section of the Configure your app page
* [How to request a signature by email using CORS](/docs/esign-rest-api/how-to/request-signature-email-browser-cors)
* [How to request a signature through your CORS-enabled browser app](/docs/esign-rest-api/how-to/request-signature-in-cors-app-embedded)
* [CORS error responses](/platform/single-page-applications-cors/error-responses) for information on error messages and troubleshooting