Authentication Token for Signer or Sender

harishkonda | Posts: 26

Authentication Token for Signer or Sender

Friday, September 22, 2017 at 11:55am

At my work place, we are trying to get a Sender Authentication token for a package using the below information /api/authenticationTokens/sender Authorization and Accept Headers are included. In Body, in the request payload, inlcuded packageId in JSON. Getting below error { "code": 404, "message": "The requested resource does not exist on this server.", "messageKey": "error.routeNotFound", "name": "Resource Not Found", "technical": "This route does not exist." } we are on version 11.0.4 I believe. Any inputs on how to make this work? Does this Sender token, depend on the Account configuration? If we disable the login into UI for a account and still have API access, can we still use this API to get a token?

September 22 Created

January 21 Last Updated

7 years ago Last Reply

7 Replies

113 Views

2 Users

0 Likes

0 Links

harishaidary | Posts: 1812

Reply to: Authentication Token for Signer or Sender

Saturday, September 23, 2017 at 08:53am

Hi Harish, You can always generate a sender token through the API to get a session. In your request, did you include a package id? For example:

{
  "packageId": "a1UXlExmZRUs6MI8yGHwQLLyeNk="
}

Also make sure you are hitting the correct url ( https://sandbox.esignlive.com/api/authenticationTokens/sender )

harishkonda | Posts: 26

Reply to: Authentication Token for Signer or Sender

Monday, September 25, 2017 at 03:59am

I did make sure my request json has the package id as above and I am hitting the correct URI. Still getting 404 error. Is their any way to debug this problem by enabling any trace on server side to capture requests coming from specific API key or so?

harishaidary | Posts: 1812

Reply to: Authentication Token for Signer or Sender

Monday, September 25, 2017 at 02:15pm

You can use a tool like Fiddler to monitor the requests going to eSignLive.

harishkonda | Posts: 26

Reply to: Authentication Token for Signer or Sender

Tuesday, September 26, 2017 at 04:53am

Haris, I have did that already, and results are no different. {"code":404,"message":"The requested resource does not exist on this server.","messageKey":"error.routeNotFound","name":"Resource Not Found","technical":"This route does not exist."} Can you confirm or provide any references, from which version, we have this Authentication Token feature available in eSign Live?

harishaidary | Posts: 1812

Reply to: Authentication Token for Signer or Sender

Wednesday, September 27, 2017 at 07:54am

Hi there, Sorry for the late reply. I am away on a developer conference. A 404 error means that you are hitting an incorrect endpoint URL. What is the URL you are calling to?

harishkonda | Posts: 26

Reply to: Authentication Token for Signer or Sender

Wednesday, September 27, 2017 at 10:28am

Haris, As already posted, I am hitting the URI /api/authenticationTokens/sender. Once again, this is internal at our work place, in an on-premise eSign version 11.0.4.

harishaidary | Posts: 1812

Reply to: Authentication Token for Signer or Sender

Wednesday, September 27, 2017 at 01:23pm

If you're on-premise, then you will need to contact [email protected] as we have a dedicated team for on-premise. The developer community is mainly for SaaS users.

Authentication Token for Signer or Sender

Reply to: Authentication Token for Signer or Sender

Reply to: Authentication Token for Signer or Sender

Reply to: Authentication Token for Signer or Sender

Reply to: Authentication Token for Signer or Sender

Reply to: Authentication Token for Signer or Sender

Reply to: Authentication Token for Signer or Sender

Reply to: Authentication Token for Signer or Sender

Log in

Two-step verification is required