-
Notifications
You must be signed in to change notification settings - Fork 714
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
Module no longer works with Twitter free tier #463
Comments
Thanks @boogheta for your reply, but I'm not sure what you are saying. Yes, they changed all of their API access tiers earlier in the year, but I already converted my app to their new "Free" tier. The free tier worked with the v1.1 endpoints up until yesterday, and now they stopped working. I believe if this twitter module started using their v2 endpoints, it would continue working in their free tier. |
Even when I completely recreate my Twitter App, it gives me different login info, and I'm forced to use OAuth2; but even then I still get errors about trying to use v1.1 endpoints. |
I believe they kept for a long time all routes of v1.1 available but finally closed down it all yesterday. But indeed some v1.1 and v2 routes are supposed to be available with the free tiers, you can try it out. You can use the v2 endpoints by installing the 2.0-a2 release ( |
Starting today, I get this message while trying to use this library to post anything on Twitter:
twitter.api.TwitterHTTPError: Twitter sent status 403 for URL: 1.1/statuses/update.json using parameters: (media_ids=...&oauth_consumer_key=...&oauth_nonce=...&oauth_signature_method=HMAC-SHA1&oauth_timestamp=...&oauth_token=...&oauth_version=1.0&status=Today%20is%20the%20muggiest%20day%20on%20record%20in%20%23Gander%3A%2040.5.%20%23NLWx&oauth_signature=...)
details: {'errors': [{'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}]}
The text was updated successfully, but these errors were encountered: