The method you are using is called Pin-based OAuth, designed for

It's not ideal for mobile integration b/c it is cumbersome to ask
mobile user to copy and paste a pin from safari browser, then open app
2nd time to paste the pin in the right place in the app. Who would
want to take extra steps to authenticate such app on the go?

Plus your app would request user to enter multiple twitter accts to
request matching pin for each account. Think of how many steps the
same user have to do?


On Dec 20, 12:48 pm, Omar Gonzalez <> wrote:
> I found this thread about OAuth and multiple 
> devices:
> All of the information in that thread makes sense to me.  I currently
> have a mobile application where I have successfully implemented an
> OAuth flow, I'm not quite sure what the official name is, so I will
> describe it.
> If the application does not have an OAuthToken the mobile browser is
> opened and the user is asked to log in to give the mobile application
> permission to access their account.  If the user agrees, they get a
> PIN number to enter into my mobile application.  Once the user enters
> the PIN, I request a token from Twitter, my app verifies the token
> access and retrieves the user's screen name.
> What I am not sure of is what is the intended way to handle mobile
> applications that post to multiple Twitter accounts?  Do I need
> messaging in my application to instruct the user to make sure they're
> logged out of their application so they can log in with another
> account and my application can request access that way?  That seems
> kind of clunky.  Is there another alternative where I can have the
> user enter their screen name and I can start an OAuth flow with that?
> Any help/guidance is appreciated.
> -omar

Twitter developer documentation and resources:
API updates via Twitter:
Issues/Enhancements Tracker:
Change your membership to this group:

Reply via email to