[twitter-dev] Re: Twitter's OAuth provider ... what happened?
I'm getting the same error since this afternoon, any ideas??? 401:Authentication credentials were missing or incorrect. Invalid oauth_verifier parameter /oauth/access_token -- 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
Re: [twitter-dev] Re: Twitter's OAuth provider ... what happened?
Looking at your examples it looks like you don't have the oauth_verifier included in your request. The oauth_verifier can be found in the request parameters of the callback we make to you. Try adding the parameter in to see if that resolves the issue. Best @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Thu, Dec 2, 2010 at 4:46 PM, Hector hvazq...@gmail.com wrote: I'm getting the same error since this afternoon, any ideas??? 401:Authentication credentials were missing or incorrect. Invalid oauth_verifier parameter /oauth/access_token -- 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 -- 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
Re: [twitter-dev] Re: Twitter's OAuth provider ... what happened?
Looks like that was it ... updated my OAuth consumer and now things are working again. Was this announced somewhere and I totally missed it? On 12/2/10 8:07 PM, Matt Harris wrote: Looking at your examples it looks like you don't have the oauth_verifier included in your request. The oauth_verifier can be found in the request parameters of the callback we make to you. Try adding the parameter in to see if that resolves the issue. -- Dossy Shiobara | do...@panoptic.com | http://dossy.org/ Panoptic Computer Network | http://panoptic.com/ He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on. (p. 70) -- 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
