It is specified on the XAuth documentation. On Sun, Apr 25, 2010 at 13:39, Craig Hockenberry < craig.hockenbe...@gmail.com> wrote:
> No, I didn't ask for access. I guess that's the bug: there's no place > during the signup process that tells you that you need to go through a > manual process to get xAuth access... > > -ch > > On Apr 25, 1:29 pm, Raffi Krikorian <ra...@twitter.com> wrote: > > hi craig. > > > > have you gotten access to xAuth? applications are not, by default, given > > access to xAuth - if you e-mail a...@twitter.com with > > > > - your client token; and > > - a description of your application > > > > then we can grant it access. > > > > On Sun, Apr 25, 2010 at 1:22 PM, Craig Hockenberry < > > > > > > > > > > > > craig.hockenbe...@gmail.com> wrote: > > > Hi Raffi! > > > > > Is there a delay/verification after a new app is created? I just > > > created a new app and am seeing problems getting the OAuth token with > > > a xAuth HTTP request that looks like this: > > > > > xAuth consumer key = N3fq77IdBT4qfglbcb4njg, consumer secret = > > > REDACTED > > > xAuth URL =https://api.twitter.com/oauth/access_token > > > xAuth HTTP method = POST, shouldHandleCookies = NO, cachePolicy = > > > NSURLRequestReloadIgnoringCacheData > > > xAuth HTTP headers = { > > > "Content-Length" = 78; > > > "Content-Type" = "application/x-www-form-urlencoded"; > > > } > > > xAuth HTTP body = > > > > x_auth_mode=client_auth&x_auth_username=REDACTED&x_auth_password=REDACTED > > > > > I get back a status code of 0 and a response of "Failed to validate > > > oauth signature and token". > > > > > For an older application with different consumer information (key = > > > 5CAYV1DR5uwhVRJDBrepw) but the same username and password), I get back > > > a code of 200 and an empty response. > > > > > If there is indeed a delay for this information to propagate, you need > > > to let people know... > > > > > -ch > > > > > On Apr 24, 8:40 am, Raffi Krikorian <ra...@twitter.com> wrote: > > > > hi all. > > > > > > you're going to be hearing a lot from me over the next 9 weeks. our > plan > > > is > > > > to turn off basic authorization on the API by june 30, 2010 -- > developers > > > > will have to switch over to OAuth by that time. between now and > then, > > > there > > > > will be a *lot* of information coming along with tips on how to use > OAuth > > > > Echo, xAuth, etc. we really want to make this transition as easy as > we > > > can > > > > for everybody. > > > > > > as always, please feel free to reach out to this group, or to > @twitterapi > > > > directly. if you need help remembering the date - > > >http://bit.ly/twcountdown > > > > . > > > > > > -- > > > > Raffi Krikorian > > > > Twitter Platform Teamhttp://twitter.com/raffi > > > > > > -- > > > > Subscription settings: > > >http://groups.google.com/group/twitter-development-talk/subscribe?hl=en > > > > -- > > Raffi Krikorian > > Twitter Platform Teamhttp://twitter.com/raffi > -- Abraham Williams | Developer for hire | http://abrah.am @abraham | http://projects.abrah.am | http://blog.abrah.am This email is: [ ] shareable [x] ask first [ ] private.
