Skip to main content
arrow-left Back to Docusign.com
Question

Connect Event for Browser Closed

  • February 19, 2025
  • 1 reply
  • 23 views
A
Newcomer
Forum|alt.badge.img

I am working on a PoC for Integration with Docusign and using Embedded Signing with Focussed View because we have our website and don’t want Admins to go out of application context.

I have 2 options to display the document to end user 

  1. Load the document in the same application window by loading DocusignJS and passing it RecipientViewURL and ClientId.
  2. Cross Launch the RecipientViewUrl obtained by making CreateEnvelope and CreateRecipientView API calls.

For my integration, I am making Docusign eSignature API calls from a backend service and passing on the URL to the frontend portal.

I am also working on using Connect APIs to receive a callback when Envelope event is raised (completed, voided and declined). 

I want to understand

  1. What event is raised when the enduser views the Document but
    1. Does not perform any action and the URL expires.
    2. Close the browser without taking any action
  2.  If there’s no connect event raised, how can we handle the case when end user performs above actions and take appropriate actions.

 I believe the Envelope expiry is 120 days by default but the generated URL is one time view and TTL is 5 mins. 

Does the TTL (5 mins) for generated RecipientView URL start immediately after it is created or after it is opened?

 

1 reply

B
Docusign Employee
Forum|alt.badge.img+7
  • Byungjae.ChungDocusign Employee
  • Docusign Employee
  • 65 replies
  • February 21, 2025

> Does not perform any action and the URL expires.
No Connect event will be raised as the envelope or recipient status hasn't changed. In this case, you would need to call CreateRecipientView API again to get the new URL.

> Close the browser without taking any action
If the recipient opens the signing view but close the browser without taking any action, the "recipient-delivered" event is sent to your listener. However, this event is typically triggered when the Continue button is selected in an eSignature workflow. Note that, if Electronic Record and Signature Disclosure (ERSD) is required by your account, this event will only trigger after the user agrees to the ERSD, because the Continue button will not be selectable until that time.

More information about the Connect event type is here: https://developers.docusign.com/platform/webhooks/connect/event-triggers/

 

> If there’s no connect event raised, how can we handle the case when end user performs above actions and take appropriate actions.
In this case, you would need to call GetEnvelope API (https://developers.docusign.com/docs/esign-rest-api/reference/envelopes/envelopes/get/) to check the status of the recipient before proceeding.

More information about getting an update in an embedded signing workflow is here: https://www.docusign.com/blog/developers/the-trenches-real-time-updates-embedded-signing-workflow

 

> Does the TTL (5 mins) for generated RecipientView URL start immediately after it is created or after it is opened?
The TTL for the recipientView URL starts immediately. So you would need to open this URL within 5 mins. 

Reply


Most helpful members this week

Code of Conduct

Docusign Community

Code of Conduct