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?
Reply to: Authentication Token for Signer or Sender
Saturday, September 23, 2017 at 08:53am{ "packageId": "a1UXlExmZRUs6MI8yGHwQLLyeNk=" }Also make sure you are hitting the correct url ( https://sandbox.esignlive.com/api/authenticationTokens/sender )Reply to: Authentication Token for Signer or Sender
Monday, September 25, 2017 at 03:59amReply to: Authentication Token for Signer or Sender
Monday, September 25, 2017 at 02:15pmReply to: Authentication Token for Signer or Sender
Tuesday, September 26, 2017 at 04:53amReply to: Authentication Token for Signer or Sender
Wednesday, September 27, 2017 at 07:54amReply to: Authentication Token for Signer or Sender
Wednesday, September 27, 2017 at 10:28amReply to: Authentication Token for Signer or Sender
Wednesday, September 27, 2017 at 01:23pm