Hi Kutsumi, You are correct in assessing the current behavior -- we'll return to your callback URL if they hit deny. In that case, we'll also NOT be sending you an oauth_verifier and other information you'd need on the callback URL to properly execute the "exchange request token for access token" negotiation step of OAuth.
If your callback function is executed and does not contain the necessary paramaters to further consume an access token, you can make a reasonable assumption that the user denied the access without your application needing to make API calls to verify_credentials (you also wouldn't have any credentials to "verify" in this case. Taylor On Mon, Sep 27, 2010 at 9:36 PM, K <kuts...@gmail.com> wrote: > Hi > sorry for bringing up the issue that has been discussed in the past... > I found this issue tracking from other posts about the same issue. > > http://groups.google.com/group/twitter-development-talk/browse_thread/thread/3c3c97cd80ebc707/a82aab0e12c61dc3?hl=en&lnk=gst&q=deny#a82aab0e12c61dc3 > > So it says here the issue is solved, but just wanted to get > clarification on how the issue is solved, and how I should implement > my program. > > So I believe, now after user click "deny", they will go to the page > which has link and if user clicks on it he/she goes back to the > callback_url. Is that correct? > > Is there any parameter that is attached when callback url is called > that will tell me if user has clicked on "deny"? > If not, do I need to call verify credentials everytime callback url is > accessed just to find out if user has allowed or denied? > > Thanks for your help! > Kate > > -- > 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