Skip to content
This repository has been archived by the owner on Aug 7, 2024. It is now read-only.

Endpoint Access, Is this an issue with the script or with Twitter changing something? #722

Open
stephen-calm opened this issue Jul 12, 2023 · 2 comments

Comments

@stephen-calm
Copy link

status = api.PostUpdate('I love python-twitter!')

twitter.error.TwitterError: [{'message': 'You currently have access to a subset of Twitter API v2 endpoints and limited v1.1 endpoints (e.g. media post, oauth) only. If you need access to this endpoint, you may need a different access level. You can learn more here: https://developer.twitter.com/en/portal/product', 'code': 453}]

@JohnKun136NVCP
Copy link

JohnKun136NVCP commented Jul 28, 2023

May your code is not wrong, I've been same issue, but it's about Twitter's API since if your check this link, you will see that you have to pay to get new environments for your App is working.
It's my app but it's free so if you see:
image

And my endpoints (free plan):
image
So if my code is this, it'll be same issue

api = tweepy.API(auth)
statuses = api.home_timeline()
for status in statuses:
    print(statuses.user.screen_name)

With $100 USD per month (Basic plan):
image

@jeremad
Copy link

jeremad commented Aug 14, 2023

Seems like the 1.1 API to post tweets is not a free API anymore, we should switch to the v2 API:

https://twittercommunity.com/t/understanding-the-error-453-you-currently-have-access-to-a-subset-of-twitter-api-v2-endpoints/200361

They published an example, the interesting part is after line 51:
https://github.com/twitterdev/Twitter-API-v2-sample-code/blob/main/Manage-Tweets/create_tweet.py#L51

adilosa added a commit to adilosa/awswhatsnew that referenced this issue Nov 22, 2023
python-twitter appears to not handle the new twitter v2 changes,
example usage from twitter is to just call the api directly

bear/python-twitter#722
https://github.com/twitterdev/Twitter-API-v2-sample-code/blob/main/Manage-Tweets/create_tweet.py#L51

which didn't work, so switched to Tweepy which is working.

Additionally the new rate limits don't like the bot bulk-posting a whole
update at once, so adjusted to just exit if we hit a rate limit. The
dynamo cache should make sure we don't miss a post or repost.

Last, the API apparently somehow now doesn't support tweets longer than
280 chars at all, so making sure we stay under budget
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants