It's forbidden to automate the OAuth flow such that you attempt scarping the PIN code from the resultant page.
If your application is capable of receiving URL-based callback, you'll want to preconfigure a default callback on dev.twitter.com (which indicates that your app is capable of receiving a callback) and provide an explicit callback on the request token step. When the user is sent to your callback, an oauth_verifier (PIN) will be included with the other relevant oauth_* parameters. If your application is incapable of receiving an URL-based callback, you need to present a UI for the user to hand-enter the PIN code/oauth_verifier, and then use that value to complete the flow after sending the user through the authorization steps. Taylor On Mon, Sep 6, 2010 at 12:14 AM, Amid Lad <amid....@gmail.com> wrote: > I've been transitioning our basic authentication calls over to OAuth. > I'm using the j2me OAUTH library(for mobile). All of the > authentication calls > are working and I receive proper responses from GET requests. > > But the problem is with access token. What I have to do is to pass the > url and get the > pin number and need to pass the pin number to get the access. > > How can I avoid this process and directly get the pin response from > server and use it get the > twitter access? > > What is the url to get the pin response? > > Thanks in advance. > > -- > 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?hl=en > -- 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?hl=en