Sudipta

Callback endpoint while creating eSignLive package using Java SDK

0 votes
Hello Can anybody please help is finding a way to specify a callback endpoint while creating eSignLive package using Java SDK? Thanks Sudipta

Reply to: Callback endpoint while creating eSignLive package using Java SDK

0 votes
Hi Sudipta, What would be the reason for this? Callback notifications are on an account level and if you change the endpoint for every package, then you run the risk of missing a big chunk of them.
Haris Haidary OneSpan Technical Consultant

Reply to: Callback endpoint while creating eSignLive package using Java SDK

0 votes
We wanted to set the callback at package level so that we can setup custom query parameter (say, ) which will be unique for a package. We need this parameter (id) to be appended to the callback url so that we can uniquely identify the package in the response. We do not save the packageid in our DB. So, only way we can identify a package in callback is by the unique value of the parameter appended to callback url. We are using the following code to generate the package. We are expecting PackageBuilder to provide us a way to set the callback url while creating the package. Document document = new Document(); document.addSignatures(signs); document.setContent(DatatypeConverter.parseBase64Binary(); document.setName("TestDocument"); document.setFileName("TestDocument.pdf"); DocumentPackageSettings settings = DocumentPackageSettingsBuilder .newDocumentPackageSettings() .hideOwnerInPersonDropDown() .withoutDocumentToolbarDownloadButton() .withoutDialogOnComplete() .withoutCaptureText() .withDecline() .withoutInPerson() .withoutOptOut() .withoutOptOutOther() .withoutWatermark() .withoutDialogOnComplete() .withoutLanguageDropDown() .withCeremonyLayoutSettings(CeremonyLayoutSettingsBuilder.newCeremonyLayoutSettings() .withoutNavigator() .withoutGlobalNavigation() .withoutBreadCrumbs() .withoutSessionBar() .withoutTitle() .withoutIFrame() .withoutGlobalConfirmButton() .withoutGlobalDownloadButton() .withoutGlobalSaveAsLayoutButton() .withLogoSource(null)) .build(); PackageBuilder packageBuilder = newPackageNamed("uSign Transaction " + format.format(new Date())) .withSigner(newSignerWithEmail(email) .withCustomId(uSignId.toString()) .withFirstName(signerFirstName) .withLastName(signerLastName)); final DocumentPackage documentPackage = packageBuilder.withDocument(document).withSettings (settings).build();

Reply to: Callback endpoint while creating eSignLive package using Java SDK

1 votes
The callback notification feature is on an account level. That cannot be changed. However, what you can do is store the parameter in the package as attributes. Hence, when you receive the callback notification, you simply use the package id returned by esignlive to retrieve the package attribute and match it with your application. Here's a guide on how to add package attributes: https://developer.esignlive.com/guides/feature-guides/package-attributes/
Haris Haidary OneSpan Technical Consultant

Reply to: Callback endpoint while creating eSignLive package using Java SDK

0 votes
Thanks for the information Haris. It was really helpful. Can you also share an example of setting the callback url at account level? Regards Sudipta

Reply to: Callback endpoint while creating eSignLive package using Java SDK

0 votes
Sure :) https://developer.esignlive.com/guides/feature-guides/callback-notifications/
Haris Haidary OneSpan Technical Consultant

Reply to: Callback endpoint while creating eSignLive package using Java SDK

0 votes
Thanks Haris. I got all my questions around callback answered. Regards Sudipta

Hello! Looks like you're enjoying the discussion, but haven't signed up for an account.

When you create an account, we remember exactly what you've read, so you always come right back where you left off