Re: [twitter-dev] What is the correct OAuth API endpoint

2010-03-04 Thread Thomas Woolway
It's good to know that this is the recommended URI root for OAuth. Any
chance of getting the docs (
http://apiwiki.twitter.com/Twitter-REST-API-Method:-oauth-access_token etc)
updated to help out newcomers? Also, it might be worth adding a big NB that
those resources aren't versioned - it's one of those things that is quite
easy to miss.

Cheers,

Tom

On Wed, Mar 3, 2010 at 3:26 PM, Scott Wilcox sc...@tig.gr wrote:

 Zhami,

 I'd go with https://api.twitter.com/1

 Scott.

 On 3 Mar 2010, at 15:02, Zhami wrote:

  What is the correct API end-point for OAuth authenticated,
  *documented* API calls?
 
  http(s)://twitter.com
 
  http(s)://api.twitter.com
 
  http(s)://api.twitter.com/1
 




Re: [twitter-dev] What is the correct OAuth API endpoint

2010-03-04 Thread Taylor Singletary
The OAuth steps in the apiwiki have been updated to reflect the preferred
subdomain of api as well as a note about the URLs not being versioned yet.

Thanks,
Taylor

On Thu, Mar 4, 2010 at 7:18 AM, Thomas Woolway tswool...@gmail.com wrote:

 It's good to know that this is the recommended URI root for OAuth. Any
 chance of getting the docs (
 http://apiwiki.twitter.com/Twitter-REST-API-Method:-oauth-access_token etc)
 updated to help out newcomers? Also, it might be worth adding a big NB that
 those resources aren't versioned - it's one of those things that is quite
 easy to miss.

 Cheers,

 Tom


 On Wed, Mar 3, 2010 at 3:26 PM, Scott Wilcox sc...@tig.gr wrote:

 Zhami,

 I'd go with https://api.twitter.com/1

 Scott.

 On 3 Mar 2010, at 15:02, Zhami wrote:

  What is the correct API end-point for OAuth authenticated,
  *documented* API calls?
 
  http(s)://twitter.com
 
  http(s)://api.twitter.com
 
  http(s)://api.twitter.com/1
 





Re: [twitter-dev] What is the correct OAuth API endpoint

2010-03-03 Thread Taylor Singletary
Hi Zhami,

http(s)://api.twitter.com is best for OAuth-related operations like the
requestToken, accessToken, and authorizeToken steps of the OAuth flow. These
aren't versioned the way that resource-based APIs are.

http://api.twitter.com/oauth/request_token
http://api.twitter.com/oauth/authorize
http://api.twitter.com/oauth/access_token

For resource requests for things like tweets, timelines, lists, etc. use the
versioned URL scheme with the api.twitter.com. Adopting the versioning
scheme helps protect you from future changes to what might be considered the
default version of the API, should things ever change significantly.

http://api.twitter.com/1/statuses/friends_timeline.json

Taylor

On Wed, Mar 3, 2010 at 7:02 AM, Zhami stu...@zhameesha.com wrote:

 What is the correct API end-point for OAuth authenticated,
 *documented* API calls?

 http(s)://twitter.com

 http(s)://api.twitter.com

 http(s)://api.twitter.com/1




Re: [twitter-dev] What is the correct OAuth API endpoint

2010-03-03 Thread Scott Wilcox
Zhami,

I'd go with https://api.twitter.com/1

Scott.

On 3 Mar 2010, at 15:02, Zhami wrote:

 What is the correct API end-point for OAuth authenticated,
 *documented* API calls?
 
 http(s)://twitter.com
 
 http(s)://api.twitter.com
 
 http(s)://api.twitter.com/1
 



smime.p7s
Description: S/MIME cryptographic signature