Well ... the most obvious thing to do would be to get rid of the unexpected oauth_verifier parameter :)
Seriously, if you're using it as a webapp, you shouldn't put that in there. On Sat, Sep 12, 2009 at 14:05, DanInDC <danjacob.beaul...@gmail.com> wrote: > > I am trying to build a twitter app that uses oauth to signin. > > I am successfully getting a request token and successfully being > returned to my callback url. But when I request the access token using > a request: > > > http://twitter.com/oauth/access_token?oauth_nonce=83055562&oauth_timestamp=1252784756&oauth_signature_method=HMAC-SHA1&oauth_consumer_key=CONSUMER_KEY&oauth_verifier=None&oauth_version=1.0&oauth_token=OAUTH_TOKEN&oauth_signature=OUATH_SIG%3D&oauth_callback=None > > and I get the error: > > <error>Unexpected oauth_verifier parameter</error> > > I understand oauth_verifier is for desktop twitter apps, but my app is > a web app and is set as such in my application settings at > twitter.com. > > Upfront, I am working with a lot of new technologies on this project, > so it may be something obvious. > Would appreciate any help. > -- Internets. Serious business.