Integrate WebSign by URL redirection



For integrating signing into your application, our recommendation is to redirect directly to Bulksign for the signing part and configure it to redirect back to your website/application afterwards.

Important!

The other option is to "host" WebSign in an iframe in your application . The problem with this approach is that web browsers are blocking 3rd party cookies by default, so this approach requires workarounds to work correctly.

Here are the steps needed for this type of integration :

  • after sending the envelope, you can obtain the signing URL for the current signer(s) from the SendEnvelope response. It contains the URL in a property called "SigningUrl". Redirect to that url to allow signing.

  • to redirect back to your web application after signing, you need to configure the redirect url :

a) If you are developing a "global" / per organization integration which requires the same redirect for all signers, this can be configure from Settings \ Signing. The option name is "Allow signer to download documents after signing is finished". Choose "Redirect" and enter the redirect url.

b) If you need to configure this redirect at the envelope level, this can be done when sending the envelope with the SendEnvelope API.

Sample code : 

            envelope.OverwriteSignSettings = new SignSettingsApiModel()
            {
                DocumentDownload = SignerDownloadDocumentActionTypeApi.RedirectToUrl,
                DocumentDownloadRedirectUrl = "https://your_website_here.com"
            }

Please see this Github sample code which highlights this type of integration.