Rate limit exceeded for OAuth calls

arungupta · 2012-01-12T01:22:01.000Z

I’m writing a Java client to talk to Twitter. Did OAuth using Jersey API using and then passing the signed oauth_token to request user_timline as:

https://api.twitter.com/1/statuses/user_timeline.json?include_entities=true&include_rts=true&screen_name=arungupta&count=10

The Authorization header is also set correctly. But I’m still getting the error:

“Rate limit exceeded. Clients may not make more than 150 requests per hour.”

https://dev.twitter.com/docs/rate-limiting says OAuth calls are permitted 350 per hour. This message seem to indicate that unauthenticated request limit is reached. Why so ?

-Arun

episod · 2012-01-12T16:37:36.000Z

Examine your HTTP headers in the response – you might have an X-Warning header telling you that your auth is actually invalid but that since you’re requesting a method not explicitly requiring auth, we’re serving it to you in an unauthenticated context to satisfy your request. Most likely there is something subtle causing invalid auth for you.

arungupta · 2012-01-13T17:44:28.000Z

Ah, that explains!

Following up on why X-Warning header is coming with @kurrik at https://dev.twitter.com/discussions/4865.

Any insights on that thread will be helpful as well.