ELI5: tweepy.errors.Unauthorized: 401 Unauthorized 32 - Could not authenticate you

[reagle]

I have a simple app that scrapes and posts to Twitter (code below), perhaps 3 or 4 times a week. It was suspended a few days ago -- though I'm not sure why. I know there's different versions of the API, and different authentication mechanisms, and all kind of Musk changes, but is it possible to have a simple app using tweepy still do these things for free?

https://github.com/reagle/thunderdell/blob/main/utils/web.py#L132

https://github.com/reagle/thunderdell/blob/main/formats/scrape/twitter.py

[Harmon758]

Create Tweets as with the former, yes.
Retrieve Tweets as with the latter, no.
See https://twittercommunity.com/t/announcing-new-access-tiers-for-the-twitter-api/188728 and https://developer.twitter.com/en/docs/twitter-api/getting-started/about-twitter-api.

[Harmon758]

You likely haven't given your app write permissions.
https://developer.twitter.com/en/docs/apps/app-permissions

Otherwise, you'll need to provide the full traceback.

[reagle]

Thank you for your patience! The environment for the app is set to "Development" and it is set to read and write.

[Harmon758]

Did you regenerate your credentials after enabling write app permissions, and are you using those regenerated credentials?

[reagle]

I believe so, I double-checked when setting it up, but mapping the tokens' names from what the twitter-dev documentation uses and what this documentation uses can be confusing (e.g., client secret is access token secret). Yesterday, I was able to do some other things with the API, so I figured those were correct. I'll have to step away for a bit and try again from the start.

[Harmon758]

The client secret is not the access token secret, and the client ID is not the access token.
You're using the wrong credentials.

https://tweepy.readthedocs.io/en/v4.14.0/authentication.html
https://developer.twitter.com/en/docs/twitter-api/getting-started/getting-access-to-the-twitter-api
https://developer.twitter.com/en/docs/authentication/oauth-1-0a
https://developer.twitter.com/en/docs/authentication/oauth-1-0a/api-key-and-secret

Those other methods are probably working because they're using endpoints that don't require you to authenticate as a user. You likely aren't even using OAuth 1.0a with them.