title: Why is Twitter quota for app-auth greater for some endpoints and less for others, compared to user-auth?
body: <p>Twitter allows developers to use <a href="https://developer.twitter.com/en/docs/basics/authentication/overview/application-only.html" rel="nofollow noreferrer">app-auth</a> rather than user-auth, but sometimes the API quotas for app-auth are <em>better</em> than with user-auth, and sometimes they're <strong>worse</strong> - why is that?</p>
  
  <p>From <a href="https://developer.twitter.com/en/docs/basics/rate-limits.html" rel="nofollow noreferrer">https://developer.twitter.com/en/docs/basics/rate-limits.html</a> :</p>
  
  <p><a href="https://i.stack.imgur.com/ufuQK.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/ufuQK.png" alt="enter image description here"></a></p>
  
  <p>In the table above you can see that if you want to <a href="https://developer.twitter.com/en/docs/tweets/search/api-reference/get-search-tweets.html" rel="nofollow noreferrer">search tweets</a>, it's better to use app-auth, but if you want to simply do <a href="https://developer.twitter.com/en/docs/tweets/post-and-engage/api-reference/get-statuses-lookup" rel="nofollow noreferrer">bulk lookup by id</a>, it's better to use user-auth.</p>