Notary Integration

Ryan_Coleman | Posts: 258

Notary Integration

Thursday, December 20, 2018 at 05:00am

Guys, We are in the process of setting up accounts and we have a few where Integration is not set. Is feature needed for any account that will have API calls ran against it? I am trying to generate an auth token for one of these users and I am getting this error below.

{
    "messageKey": "http.status.405",
    "technical": "",
    "packageId": null,
    "messageLanguage": null,
    "entity": null,
    "parameters": {},
    "message": "Method Not Allowed",
    "code": 405,
    "name": "Method Not Allowed"
}

December 20 Created

January 21 Last Updated

6 years ago Last Reply

4 Replies

85 Views

2 Users

0 Likes

0 Links

Duo_Liang | Posts: 3777

Reply to: Notary Integration

Thursday, December 20, 2018 at 06:19am

Hi Ryan, A quick question for you, which workflow are you following to generate the Auth Token for your user? Did you first retrieve their API Key then generate the User Authentication Token? Which API are you calling caused this 405 error? Normally, it's because of the wrong REST method you used, etc, POST vs PUT/GET, so please make sure you are using the correct API. Hope this could help! Duo

Ryan_Coleman | Posts: 258

Reply to: Notary Integration

Thursday, December 20, 2018 at 06:53am

Duo, Here is my workflow for when getting this error. The API calls we are hitting are production because that is where these users were created. I start with this call, using our API key to get the senders associated with our account. https://apps.esignlive.com/api/account/senders This is a GET API call. I then take the sender's ID from that list and hit this api call to get the apiKey. https://apps.esignlive.com/api/account/senders//apiKey This is another GET API call. This works. It gives me the API key of the sender. I then take that API key and I use this call to get the auth token, using that sender's api key. https://apps.esignlive.com/api/authenticationTokens/user This is where I am getting the 405 error mentioned above.

Duo_Liang | Posts: 3777

Reply to: Notary Integration

Thursday, December 20, 2018 at 07:55am

Hi Ryan, I tested on your workflow and it works fine at my side. Please make sure the last API is a POST call:

POST https://apps.esignlive.com/api/authenticationTokens/user

with your user's API KEY as Authorization in the request header. Duo

Ryan_Coleman | Posts: 258

Reply to: Notary Integration

Thursday, December 20, 2018 at 09:12am

Duo, I checked all of the calls and yes, I was doing a POST call on the last one. After coming back from lunch, I ran the same calls again and this time they worked. Not sure what that is about but it is now functioning as expected! Thanks!