chris-josongmail-com

SignDocuments() returning "error.routeNotFound"

Thursday, January 12, 2017 at 06:05am
0 votes
Trying out the SignDocuments(packageId, signerId) call in the example throws EslServerException. Additional information below: Could not create a signer authentication token. Exception: The remote server returned an error: (404) Not Found. HTTP POST on URI https://sandbox.e-signlive.com/api/authenticationTokens/signer/multiUse. Optional details: 
{"messageKey":"error.routeNotFound","packageId":null,"entity":null,"technical":"This route does not exist.","message":"The requested resource does not exist on this server.","code":404,"name":"Resource Not Found"}
My other question is, is using SignDocuments() a legitimate way to provide our end users the means to sign documents via our own UI (i.e. custom "Sign" action button) instead of going thru the embedded eSignLive iframe experience.
Approved Answer
harishaidary

Reply to: SignDocuments() returning "error.routeNotFound"

Thursday, January 12, 2017 at 07:29am
0 votes
You can get the full release notes for version 11 here: http://docs.esignlive.com/content/a_esignlive_enterprise/release_notes.htm#Release2. To will also have to contact our customer success representatives to move to version 11: [email protected] (1-888-745-2647). Note that our migration scripts are not yet ready. Therefore, you will have to start from scratch if you decide to move to version 11. Also, if you're on version 10.13, you should be using SDK 10.13 as you noticed some features are available on version 11 and not on 10.13. This will avoid running into errors like this one.
Haris Haidary OneSpan Technical Consultant
harishaidary

Reply to: SignDocuments() returning "error.routeNotFound"

Thursday, January 12, 2017 at 06:44am
0 votes
Hi Chris, What instance of esignlive are you testing SignDocuments()? This call only works on version 11 of esignlive (i.e. sandbox.esignlive.com or apps.esignlive.com). In regards to your second question, yes that is a perfectly legitimate way to sign documents. This feature is intended to work as a "rubber stamping" feature. For example, let's say a manager has 100 packages to sign. It would be cumbersome for him to go though 100 packages and sign each one manually. Therefore, this feature was introduced in the version 11 release to alleviate these kind of scenarios.
Haris Haidary OneSpan Technical Consultant
chris-josongmail-com

Reply to: SignDocuments() returning "error.routeNotFound"

Thursday, January 12, 2017 at 07:02am
0 votes
We're using sandbox.e-signlive.com / apps.e-signlive.com, the "e-" (e dash). Seems different from the URL you mentioned. Also has this version in the webpage;s footer - v10.13.12. How do we move to v11? Is there a list of breaking changes with the SDK if any? As for the ESL SDK we're using v11.0.1.0.

Hello! Looks like you're enjoying the discussion, but haven't signed up for an account.

When you create an account, we remember exactly what you've read, so you always come right back where you left off

LoginSign Up