Signing ceremony is required to collect signature or ‘Click to Sign’ option.
Tuesday, April 23, 2019 at 06:11am
Signing ceremony is required to collect signature or ‘Click to Sign’ option from user using eSign UI. When user chooses ‘Click to Sign’ option, he or she does not need to sign in signing text pad. Is it possible to pass ‘Click to Sign’ option through any API instead of starting signing ceremony and click to sign on the eSign screen?
Our scenario Steps are explained below:
1. Create package in eSign system with ‘Click to Sign’ option.
2. We create our own UI page that contains click to sign option check box. We don’t need to show any documents to customer or text.
3. User goes to our own page (not eSIgn UI) and click the checkbox to complete signature process.
4. Once user click the checkbox, we will call some eSign API to send ‘Click to Sign’ option along with required information like IP number, date signed..etc provided by esignLive.
5. ESign system will get the ‘Click to Sign’ option and embed signature in uploaded document. Later we can download signed document from eSign system.
Reply to: Signing ceremony is required to collect signature or ‘Click to Sign’ option.
Tuesday, April 23, 2019 at 07:01amHTTP Request POST /api/packages/{packageId}/documents/signed_documents HTTP Headers Accept: application/json Content-Type: application/json Cookie: ESIGNLIVE_SESSION_ID={sessionToken} Request Payload { "documents": [ { "id": "default-consent" }, { "id": "6489338764d20465" } ] }To adjust to this scenario, it would be better that if you can first let your signer choose from which signatures to sign, then create your package with only necessary signatures and programmatically bulk sign all. Or if you still want to sign per signature, for each document, you can #1 loop through to sign signatures #2 confirm the document after all required signatures are signed. This method was a little bit complex so it's better that you give your thoughts on above options before we came here. (3)For "programmatically sign on behalf of your signer" scenario, IP address would be shown as your application's and the signing date was the moment you call the API. And please always consult your legal department before you follow this solution. Hope this could help! Duo