This topic contains 4 replies, has 2 voices, and was last updated by  Ryan_Coleman 1 month ago.

  • Author
    Posts
  • Participant
    Ryan_Coleman
    Senior Member
    Member since: 16.07.2018
    Number of posts: 84

    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"
    }
    
    Keymaster
    Duo_Liang
    Guru
    Member since: 14.06.2018
    Number of posts: 608

    Score

    0

    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


    Duo Liang
    OneSpan Junior Technical Evangelist
    Participant
    Ryan_Coleman
    Senior Member
    Member since: 16.07.2018
    Number of posts: 84

    Score

    0

    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/<senderID>/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.

    Keymaster
    Duo_Liang
    Guru
    Member since: 14.06.2018
    Number of posts: 608

    Score

    0

    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


    Duo Liang
    OneSpan Junior Technical Evangelist
    Participant
    Ryan_Coleman
    Senior Member
    Member since: 16.07.2018
    Number of posts: 84

    Score

    0

    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!

You must be logged in to reply to this topic.