> 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

# Embedding Docusign eSignature into your app

> Learn about how to embed the envelope sending and document signing views directly into your app. Explore example requests and responses and see the requirements to enable this feature.

An eSignature agreement flow includes multiple user experience options (UXs) designed for different use cases. For most user experiences, you have two options for integrating the experience into your app:

* **Use the API:** Your app can provide its own user experience and call the eSignature API to implement your app’s e-signature functionality. For example, you can add a **Send for Signature** button to your app. Your software would then call the eSignature API to create and send an envelope by combining a template with your app’s current document and signer’s information. You should always investigate this option when you’re designing your app.

  * Uses your own app’s user experience, and so typically provides a smoother experience for your users.
  * Is often easy to provide and implement.
* **Embed the Docusign user experience:** You can embed parts of the Docusign eSignature signing experience into your application. In other cases, your app can redirect to Docusign and, afterwards, Docusign will redirect the user’s browser back to your application.

  * Uses your app’s user experience to initiate the signing process and enable your users to send or sign documents directly within your app.
  * Avoids the need to switch contexts to email.

## Embedding options for eSignature

### Preparing and sending the envelope

This step is often the easiest to implement using your own user experience and the eSignature API. Gather the information for the signers and other recipients, your templates, documents, and other information for the envelope, then send the envelope using the API.

**Tagging documents**

When creating the envelope, your documents should be *tagged* with text that Docusign can use as identifiers to place the **Sign Here**, **Text**, **Payment**, and other types of [Tabs](/docs/esign-rest-api/esign101/concepts/tabs) (also known as fields) with which the recipients interact. This recommended type of tab placement is known as [Auto-place (anchor tagging)](/docs/esign-rest-api/esign101/concepts/tabs/auto-place). [Fixed positioning](/docs/esign-rest-api/esign101/concepts/tabs/fixed) placement for tabs is also supported.

One advantage of using templates to create your envelope is that, if a template definition can be used to tag the documents, the documents will not need to be tagged for each envelope.

If the documents for an individual envelope need to be manually tagged, you can embed the **Sender View** into your application. For more information, see [Embed the Sender and Correct views](/docs/esign-rest-api/esign101/concepts/embedding/embed-sender-correct-views).

### Correcting the envelope

You can correct an envelope by making changes to it after it has been sent. When you design your process flow, correcting an envelope should never be a standard part of your process. Envelopes should only be corrected as part of an exception process. Envelopes cannot be corrected after they’ve reached the completed state.

Sometimes, however, you may need to change an envelope’s recipients, documents, tabs, or other data after the envelope has already been sent and possibly signed by some recipients. For these cases, you can correct envelopes programmatically using the API, or you can [Embed the Sender and Correct views](/docs/esign-rest-api/esign101/concepts/embedding/embed-sender-correct-views).

### Signing

There are two types of recipient signers:

* **Remote Signers**. These signers are notified by email, SMS, or WhatsApp to open the Docusign web app and sign. This is the default mode.
* **Embedded Signers**. These signers use your application and the **Embedded Recipient View** to sign from within your application. This is the recommended choice when the signer is already using your application via a browser or mobile app. See [Embedded signing](/docs/esign-rest-api/esign101/concepts/embedding/embedded-signing) for an example.

Note that the API cannot be used to sign a document. It must be signed directly by recipients.

## Template editing

Depending on your application’s use cases, you can use the [TemplateViews : createEdit](/docs/esign-rest-api/reference/templates/templateviews/createedit) to enable your application’s users to update templates from within your application.

## Next steps

For details on each step and full example code that demonstrates how to request signatures using embedded signing, see:

* [Embed the Sender and Correct views](/docs/esign-rest-api/esign101/concepts/embedding/embed-sender-correct-views)
* [Embedded signing](/docs/esign-rest-api/esign101/concepts/embedding/embedded-signing)
* [How to request a signature using focused view](/docs/esign-rest-api/how-to/request-signature-focused-view)
* [How to request a signature through your app](/docs/esign-rest-api/how-to/request-signature-in-app-embedded) (embedded signing)
* [How to request a signature using a composite template](/docs/esign-rest-api/how-to/request-signature-composite-template-embedded) (embedded signing)
* [How to request a signature through your app (embedded signing) with a CFR Part 11 account](/docs/esign-rest-api/how-to/request-signature-in-app-embedded-cfrpart11)
* [How to send an envelope via your app](/docs/esign-rest-api/how-to/embedded-sending) (embedded sending)
* [How to embed a workflow in your web application](/docs/maestro-api/maestro101/embed-workflow)

For a demo of embedded signing and a walkthrough of the sequence of API calls that implement it, see the [Embedded Signing](https://myapicalls.sampleapps.docusign.com/scenario/2) scenario in the MyAPICalls sample app.

> Learn about how to embed the envelope sending and document signing views directly into your app. Explore example requests and responses and see the requirements to enable this feature.

## Docs

- [Embedded signing](https://developers.docusign.com/docs/esign-rest-api/esign101/concepts/embedding/embedded-signing.md): Embedded signing (also called the envelope recipient view) enables users to view and sign documents directly through your app or website by embedding a Docusign signing session into your application.
- [Docusign JS for embedded signing reference](https://developers.docusign.com/docs/esign-rest-api/esign101/concepts/embedding/docusign-js-embedded-reference.md): See details about Docusign JS methods used for embedded signing.
- [Embed the Sender and Correct views](https://developers.docusign.com/docs/esign-rest-api/esign101/concepts/embedding/embed-sender-correct-views.md): Embedded sending (also called the envelope sender view of an envelope) enables your app’s users to edit the tabs, documents, recipients, and other settings of draft Docusign envelopes within your app before sending them out for approval.