I'm using the twitter api to get data on many twitter accounts, because of the rate limit and since i can't ask the owners of all those twitter accounts to authenticate, i've to create several applications on my developer account
(note that i'm already queuing and combining requests, i've used all best practices).
My question, what's the maximum number of applications allowed per developer account? i didn't manage to get this answer anywhere on the web nor on the twitter documentation
Mentioned in 24 July 2018 twitter announcement, The limit is 10 apps per dev account.
We’re also limiting the default number of apps you may have registered
by a single developer account to 10. Developers who need to register
more than 10 apps — for instance, to enable client-specific products
which require distinct apps — can request permission using the API
Policy support form. If you already have more than 10 apps registered,
you can continue to use them as long as they comply with our rules but
you won’t be able to register new apps until you either request
permission for additional apps or delete unused ones.
https://blog.twitter.com/developer/en_us/topics/tools/2018/new-developer-requirements-to-protect-our-platform.html
Also, note that you can only create 3 new apps in a 24 hour period.
First of all, you should NOT make more than one Application for one application.
You need to handle data logically. Cache the data you are requesting so you can limit the number of requests to twitter's API.
How to limit requests: https://dev.twitter.com/docs/faq#5823
Here are some docs:
https://dev.twitter.com/docs/rate-limiting/1.1
and https://dev.twitter.com/discussions/8126
Related
1: When it says 15 requests per 15 minute window, does this really mean I can only send 15 requests per 15 minutes?
2: Do I really need to set up a Twitter bot to send basic requests like getting a list of a user's followers? Is there a way to get the data through a URL, like in most web APIs? I'm making software that will be used by other people, so it can't have a bot auth token in the code.
I know I'm pretty much asking if what it blatantly says is true, but I'm just having trouble believing that the Twitter API is really this bad.
It sounds like you are specifically asking about the friends and followers endpoints. Yes, this is limited to 15 requests in a 15 minute window. Other endpoints / features have different rate limits.
The Twitter API requires authentication. You do not need to set up a "bot", but you will need a registered Twitter developer account, and a Twitter app, in order to use the API. If your app will be used by other people, you would need to implement Sign-in with Twitter to enable them to authenticate with your app; you can then store their access token (until or unless they revoke it) to make requests on their behalf. This is pretty standard for any multi-user web app.
Can someone please help me find the official confirmation regarding what the refresh token generation limit for single project is regardless of how many users authorize access to it? Or if there is any limit at all?
I have gone through the google documentation and also read through answers provided here for similar questions asked earlier but cannot find any answer that pinpoints to the exact documentation that confirms this.
Google Api documentation:
https://developers.google.com/identity/protocols/OAuth2#expiration
Paragraph in context from google documentation:
"There is currently a limit of 25 refresh tokens per user account per client. If the limit is reached, creating a new token automatically invalidates the oldest token without warning. This limit does not apply to service accounts.
There is also a larger limit on the total number of tokens a user account or service account can have across all clients. Most normal users won't exceed this limit but a developer's test account might."
It is clear from the documentation that 25 is the limit for client-user combination. However it is still not clear what the limit for a single project is. (or if there is a limit at all?)
p.s. The project I'm working would ask user to authorize then prompt him to allow offline access.
There is no per project limit.
Buffer claims to have millions of users, all scheduling posts. The free plan allows for 10 posts per day.
How does Buffer overcome Twitter API limits?
They're not bypassing the limit, they're doing the queries on your behalf. I don't have an account with them, but most sites where you can login to them using Twitter utilize your credentials to submit the queries allowing them to do many at once.
A good way to test this is going to your profile settings, then click on either Apps or Your Twitter Data you should see their name popup there. For their paid version, they could purchase an increase in limit from Twitter but you'll end up paying for that through their pricing cost.
The question seems duplicated, yet it's not. The question seems silly and it is. If I want to search for a certain word in tweets, I would send a request to the Twitter API. I can send the request:
Using user authentication: which requires logged in user.
Using application authentication: which doesn't require a logged in user and uses an application ID (public and private keys).
Now, Facebook, Twitter and other social networks for that matter provides API Rate Limit per user and per application (globally). Suppose that I want to search for the word "stackoverflow" from two application instances (one on iOS and the other on Android). Is the API limit divided on both of them? or each has its own full limit?
For example, assume that social network "X" provides up to 150 requests/app/15 min window. Do I have that 150 requests for each running instance of the application or I have a total of 150 requests for all instances?
Hope I made it clear enough.
Found the answer here: Question about app-only auth and rate limits for an iOS app in API v1.1
The number of users or "instances of use" of your application are not figured in to rate limits for app-only auth. A method with a limit of 180 requests per 15 minute window is intrinsic to your application, regardless of whether it's on device A, device B, device C, website 1, website 2.
I'm building a suite of tools that integrate with Asana. These tools comprise a web browser extension and a web app (or Chrome packaged app). Do the browser extension and web app share the same API call quota?
Right now, API rate limits are enforced per-user. Until we released OAuth support, there was no way to distinguish between different apps (since users were always authorized by the same API key). In future, each app will get its own rate limit quota (per user). If you intend to make them separate apps (and have users authorize them separately) they would then get separate quotas - but if you're either using an API key for both, or sharing one OAuth app, they'll end up sharing their quota, too, even if we roll out the change I mentioned earlier.