304 results matched your search criteria
Forum topic
OneSpan Sign
Hello,
This was working yesterday, and now I'm getting the following error. There haven't been any code changes on our end.
Using .NET SDK version 11.0.0.
Could not upload document to package. Exception: The remote server returned an error: (500) Internal Server Error.
Forum topic
OneSpan Sign
Hi Team ,
As suggested by you we are using single step package creation call where in package creation, doc upload and status sent happens at one go .For this we are using silanis provided java class.
This is wrking perfectly fine in all environments but when we moved to production , its giving conn
Forum topic
OneSpan Sign
We have below settings that we are using in SOAP now we are migrating to REST.
Please provide us exact mappings to REST service for below fields
Forum topic
OneSpan Sign
I am trying to create the package only with documents and I will need to update it later adding the signers, the signature tag is already created in one of the documents, that is why I am using EnableExtraction. I get an error:
Forum topic
OneSpan Sign
Hi Team,
We are using POST reminders api to schedule reminders. Initialy, we are creating package in DRAFT status.
Secondly, we are calling reminders POST api to set reminders.
As a response, we are getting 404 error.
Forum topic
OneSpan Sign
Our client is receiving the error message "No Role found for signer email" when trying to send a package. We are creating a custom ID however the custom ID is guaranteed to be different (one ends in -1 the other in -2).
Forum topic
OneSpan Sign
Good Morning guys,
My team and I have been working on this error for a few days now and we aren't sure why it is firing off.
Forum topic
OneSpan Sign
Hi,
I am unable to insert document with an existing package. My sandbox api key and url work fine.
Forum topic
OneSpan Sign
1. I created a function app in azure portal for the callback to download docs.
2. And then I created some transactions through the Dashboard.
3.
Forum topic
OneSpan Sign
Has anyone noticed problems with the handover URL and hash location strategy routing? If so, have you found a workaround?
When setting the handover url to something like "https://www.mydomain.com/#esign", we are seeing different behavior between the handover button and text link.