Hi. I'm using python-oauth2 to handle the authentication with the REST and user stream APIs. I'm using the same code to sign the request in both cases, and send the oauth credentials as authentication header.
While everything works perfectly with REST requests, I'm getting 401 responses with the user stream ones. The oauth related code is exactly the same, and token and consumers keys and secrets too. If I change to query parameters based oauth, then everything works correctly with the user stream API. Is there any limitation in how oauth data is to be sent to user stream API? I can't find any specific information on how authentication is no be handled with this endpoint. Should the headers approach work just like in the REST API case? Thanks! -- 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