> 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

# Redirect users after form submission

> Learn about options for a Web Forms API integration to display a page to inform users that their information has been submitted successfully.

> **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.

After a user submits a [web form instance](/docs/web-forms-api/web-forms-101/concepts#web-form-instances), your application should direct their browser to an appropriate page to inform the user that their information was successfully submitted.

The mechanism for doing so depends on which of these options your application uses to [render or deliver web form instances](/docs/web-forms-api/web-forms-101/when-to-use-embedded-or-remote-delivery):

* [Docusign JS](/docs/web-forms-api/plan-integration/redirect-users-form-submission#form-submission-when-rendering-with-docusign-js)
* [Redirection to the Docusign platform](/docs/web-forms-api/plan-integration/redirect-users-form-submission#form-submission-after-a-redirect-to-the-docusign-platform)
* [Remote delivery](/docs/web-forms-api/plan-integration/redirect-users-form-submission#redirects-for-remote-web-form-instances)

## Form submission when rendering with Docusign JS

If your application uses the [Docusign JS](/docs/web-forms-api/plan-integration/render-instances#use-docusign-js-to-render-web-form-instance-urls) client SDK to render [web form instances](/docs/web-forms-api/web-forms-101/concepts#web-form-instances) in an embedded iframe, you should implement listeners to detect [events](/docs/web-forms-api/plan-integration/render-instances#form-and-envelope-events) that indicate when a form submitter has finished their tasks. When the relevant event is triggered, your application can route the user to another page in your web application. See [Form and envelope events](/docs/web-forms-api/plan-integration/render-instances#form-and-envelope-events) for details about the events your application should use to trigger a redirect.

## Form submission after a redirect to the Docusign platform

If your web application redirects users' browsers to the Docusign platform for the display of [web form instances](/docs/web-forms-api/web-forms-101/concepts#web-form-instances), page display options after form submission depend on the [type of web form configuration](/docs/web-forms-api/plan-integration/retrieve-configuration-details#web-form-configuration-type) that is used to generate web form instances. See the next sections for details.

**Instances generated from template-based configurations with embedded signing**

In this scenario, web form instances are generated from a [template-based](/docs/web-forms-api/web-forms-101/instance-processing#instance-processing-template-based-web-form-configurations) web form configuration, and the configuration's [Initiate signing session from email](https://support.docusign.com/s/document-item?bundleId=gmi1660583110357\&topicId=bna1674685085797.html) setting is not enabled. This means that the [envelope](/docs/web-forms-api/web-forms-101/concepts#esignature-envelopes) generated on web form instance submission is displayed in an *embedded signing* view within your web application. To redirect users' browsers after envelope completion, your application can supply a [returnUrl](/docs/web-forms-api/reference/webforms/instances/createinstance#schema__createinstancerequestbody_returnurl) in the [Instances:createInstance](/docs/web-forms-api/reference/webforms/instances/createinstance) API request or an equivalent [SDK](/docs/web-forms-api/sdks) method call that creates a web form instance. If you do not supply a `returnUrl`, the web form configuration [thank you page](https://support.docusign.com/s/document-item?bundleId=gmi1660583110357\&topicId=vgq1683244272836.html) is displayed after users complete envelopes.

**Instances generated from template-based configurations with remote signing**

In this scenario, web form instances are generated from a [template-based](/docs/web-forms-api/web-forms-101/instance-processing#instance-processing-template-based-web-form-configurations) web form configuration, and the configuration's [Initiate signing session from email](https://support.docusign.com/s/document-item?bundleId=gmi1660583110357\&topicId=bna1674685085797.html) setting is enabled. After submitting a web form instance, a user accesses the [envelope](/docs/web-forms-api/web-forms-101/concepts#esignature-envelopes) on the Docusign platform via an emailed link (a process known as *remote signing*).The user is not routed elsewhere after signing, unless the [web form template](/docs/web-forms-api/web-forms-101/concepts#web-form-templates) is associated with a brand that specifies a post-signing destination. See [Destination URLs for Post-Signing Navigation ](https://support.docusign.com/s/document-item?bundleId=pik1583277475390\&topicId=tad1583277330037.html) for more information.

**Instances generated from standalone configurations**

For web form instances generated from [standalone](/docs/web-forms-api/web-forms-101/instance-processing#instance-processing-standalone-web-form-configurations) web form configurations, form instance submission does not generate an envelope. After form submission, Docusign displays the [thank you page](https://support.docusign.com/s/document-item?bundleId=gmi1660583110357\&topicId=vgq1683244272836.html) defined in the web form configuration. In the current release, there is no option to redirect users to another URL.

## Redirects for remote web form instances

Redirects after submission for [remote web form instances](/docs/web-forms-api/plan-integration/deliver-remote-instances-to-users) are supported through the [branding](/docs/web-forms-api/plan-integration/apply-custom-branding) feature. A redirect works only if the [web form template](/docs/web-forms-api/web-forms-101/concepts#web-form-templates) or instance is associated with a brand, and that brand has a post-signing URL configured. A brand associated with a web form template will be applied by default to all web form instances created from that template. A brand supplied in an [Instances:createInstance](/docs/web-forms-api/reference/webforms/instances/createinstance) request overrides a brand associated with a web form template. Without a brand that includes a post-signing URL, a remote web form instance will redirect to a static, Docusign-branded page.

To configure a post-signing URL in a brand:

1. In your Docusign account, select **Admin**, then from the left nav, choose **Brands**.
2. Create a new brand; or select the brand you want to apply and choose **Edit** from the brand’s kebab menu; then, under **Advanced Configuration,** choose **Destination URLs.**
3. In the **Signing Completed** field, add the destination URL to which you want users routed after they complete the remote web form instance and envelope.

![Destination URL](/_fern-files/_img/4d373c68a2272d7f33c8514e0e61137348ba2e2f53a6347019ff3edb9efa76c0.webp)

When the brand is applied to a web form template or instance, the **Signing Completed** URL from the brand’s configuration determines the redirect destination. See [Apply custom branding](/docs/web-forms-api/plan-integration/apply-custom-branding) for more information about how to associate a web form template or instance with a brand.

## Next steps

* See [Web form instance processing](/docs/web-forms-api/web-forms-101/instance-processing) for an overview of the interaction between a user, a Web Forms API integration, and the Docusign platform.
* Review the process to [deliver remote web form instances via email](/docs/web-forms-api/plan-integration/deliver-remote-instances-to-users).
* See the options for [rendering embedded web form instances](/docs/web-forms-api/plan-integration/render-instances).