-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug Report] Error 403 Forbidden when using GET /2/users/:id/following with Twitter API v2 endpoint #130
Comments
I'm using the basic plan (100$ monthly) and untill this morning I was able to pull the followers/followings of the user. In case anyone experiences any changes (API working) please write here. Thank you! :) |
I am having the exact same problem since today. |
We're having the exact same problem too! As of 2 hours ago. Why is the API so unstable?! |
same here |
We have the same issue. Anyone help for that!!! |
Having exactly the same issue on followers and following. I'm also using tweepy. |
Has anyone found a fix yet? |
Also getting this error Api docs are returning a 404 (https://developer.twitter.com/en/docs/twitter-api/users/follows/api-reference/get-users-id-followers) I hope this API is not getting deprecated? |
Same issue here |
Their updated documentation lacks GET /2/users/:id/following 😂 I can't believe this is an expensive paid API. https://developer.twitter.com/en/docs/twitter-api/rate-limits#v2-limits |
twitter made a mess of shit。 |
The changelog appears to be for the v1.1 API. Here is the community developer forum topic: https://twittercommunity.com/t/get-2-users-id-following-is-now-broken/197526 No solutions there either as of now. For the v1.1 endpoint you get the following on basic paid access btw, 453 code with: "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". EDIT: what am I saying 😂 , it literally says for the v2 API in the message. Probably the label is wrong 🤔 ? They even managed to break the message 🙈 . |
Twitter is crazy poor. Two api need pay $42000 a month.............. |
Has anyone found anything yet? It's been a week lol |
What's the workaround for this? I guess we'll have to scrape? |
same issue here using bearer token to authenticate: |
DId anyone find a solution? |
getting the same issue |
Same problem here. |
if you are using python tweepy, use the create_tweet instead of update_status client = tweepy.Client(consumer_key =CONSUMER_KEY, consumer_secret =CONSUMER_SECRET, access_token =ACCESS_KEY, access_token_secret =ACCESS_SECRET) client.create_tweet(text='Hello World!') |
Is there any way to attach images without using "tweepy.API" as it gives error and "tweepy.Client" does not allow to attach images. |
Anyone found a solution yet? |
Thats the solution to get total followers count and following count. |
I wasn't replying to you |
GET /2/users/:id/following I am currently experiencing a problem when using consumer_ Key and consumer_ 401 Unauthorized appears during secret authentication. Using Bearer_ Token undergoes 2.0 authentication and appears as: 403 Forbidden I am certain that all the information is correct because all other interfaces can be used normally. I'm thinking how to solve this problem? thanks |
Facing same issue with basic plan, anyone have solution yet?? |
also 403 Forbidden |
我通过第三方服务解决的验证关注者信息~~需要的话加VX cs_125569489 |
Hello, how did you solve the issue? |
|
Describe the bug
Hello,
I am currently subscribed to the $100 Basic Plan. I encountered a bug while using the Twitter API v2 endpoint with the GET /2/users/:id/following method.
When making the request, I received the following error message:
"403 Forbidden
When authenticating requests to the Twitter API v2 endpoints, you must use keys and tokens from a Twitter developer App that is attached to a Project. You can create a project via the developer portal."
I want to highlight that my app is already attached to a project, and I am not the only user experiencing this bug. Several other users are also encountering the same issue.
Please investigate this bug and take the necessary actions to resolve it as soon as possible. If you require any additional information, such as screenshots or logs, please let me know.
Thank you for your attention to this matter.
The text was updated successfully, but these errors were encountered: