Thanks again, Taylor. I'll use api.twitter.com instead of twitter.com I'm already using https://twitter.com calls for the app (currently in the app store), but I use http for test purposes (easier for debugging and tracking traffic)
Ram On Mar 19, 1:30 pm, Taylor Singletary <taylorsinglet...@twitter.com> wrote: > Hi Ram, > > I recommend standardizing on api.twitter.com for the OAuth endpoints as well > as the resource endpoints. > > Further, for all the OAuth-related steps (authorize, access_token, and > request_token) I strongly recommend using SSL. > > Taylor Singletary > Developer Advocate, Twitterhttp://twitter.com/episod > > > > On Fri, Mar 19, 2010 at 1:21 PM, Ram <group...@cascadesoft.net> wrote: > > Thanks Taylor, this is good to know. > > > Btw for OAuth, should I be using the following URLs > >http://api.twitter.com/oauth/authorize?oauth_token=xxxxxx > >http://api.twitter.com/oauth/authorize > >http://api.twitter.com/oauth/access_token > > > or should I be using theirhttp://twitter.comequivalents ? > > > Both work fine. > > > Thanks Ram > > > On Mar 19, 1:07 pm, Taylor Singletary <taylorsinglet...@twitter.com> > > wrote: > > > While we may very well version the OAuth endpoints in the future, it's > > best > > > not to consider OAuth authorization flow steps as "APIs" in and of > > > themselves. At this time, versioned areas of the API are areas relating > > to > > > actual resources that correspond to data Twitter provides and processes > > > (statuses, search results, information about users, favorites, lists, > > > timelines, etc.) > > > > Taylor Singletary > > > Developer Advocate, Twitterhttp://twitter.com/episod > > > > On Fri, Mar 19, 2010 at 11:11 AM, Ram <group...@cascadesoft.net> wrote: > > > > I didn't get any response for last week's > > > >http://twitter.com/CascadeRam/status/10487105790 > > > > , so I'm hoping to get an official response here. > > > > > In October, last year, > > > >http://groups.google.com/group/twitter-api-announce/browse_thread/thr. > > .. > > > > recommended that all developers move to the new versioned apis and > > > > that Twitter would set a hard date after whchhttp://twitter.comwill > > > > not be serviced. > > > > > However, 5 months after that announcement, the new versioned api > > > > doesn't seem to be supported for Twitter OAuth calls (though the > > > > versioned api works with other methods like > > > >http://api.twitter.com/1/friendships/create.xml) > > > > >http://api.twitter.com/1/oauth/request_tokenreturnsa 404 (but > > > >http://twitter.com/oauth/request_tokenand > > > >http://api.twitter.com/oauth/access_token > > > > work correctly) > > > > > So for now, I'm using the following (non-versioned) URLs > > > >http://api.twitter.com/oauth/authorize?oauth_token=xxxxxx > > > >http://api.twitter.com/oauth/authorize > > > >http://api.twitter.com/oauth/access_token > > > > > and I'm using versioned URLs for other stuff like > > > >http://api.twitter.com/1/statuses/update.xml > > > > > Are these the best URLs to be using now ? > > > > > Does anyone know whether the 404 error is due to a bug, due to an > > > > incomplete implementation of the new api or whether OAuth apis are > > > > exempted from versioning ? > > > > > To unsubscribe from this group, send email to twitter-development-talk+ > > > > unsubscribegooglegroups.com or reply to this email with the words > > "REMOVE > > > > ME" as the subject.- Hide quoted text - > > > > - Show quoted text - > > > To unsubscribe from this group, send email to twitter-development-talk+ > > unsubscribegooglegroups.com or reply to this email with the words "REMOVE > > ME" as the subject.- Hide quoted text - > > - Show quoted text - To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
