1540 results matched your search criteria
Forum topic
OneSpan Sign
Using REST API to create the package along with the documents and return a response package id. After that, we initiate a REST API signerAuthenticationToken passing packageId and email address of the signer which then redirect to an iframe to begin the signing ceremony.
Forum topic
OneSpan Sign
Hello Team,
I am using "https://sandbox.esignlive.com/api/packages/" to create request on EsignLive.
after successful call we received email from eSignLive to sign this document we open email to sign this document.
then we have requirement from client to move our signatory box which we set using
Forum topic
OneSpan Sign
I'm trying to add a role to an existing package in draft status.
Forum topic
OneSpan Sign
Hello,
I am working with .NET SDK. Currently according to my requirement I need to change my enforceCaptureSignature to true for allowing user for multiple time signing. While searching for solutions I found "https://sandbox.esignlive.com/api/packages/{packageId}".
Forum topic
OneSpan Sign
Hi.
I have just started working with the API and the .NET SDK, because I wasn't able to add another signer from the sandbox WEB UI to a recently created transaction.
This just occurs when one or more of the recipients have already signed the document.
Forum topic
OneSpan Sign
I have registered http://xyz.com/dir/api/CallbackLog/Log as callback Url on account page.
I have also created API controller method
public static void Log(CallbackLogModel model)
{
.........
}
where model is JSON model I expect to be posted to the specified url.
Also based on your documentatio
Forum topic
Intelligent Adaptive Authentication
I'm testing out the API calls against my sandbox and trying to trigger the "2 Different IP Countries in 1 hour" rule, but I seem to be missing a step. These are the steps I tried.
Forum topic
OneSpan Sign
Can one use the API to upload an excel document with tags in it?
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.