[twitter-dev] Re: 401 Unauthorized When Getting an Access Token

2009-07-31 Thread mattarnold1977
Please, if anyone can assist I would be grateful. Here is a sample of my url I've formed to get the access token: http://twitter.com/oauth/access_token?oauth_consumer_key=myconsumerkey&oauth_nonce=6475147&oauth_signature=mysignature&oauth_signature_method=HMAC-SHA1&oauth_timestamp=1248981982&oau

[twitter-dev] Re: 401 Unauthorized When Getting an Access Token

2009-07-31 Thread JDG
Since you're not including an oauth_callback, i would assume you're using the oob flow, in which case, i have to ask, where's your oauth_verifier parameter? On Fri, Jul 31, 2009 at 13:09, mattarnold1977 wrote: > > Please, if anyone can assist I would be grateful. Here is a sample of > my url I'v

[twitter-dev] Re: 401 Unauthorized When Getting an Access Token

2009-08-01 Thread mattarnold1977
JDG, Thanks for the reply. I didn't realize that I needed to include an oauth_callback parameter for getting the ACCESS TOKEN. I knew I could supply one (optional) when getting the REQUEST TOKEN. I thought it would automatically callback to the application I created with Twitter. I'm also not

[twitter-dev] Re: 401 Unauthorized When Getting an Access Token

2009-08-01 Thread JDG
oob means Out of Band, and is designed for desktop applications. If you don't specify a callback when getting the request token, you're given a pin to enter. It sounds like you're not using that flow though. On Sat, Aug 1, 2009 at 14:55, mattarnold1977 wrote: > > JDG, > > Thanks for the reply. I