578 results matched your search criteria
Forum topic
OneSpan Sign
Hi , i am trying to create a package using the rest API with sandbox url : https://sandbox.esignlive.com/api/packages.
Forum topic
OneSpan Sign
When I use the .NET SDK version 11.5, I'm have a problems getting the signerId of package signers.
What I want to do is this:
call the eslClient.GetPackage(packageId) method to get information about an existing package
get an authorization token, by SignerId, for a signer from
Forum topic
OneSpan Sign
Hi, I'm trying to set up a demonstration project using the sandbox environment but I'm having troubles authenticating with the API.
I initially used the .NET SDK to access the sandbox but when I hit troubles I decided to try and distill the problem down.
What I'm observing is that my first attempt
Forum topic
OneSpan Sign
Hi,
I get 400 error code.
I have the sample code below:package RestAPI;
import java.io.BufferedReader;
import java.io.File;
import java.io.IOException;
import java.io.InputStreamReader;
import java.io.OutputStream;
import java.io.OutputStreamWriter;
import java.io.PrintWriter;
import java.net.Htt
Forum topic
OneSpan Sign
While attempting to upload a document to a package via the following call: https://sandbox.esignlive.ca/api/packages/9uPhYzkvKRJXmdxv4Bje_7gz9Ls=/documents
I am presented with the following error:
POST https://sandbox.e-signlive.ca/api/packages/9uPhYzkvKRJXmdxv4Bje_7gz9Ls=/documen
Forum topic
OneSpan Sign
Hi,
I am getting below error while creating the package
Forum topic
OneSpan Sign
Hi,
I am trying out the Text Tags for configuring the signing over the API and getting this error as I try to create the package and send.
Forum topic
OneSpan Sign
Hello,
I am not sure if this is an issue with the APEX SDK, REST API, or bug in eSignLive. We are using the APEX SDK to create the package + documents in one call from a custom Salesforce page.
Forum topic
OneSpan Sign
Hi,
This issue popped up in the last couple of weeks in our testing Sandbox environment. We've been using Text Anchors to configure all our signatures, so we have a FULLNAME block, and a corresponding Date signed that gets auto-populated on signature.