Creating signing ceremony for in-person signers using REST API

Hi there,

To do so:
(1)create a package with in-person setting enabled, check the Signing Ceremony Settings Guide.

(2)you may already know that you can build two types of links to access Signing Ceremony #1 signing URL #2 link built by signer authentication token. I have a blog series talking about the differences of these two. Among them, with in-person signing turned on, the #1 will still lead signer to remote signing (you can choose whether to send the remote signing email, and the link behind the email is signing url), so in order to kick off the in-person signing session, you'd use #2 link, check below steps.

(3)retrieve a signer authentication token (multiple or single use). Could be any of the signer, or sender if you preferred since the person is fixed

(4)build the link https://sandbox.esignlive.com/access?sessionToken={signerAuthToken}

Note: New Signer Experience currently doesn't work with above steps. There's a ticket reporting this already.

Duo

An update for the in-person signing with NSC (New Signing Ceremony) that the issue is fixed now, but ONLY sender's authentication token can used to kick off the in-person signing ceremony. (in classic SC, any signer's authentication token works)

Duo

Hi Duo,

I created the InPersonSigning package with API to set "InPerson"=true, when I get authentication token and tried to manually launch the signing via https://sandbox.e-signlive.ca/access?sessionToken={signerAuthToken}, I don't see the InPerson signing option in the NSE. what's the correct way to show InPerson signing option in the NSE

thanks,

Cindy

Hi Cindy,

Kindly refer to my reply to your another post. It's probably because you used a signer authentication token in above link. Please notice that, in NSE, only signing links built with sender authentication token or sender's signer authentication token allows to kick off an in-person signing ceremony.

Duo