The API is deliberately made un-rich. Its difficult to use. On Wed, Jun 29, 2011 at 8:51 PM, CD <chesterdorae...@gmail.com> wrote:
> figured it out on my own. must use HTTP GET with OAuth params passed > in URI string. Not mentioned in the documentation. Wasted many hours > figuring out this stuff would be clarified if someone updated the docs > and made some examples. > > On Jun 29, 2:03 pm, CD <chesterdorae...@gmail.com> wrote: > > I have successfully implemented oauth and have used > > /statuses/update > > /friendships/create > > > > I was also able to connect to > http://stream.twitter.com/1/statuses/sample.json > > using Basic Auth on HTTP. > > > > However, when I try to connect tohttps:// > userstream.twitter.com/2/user.json > > with HTTPS and OAuth as required in the documentation, I get back ZERO > > data. I try fiddling with the input and the best I could get is > > Unauthorized response. > > > > I am pretty much doing the OAuth the same way as other requests, > > trying POST and GET. I put OAuth in the header > > > > baseURI = urlencode(https://userstream.twitter.com/2/user.json) > > > > Authorization: OAuth oauth_callback=oob, > > oauth_consumer_key=<my_consumerkey>, oauth_nonce=9rEAx8760yc0IQYC0HCm, > > oauth_signature=Q385vY3GL9GzkppBAqEildZIKJw%3D, > > oauth_signature_method=HMAC-SHA1, oauth_timestamp=1309370434, > > oauth_token=<user_oauth_token>, oauth_version=1.0 > > -- > Twitter developer documentation and resources: https://dev.twitter.com/doc > API updates via Twitter: https://twitter.com/twitterapi > Issues/Enhancements Tracker: > https://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > https://groups.google.com/forum/#!forum/twitter-development-talk > -- ©*InFiNiTy*. *Mobinga Inc*. -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
