rate limiting due to invalid oauth credentials

Skip to first unread message


Jul 4, 2011, 11:55:47 AM7/4/11
to Twitter Development Talk
I make queries to an api method that requires authentication (statuses/
mentions.xml), and I get expected results with rate limits of 350/
hour. I make another query to an api method that does not require
authentication (users/lookup.xml) and it drops the rate limit to 150/
hour and complains of invalid oauth credentials.

Since I use common code to make the queries, this is confusing... what
could be wrong?

Mo'b Mo'b

Jul 4, 2011, 2:09:10 PM7/4/11
to twitter-deve...@googlegroups.com
Authenticated Rate Limit --- 350 Calls per hour.
Unauthenticated Rate Limit --- 150 Calls per hour.

Please read the docs.


Aug 10, 2011, 11:50:58 AM8/10/11
to Twitter Development Talk
Read the docs...thought the call was authenticated, but discovered
that the library I was using had a bug for situations where the call
included certain characters. The authentication failed, but the query
continued as an unauthenticated call. No error message. Bitch of a
time figuring out what was happening; had to reverse engineer the
library and step through it.

Matt Harris

Aug 10, 2011, 4:57:28 PM8/10/11
to twitter-deve...@googlegroups.com
Hey Mike,

Sorry to hear you were having problems there. If the credentials were being rejected we would have returned an X-Warning header in the response letting you know.

There is more information about this in our rate limiting documentation:

Hope that helps,
Twitter, Inc.

Have you visited the Developer Discussions feature on https://dev.twitter.com/discussions yet?

Twitter developer links:
Documentation and resources: https://dev.twitter.com/docs
API updates via Twitter: https://twitter.com/twitterapi

Unsubscribe or change your group membership settings: http://groups.google.com/group/twitter-development-talk/subscribe

Reply all
Reply to author
0 new messages