497 results matched your search criteria
Forum topic
OneSpan Sign
Hey,
I'm having trouble with the functionality behind saving/applying layouts in the integrated designer iframe.
Here is the flow of what is happening:
1. The REST API is used to creaete a package with one recipient that has role/id "test"
Forum topic
OneSpan Sign
I'm having some difficulty implementing DownloadDocumentsDateRange posted previously in this forum.
Forum topic
OneSpan Sign
I've been having a bit of trouble connecting to the Canadian sandbox environment. The specific error message I'm getting is: "Could not get package.
Forum topic
OneSpan Sign
Hello,
I am trying to apply a layout that is created with PlaceHolder for signers. In my package I add my real signers with email and would like to map each real signer to a placeholder in the layout. What is the best way to do this?
Forum topic
OneSpan Sign
We've been using the sandbox for testing. We use the sandbox from our development machines and a server. Everything was fine until a few weeks ago. We cannot get documents signed using the test server. I know we were able to get documents signed using the test server last December.
Forum topic
OneSpan Sign
Hi,
I'm looking for a way to add signatures to multiple documents in package in one API call instead of having to make separate calls for each individual document. We're looking to accomplish this so that we can reduce our total number of API calls to eSignLive and help our performance.
Forum topic
OneSpan Sign
Hi !
I'm trying to update a package and replace the pdf document in it, but I get this error :
Unable to update package settings. Exception: Le serveur distant a retourné une erreur : (403) Interdit. HTTP PUT on URI https://sandbox.esignlive.com/api/packages/-bANyCo4NvqdgiEPNbMG2tLdaRE=.
Forum topic
OneSpan Sign
Hello!
We've recently adopted a group recipient into our templates and now need to migrate all our templates across our other sub-production environments, with a view to then do the same into production.
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.