REST API

We're receiving some errors in OneSpan when we're running our batch class in Salesforce. The vast majority of records are processed but we're left with a few K that do not run and we receive the errors in the debug logs shown below.

When going through the forum, I noticed a few people have server logs that show a more in-depth error message but I'm guessing since this is being run for Salesforce we cannot access those.

Is there a way to dive deeper into these errors to try and understand where exactly this is failing?

I'm trying to send a new document in a package that has the status: Draft

But I get the error response

b'{"messageKey":"error.validation.invalidParameters","technical":"Unexpected Content-Disposition value for parameter \'name\'","message":"Invalid parameters.","code":400,"name":"Validation Error"}'

payload= {'description': 'Envio de documento para assinatura', 'id': 17, 'name': 'document1.pdf'}

url='https://sandbox.esignlive.com/api/packages/n4zLJaZblg1wd33HDVpVgsDIBlM=/documents'

We are integrating with Onespan using Rest API.

We have three types of Roles. Broker , customer and Business.

Broker first sign an agreement(using esign), followed by customer and then Business people sign an agreement.

Now we have requirement where we want to notify Broker(Signer1) when Customer(Signer2) signs and agreement via email.

Just wanted to know what is the best way to do this with Onespan.

Hi there, I'm trying to delete a document in python but I'm getting this return:

400 Client Error: Bad Request for url: https://sandbox.esignlive.com/api/packages/TAv__TLL2MOR_bMTDTnmiq0boLU=/documents/28

My company has a need to retrieve the actual signing stroke data that results from a CAPTURE type signature. It appears that this data is available already, but I cannot find documentation for the format of that data.

In the data returned by /api/packages/{packageId}, the key available at .documents[].approvals[].fields[].value contains what looks like a base64-encoded binary format.

At one point I found code that can convert images into this format, but no explanation how to read the format itself.

Is there anything OneSpan can provide to help read the data?

As described in this post https://community.onespan.com/documentation/onespan-sign/guides/sender-guides/user/configuring-recipients  we can configure some "personal message" for the Recipient. Just want to know where this "personal message" gets used. will thi be part of “$PACKAGE_MESSAGE;” field if we use in email template https://www.onespan.com/blog/onespan-sign-developers-email-templates-part-1 . or is it used for any other purpose. Kindly clarify. I have attached example also

We are facing this issue intermittently in production.

We have a grid on our template which includes set of `Country Code` and `Phone Number` fields. 

The issue is - after package is signed and completed, API call that returns document approval object, has Country Code populated with last 4 digits from Phone number field. But the PDF of the signed document has "1" populated in the Country Code (shown in the screenshot 1). Country code is an editable field and is populated with "1" by default.

We have integrated with Onespan using REST API. Just wanted to check , If it is possible to add additional recipients in CC, not as signers, but as viewers only. E.g. make sure everyone listed as an additional recipient gets a copy of it when the transaction complete. is there anyway to achieve this ?

We have been using oneSpan for around 2 years now and we weren't facing any issues with adding documents to a package but recently when we're trying to add certain pdfs, we are getting an error - "The number of Pre-Verify results does not match the number of documents that were sent for verification"

Hi there,

I've been finishing through all the threads and guides but not sure what was wrong with my code. Please see attached txt file & screenshots.

I've used logic apps to convert the PDF file to base64 then base64tobinary.

Our objective is to use Logic App to create & send packages, however, we've are stuck at adding documents to package step.

---------------------------------------------------- 

Error message:

<html>

<head>