REST API

SSO PROBLEM, I explain the problem to you :

in the code, the method that causes the error is (createPackageOneStep) in line : packageId = eslClient.createPackageOneStep(documentPackage); knowing that (documentPackage) contains all the information related to the demand, including the signatories.

What is causing this error?

It’s the type of authentication of the signatory:

We are using the completion report API to retrieve the completed transactions from all senders.  Using this (/api/reports/completion?status=COMPLETED&from=2020-03-01&to=2020-05-13), service did not return all of the senders (only 49 out of 146).  It also did not return all completed transactions for each sender.  We have received a lot of transactions in the last couple month, more than 10k.  The service only returned 100 transactions.

Hi,

Is there an API for re-sending the signing completion email to the signers?  The email with a link to download the completed documents.  Thanks!

Hi,

I understand additional fields can be put in the CSV for bulk send to populate custom data into a transaction by adding extra columns that map to fields in the template. Is there a limitation on the number of fields for each row in the CSV?

If there is a limitation is it per signer or is it for the whole row? I.e. if multiple signers and a limited amount of fields allowed is that split between signers since all on the one row for one transaction.

Hi,

I have signed on behalf of client using Bulk Sign feature . When i retrieve evidence summary document its showing my IP in that document. Is than anyway possible to pass Client Ip since we are signing on behalf our client and get their IP in evidence summary document.

Hi ,

is it possible to sign the document on behalf of client when client agrees to digital consent.

Guys,

I am creating a package with a notary that will have multiple signers. 

I noticed that if I include a handover, once signer one has finished signing, the pop up comes up giving that user to exit or continue. Since there are still signers and a notary left to sign, how do we get that popup with the options to leave to not come up? We do not want the users navigating away from the signing experience.

Hi there,

Please see the link below.

https://community.onespan.com/documentation/onespan-sign/guides/feature-guides/developer/signer-management

We currently use REST API to integrate with OneSpan.

In the Response Payload, it has a 'delivery' object which has three attributes 'provider'/'email'/'download'.

  i.e.

Guys -

Since we are not sending a document up for a smart note, it's being automatically generated from the data and enote data sections, how do we go about adding one to an existing transaction that is already up in OneSpan?

Logically, I would think we could just remove the smart note and then resend and updated package with the data and enote data sections filled out but that doesn't seem to work in my case. Any ideas?

Getting the below error for the url path-  https://sandbox.esignlive.com/api/packages , https://apps.esignlive.com.au/api/packages.

ORA-29273: HTTP request failed
ORA-06512: at "SYS.UTL_HTTP", line 1130
ORA-29024: Certificate validation failure

Earlier the integration code was running fine for both the url's. The certifcate screenshot is attached for your reference.