> 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

# Web form instance processing

> Learn how an end user, your application, and the Docusign platform interact during the processing of a web form instance.

> **Note**
>
> The Web Forms API is available in all developer accounts, but only in certain production account plans. Contact [Docusign Support](https://support.docusign.com/s/?language=en_US) or your account manager to find out whether the Web Forms API is available for your production account plan.

Web Forms API requests enable you to create and manage [web form instances](/docs/web-forms-api/web-forms-101/concepts#web-form-instances). These sections walk you through the processing of web form instances generated from two types of [web form configuration](/docs/web-forms-api/web-forms-101/concepts#web-form-configurations): template-based and standalone. See [Web Forms concepts](/docs/web-forms-api/web-forms-101/concepts) for details about the differences between the two configuration types.

## Instance processing: Template-based web form configuration

The next two sections illustrate how an end user, your application, and the Docusign platform interact during the processing of a web form instance generated from a template-based web form configuration.

### Embedded web form instances

For this flow, the web form instance is embedded in your application, or your application redirects users to the Docusign platform to fill out the form instance.

![Instance creation from a template-based configuration via the Web Forms API](/_fern-files/_img/760312a6595a7abc8862598699c98dcc1fafd162630df30c4eaf1fa5ad11adb4.webp)

1. A user takes an action in your application, such as clicking a button, to start filling out a form.
2. Your application launches an [Instances:createInstance](/docs/web-forms-api/reference/webforms/instances/createinstance) API request or an equivalent [SDK](/docs/web-forms-api/sdks) method call to create a web form instance for the user to fill out. The request specifies the [web form configuration](/docs/web-forms-api/web-forms-101/concepts#web-form-configurations) from which to create the instance by referencing the configuration ID.
3. The response includes a secure, unique URL for the web form instance. See [Web form instance URLs](/docs/web-forms-api/plan-integration/instance-urls) for details.
4. Your application renders the web form instance URL. It can do this by using the Docusign JS client SDK to embed the instance in your application, or by redirecting to the instance URL. See [Render embedded web form instances](/docs/web-forms-api/plan-integration/render-instances) for details about these options.
5. The user populates the web form instance fields and submits the instance to Docusign, which generates an [envelope](/docs/web-forms-api/web-forms-101/concepts#esignature-envelopes) for the user to sign. Envelope creation and its display or delivery to the user occur automatically on web form instance submission, without requiring additional API requests from your application to create or deliver the envelope.

   The envelope includes values that the user entered on the form instance, if the form fields are [connected to template fields](https://support.docusign.com/s/document-item?bundleId=gmi1660583110357\&topicId=vlb1680643208628.html) in the web form configuration.

   The envelope delivery method depends on a setting in the web form configuration:

   * [Embedded signing](/docs/esign-rest-api/esign101/concepts/embedding): If the **Initiate signing session from email** setting on the web form configuration [signature page](https://support.docusign.com/s/document-item?bundleId=gmi1660583110357\&topicId=bna1674685085797.html) is not enabled, the envelope signing session is displayed in the web browser after the user submits the form.
   * [Remote signing](/docs/esign-rest-api/how-to/request-signature-template-remote): If the **Initiate signing session from email** setting is enabled, the user receives an email that includes a link to the envelope signing session.

   > **Note**
   >
   > If the web form configuration includes additional recipients who fill out the web form instance, they will receive an [envelope email](https://support.docusign.com/s/document-item?bundleId=ulp1643236876813\&topicId=pah1578456451991.html) with a link. On selecting the link, they will be routed to the envelope with the web form instance embedded in it. After filling out the web form instance, they will be presented with the envelope. For additional recipients who are not required to fill out the web form instance, the emailed link will take them directly to the envelope.
6. Depending on the method your application used to render the form instance URL in step 4, Docusign issues one of these responses when the web form submitter signs and completes the envelope in an embedded signing session:

   1. If your application used the Docusign JS client SDK to render the form instance, Docusign returns a JavaScript `sessionEnd` [event](/docs/web-forms-api/plan-integration/render-instances#form-and-envelope-events) of type `signingResult` to your application when the web form submitter completes the envelope.
   2. If your application redirected the user to the form instance URL and the web form configuration is set to use embedded signing, Docusign sends the user to the [returnUrl](/docs/web-forms-api/reference/webforms/instances/createinstance#schema__createinstancerequestbody_returnurl) specified in the `Instances:createInstance` API request or equivalent SDK method call. See [Redirect users after form submission](/docs/web-forms-api/plan-integration/redirect-users-form-submission) for details.

      For a remote signing session, a `sessionEnd` event of type `remoteSigningInitiated` is triggered when the envelope is generated. The user is not routed to another URL upon envelope completion unless the web form template is associated with a brand that specifies a [post-signing destination](https://support.docusign.com/s/document-item?bundleId=pik1583277475390\&topicId=tad1583277330037.html). See [Form and envelope events](/docs/web-forms-api/plan-integration/render-instances#form-and-envelope-events) and [Form submission after a redirect to the Docusign platform](/docs/web-forms-api/plan-integration/redirect-users-form-submission#form-submission-after-a-redirect-to-the-docusign-platform) for more information.

## Remote web form instances

For this flow, users access web form instances via an [envelope email](https://support.docusign.com/s/document-item?bundleId=ulp1643236876813\&topicId=pah1578456451991.html).

When created from a multiple-recipient [web form configuration](/docs/web-forms-api/web-forms-101/concepts#web-form-configurations), a remote web form instance and its associated envelope can be filled out by multiple users. Each recipient who fills out the form instance sees a distinct view with form fields specific to that user. All recipients are presented with the same envelope. The web form configuration specifies which users fill out both the form instance and envelope, and which users fill out the envelope only. The configuration also defines the order in which the recipients fill out the form instance and/or envelope. See [Build a Multiple-Recipient Web Form](https://support.docusign.com/s/document-item?bundleId=gmi1660583110357\&topicId=inc1745950777430.html) for instructions to set up multiple recipients.

In the example illustrated here, the web form configuration specifies two recipients who complete their tasks sequentially. The example configuration also requires that both recipients populate the web form instance, as well as the envelope.

![Remote web form instance process flow](/_fern-files/_img/2462664cb45694a6367b9ec4c99dffc50cbd75766ba28f69d6bf45802ee13f3b.webp)

1. Your application launches an [Instances:createInstance](/docs/web-forms-api/reference/webforms/instances/createinstance) API request or an equivalent [SDK](/docs/web-forms-api/sdks) method call to create a web form instance. The request specifies the web form configuration from which to create the instance by referencing the configuration ID.

   At the same time, Docusign generates an envelope based on the configuration's [web form template](/docs/web-forms-api/web-forms-101/concepts#web-form-templates).
2. The first user in the routing order receives an envelope email.
3. The link in the email routes the user to the Docusign platform, which displays an envelope with an embedded web form instance. The user fills out the form fields associated with that user's view of the web form instance. The user submits the web form instance.

   The eSignature envelope is displayed for the user to sign. Envelope display occurs automatically on web form instance submission.

   The envelope includes values that the user entered on the form instance, if the form fields are [connected to template fields](https://support.docusign.com/s/document-item?bundleId=gmi1660583110357\&topicId=vlb1680643208628.html) in the web form configuration. The user signs and completes the envelope.
4. If a [brand](/docs/web-forms-api/plan-integration/apply-custom-branding) is applied to the web form template or instance and the brand specifies a post-signing URL, the user is routed to that URL. Otherwise, the user remains on the Docusign platform.
5. The second user in the routing order receives an envelope email.
6. The link routes the user to the Docusign platform, which displays an envelope with an embedded web form instance. The user fills out the form fields associated with that user's view of the web form instance. The user submits the web form instance.

   The eSignature envelope is displayed, and the user signs and completes it.
7. If a brand is applied to the web form template or instance and the brand specifies a post-signing URL, the user is routed to that URL. Otherwise, the user remains on the Docusign platform.

## Instance processing: Standalone web form configurations

This diagram illustrates how an end user, your application, and the Docusign platform interact during the processing of a web form instance generated from a standalone web form configuration.

![Instance creation via the Web Forms API from a standalone configuration](/_fern-files/_img/46da59a462388da3c7d790a49dd4252cb0a943c5dc974748cbaefd683009b1c5.webp)

1. A user takes an action in your application, such as clicking a button, to start filling out a form.
2. Your application launches an [Instances:createInstance](/docs/web-forms-api/reference/webforms/instances/createinstance) API request or an equivalent [SDK](/docs/web-forms-api/sdks) method call to create a web form instance for the user to fill out. The request specifies the [web form configuration](/docs/web-forms-api/web-forms-101/concepts#web-form-configurations) from which to create the instance by referencing the configuration ID.
3. The response includes a secure, unique URL for the web form instance. See [Web form instance URLs](/docs/web-forms-api/plan-integration/instance-urls) for details.
4. Your application renders the web form instance URL. It can do this by using the Docusign JS client SDK to embed the instance in your application, or by redirecting to the instance URL. See [Render embedded web form instances](/docs/web-forms-api/plan-integration/render-instances) for details about these options.
5. The user populates the web form instance fields and submits the instance to Docusign.
6. Depending on the method your application used to render the form instance URL in step 4, Docusign issues one of these responses:

   1. If your application used the Docusign JS client SDK to render the form instance, Docusign returns a JavaScript `sessionEnd` [event](/docs/web-forms-api/plan-integration/render-instances#form-and-envelope-events) of type `formConfirmation` to your application when the user submits the web form instance.
   2. If your application redirected the user to the form instance URL, Docusign displays the [thank you page](https://support.docusign.com/s/document-item?bundleId=gmi1660583110357\&topicId=vgq1683244272836.html) defined in the web form configuration.

## Next steps

* See [Plan a Web Forms API integration](/docs/web-forms-api/plan-integration) for an overview of the implementation details that you should consider before starting work on your application.
* See the [how-to guides](/docs/web-forms-api/how-to)  for detailed walkthroughs and code examples.