Hello, I need to send multiple documents, I saw this post: https://community.onespan.com/forum/adding-multiple-documents-meta-data And in this post it informs that it would not be possible, but it is from 2018, is there any current solution for this?
This is the payload I'm using:
Hello. This is not working. I tried below code and get this error message. I am trying to download an in progress transaction since this cannot be done in the UI. I tried the below code but am getting the below error message. Can you please advise how to fix this issue and run the code correctly?
Error Message:
{"messageKey":"http.status.406","message":"Not Acceptable","code":406,"name":"Not Acceptable"}
Hi, I am sending the following request:
We are in process of replacing SDK with REST
We have following scenario with SDK where we give signer email and retrieving signer details as below shown JSON object
[ { "signerStatus": { "signerID": "string", "email": "string", "status": "string", "statusReason": "string", "statusDate": "string", "signerDocumentStatuses": [ { "documentID": "string", "name": "string", "status": "string" } ] } } ]
If the 'Signing completed' or email.complete is scraped for the Download link - it doesn't directly download the package. Instead, it opens the OneSpan link which has a Download button when clicked downloads the package. But, using the email link - is it possible to craft a direct download link (when opened just downloads the file)? Is it possible with the transaction and loginToken? I'm asking because scraping the email and generating the link is faster and more ideal than doing via API (an additional JSON post page doesn't have to be crafted, we can just generate the link).
Hi
Is it possible to declare during the package creation instance that an extra file should be attached after signing the package documents? The package status automatically changes to COMPLETED after uploading the extra file or should I force the status to COMPLETED by API?
Regards
Gabriel
We are in process of changing SDK to REST in our project
Need help mapping the SDK methods to REST, In SDK add document we have SignatureFields, Signature Editable fields, Initial Fields and AcceptanceFields?
Could you provide us a sample REST AddDocument request covering all above fields?
Attached is our internal request that we are using for creating document in SDK, it would be great if we get mapping for the same.
We are in process of changing OneSpan SDK to OneSpan REST and have different operations like AddDocument, PackageCreateAndSend, UpdateDocument etc.
Can we get some good document or any references that helps our development?
As we are really facing issue in mapping the document fields from SDK to REST, noticed different field property changes and format as well.
Please help!
We are in process of changing OneSpan SDK to OneSpan REST
In SDK we are retrieving the status using GetSigningStatus(objPackageId, signerId, null) which giving us 'InActive' status as output.
REST we are using below URL to get the Signing Status
https://sandbox.esignlive.com/api/packages/{PackageID}/signingStatus?signer=signerId which giving us 'Draft' status as output.
Any ideas on this? Thanks
We are attempting to make fields read only in our OneSpan package. We are trying to use the API to mark them. We cannot find the way to mark dates read-only.
The preference would be to mark them read only using the API, so that they all work similarly.
We are actually attempting to bypass setting the fields within the PDF and marking them read only via the payload.