Regenerating the keys did the trick. Turns out there is a bug in the Django app that I'm using for Twitter authentication that uses stale access tokens. Updating the user's access token whenever he/she logs into my app fixed the issue.
Also, apigee.com has a really good Twitter API panel. Thanks for the help. On Apr 24, 1:13 am, bear <bea...@gmail.com> wrote: > Here is what I see: > > send: u'GET > /1/account/verify_credentials.json?oauth_nonce=85271670&oauth_timestamp=130 > 3621152&oauth_consumer_key=...&oauth_signature_method=HMAC-SHA1&oauth_versi > on=1.0&oauth_token=...&oauth_signature=... > HTTP/1.1\r\nAccept-Encoding: identity\r\nHost: > api.twitter.com\r\nConnection: close\r\nUser-Agent: > Python-urllib/2.7\r\n\r\n' > reply: 'HTTP/1.1 200 OK\r\n' > > and then send looks identical to yours (order and fields) so that is telling > me you may need to regenerate your tokens (especially since you are having > issues with another lib.) > > Have you tried a test using that test twitter api page? I am drawing a blank > on the link :( -- 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: http://groups.google.com/group/twitter-development-talk
