Get Signing Status directly

OliverH | Posts: 28

Get Signing Status directly

Thursday, March 14, 2019 at 06:00am

Hey team, I noticed that you provide a signing status function to get signing status per signer: com.silanis.esl.sdk.SigningStatus signerStatus1 = eslClient.getSigningStatus(packageId, new SignerId(signerId1), null); But the concern here is, we don't want multiple calls to get signing status all recipients. We are looking for a way returning all signing status for each signer directly. Any ideas on this? Thanks,

March 14 Created

January 21 Last Updated

3 months ago Last Reply

3 Replies

98 Views

4 Users

0 Likes

0 Links

Duo_Liang | Posts: 3777

Reply to: Get Signing Status directly

Thursday, March 14, 2019 at 07:59am

Hi Oliver, OneSpan Sign provides you with the capability to use a Webhook to push notifications to your callback listener vs you actively polling information. The proper solution to your issue would be to set up a callback listener and subscribe to the events for "Recipient completed signing". This way, you'd be able to update your application with statuses in real time. You could then only poll every 12 or 24 hours as a backup, in case of missed callbacks. Hope this could help! Duo

Chuck.at.Gaston | Posts: 13

Reply to: Get Signing Status directly

Wednesday, March 26, 2025 at 10:09am

The signerId1 is 'signer1'. I get an error when I try the method from above: "new SignerId(signerId1)"

If I enter in the signer id that I retrieved from the API for this signer1, it works fine:
OneSpanSign.Sdk.SigningStatus signerStatus0 = OssClient.GetSigningStatus(packageId, "a48234e3-d2cd-4208-8647-43b8eb762c7c", null);

How do I get the "new SignerId(signerId1)" to work?

daman | Posts: 1

Reply to: Get Signing Status directly

Wednesday, April 16, 2025 at 03:15pm

Hi Chuck,

When adding signer in transaction you can specify a custom signer id such as signer1 using the method withCustomId(). In case this is not specified then a random signer id is assigned by the system which is unique ID per transaction. In later case you will need to always retrieve the signerid as it is randomly generated every time the signer is added to transaction.