I am a Java developer working on a web application that makes use of
the Twitter API.  We use the Signpost library (version to
perform OAuth and issue API requests, and have been doing so
successfully for months.  We have been signing our requests with a
whitelisted key and secret that has a 20,000 request/hour rate limit.

In the last few days, we started getting only 401 Not Authorized
responses when using these credentials.  Upon looking back at our
server logs, I notice other requests failures dating back to at least
Feb 17, but they are sporadic.  Error messages look like this:

WARN org.apache.http.impl.client.DefaultHttpClient Authentication
error: Unable to respond to any of these challenges: {oauth=WWW-
Authenticate: OAuth realm="http://api.twitter.com"}

The response header shows 401 but no other enlightening information.

I have paid attention to and read lots of other postings related to
OAuth, and want to emphasize that our system has been working for
quite a while - we make calls using the proper end points and so


Something appears to have changed on Twitter's end but we don't know

Can anyone shed some light on what might be happening?  We have
already verified with Twitter API support that our credentials should
still be viable - perhaps there has been an inadvertent shutdown of
that account?

Thank you in advance for any help or guidance!

Chris Stolte

Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 

Reply via email to