319 results matched your search criteria
Bad Request 400 eslClient.CreatePackage() after upgrade from 10.3 to 10.13
Forum topic
OneSpan Sign
Hello, I recently updated the api version for Silanis.ESL.dll from 10.3 to 10.13, after doing so the code that I'm using to dynamically build the packages for getting signed no longer works.
Simulating REST workflow using SOAPUI
Forum topic
OneSpan Sign
Hi, thanks Haris for your input, my next step is to simulate the workflow and working on a POC using SOAPUI ( a freeware I use to test REST services ). The workflow is straight forward: 1. Create a Package and Send the PDF . Read the Response PackageId 2.
Extracted Field Formatting
Forum topic
OneSpan Sign
Hi, Regarding using FieldBuilder for text field extraction for the creation of inputs from PDF forms...
Mouse capture error
Forum topic
OneSpan Sign
Hello, would help me understand what I'm doing wrong ? The method is called in package creation process. In the following are the values for Mobile signature method compare with Mouse capture. I don't see any problem for Mobile signature. // Mobile signature - Error response String response = clie
Package Create
Forum topic
OneSpan Sign
Hi We are able to create the package but the status was not changing to SENT. below is the sample request we are using to create the package and then updating the status.  
Error when trying to upload documents to an existing package
Forum topic
OneSpan Sign
Guys, I have an existing transaction that I am trying to add documents to. Below, you'll find the json package that I am sending up with the files. I am getting this error when trying to upload those files.
Unable to add document to a package
Forum topic
OneSpan Sign
I am trying to add documents to a package but unable to do so. I have tried two method:
Specifying Sender of Package
Forum topic
OneSpan Sign
Hi there. What I'm trying to do is specify the sender of a package to be [email protected].  Our main account owner is [email protected]. No matter how I update my JSON, the package sender is still [email protected].  Here is my pertinent JSON package
Pkg ID vs Signer ID etc
Forum topic
OneSpan Sign
The “packageID” seems fine, works for other API call but “SignerID” from Evidence Summary does not seem to be recognized. Its confusing as items are referred to by multiple names, e.g. PackageID appears to be the same as Signing CeremonyID and Transaction.