Recently users have been seeing 429 rate limiting on
oauth/request_token which effects all users. Is this intended?
Answered! Go to the Best Answer.
Best AnswerIs your app making Client Only calls to other endpoints?
The request_token and access_token endpoints do not affect your rate limit (ie it doesnt use up your quota). However if your client exceeds the Client Only rate limit through calling other endpoints, your client will be blocked from making (client only) requests to all endpoints (including the oauth endpoints).
Best AnswerIs your app making Client Only calls to other endpoints?
The request_token and access_token endpoints do not affect your rate limit (ie it doesnt use up your quota). However if your client exceeds the Client Only rate limit through calling other endpoints, your client will be blocked from making (client only) requests to all endpoints (including the oauth endpoints).
Best AnswerI can't seem to find any culprit to this problem. It just started happening after months of no issues. Would it be possible to not rate limit on the OAuth 1.0a auth process? I do not make any client API calls... Would it be possible to just disable client api calls and not have thsi rate limit issue?
Thanks!
Best AnswerPlease Private Message me your Consumer Key and I can track down which calls are being made as OAuth 1.0 Client Only call.
Best AnswerI got your PM with the consumer key. Your application has made several thousand client only API calls in the last 24 hours and most of those were not for /oauth/request_token or /oauth/access_token.
I'll send you more detailed info in a PM.