#1

When I execute the following endpoint in Postman with the API Key and API Secret Key of the app registered in the TwitterAPI Standalone Apps, an authentication error occurs.

■Endpoints

users/show

■ error message

{
    "errors": [
        {
            "code": 32,
            "message": "Could not authenticate you."
        }
    ]
}

■Postman

スクリーンショット 2021-08-13 13.50.14
スクリーンショット 2021-08-13 13.50.141228×771 61.9 KB

However, when I ran it with a TwitterAPI “standard” application created with the same account, it worked fine.

When I create StandaloneApps and try again after a day, I get the same error.

Is this a specification that the authentication error occurs after a certain amount of time has passed since the creation of the StandaloneApps?

I would appreciate any advice you can give me.

#2

By the way, if you run postman with the “Access token” and “Access token secret” of the account created in the Standalone APP, it works fine.

However, when I run postman with the “Acress token” and “Access token secret” of another account, I get the error "Could not authenticate you.
This will work correctly if you set the “API Key” and “API Secret Key” of the TwitterAPP account created in “standard”, and run postman with the “Acress token” and “Access token secret” of another account.

Only the Standalone APP is not working properly.

Thank you very much for your help and advice.

#3

Error 32 means that you are probably having issues passing along the proper keys and tokens or authorizing your request. I suggest that you make sure to check the following:

  1. you are using the proper auth keys for this endpoint, which you can identify via the endpoint’s api reference page. It might help to review our authentication section for more details on this.

  2. you have properly generated the oauth nonce, oauth_signature, and oauth_timestamp for your request.

If you have properly set up your keys and tokens, then chances are that you aren’t handling number two properly. If so, please consider using an oauth library (example), Insomnia, or try using Twurl.

#5

Thank you very much.

The token setting is not wrong as I have checked and done it many times.

So I suspect the setting on the postman side, so I ran it with the app token set to “standard” and it worked fine.

The difference is between “standard” and “standalone”.

The “standard” app was registered six months ago and has been around for a while, while the “standalone” app was just registered a week ago.

If you run the API with “Access token” and “Access token secret” of a different Twitter account than the Twitter API app account, you will get error 32.

We can only assume that this is a bug that occurs when the Twitter API has not been registered for some time.

I think it’s a specification of the Twitter API, not a setting on the part of Postman or other developers.

Thank you for your investigation.

#6

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.