Tweets from the collection REST: Headers & Versioning on tweetlibrary.com. http://tweetlibrary.com/damon/rest:headers&versioning http://twitter.com/h3h/statuses/157223713752879105 @damon Basically just copy GitHub and/or Heroku when doing API design. Therein lives goodness. Wed, 11 Jan 2012 22:13:49 +0000 http://twitter.com/h3h/statuses/157223713752879105 http://twitter.com/h3h/statuses/157223205893976065 @damon Keeping things in headers is tidy and easy to develop against. Not sure about “RESTful”, but that’s usually not my goal. Wed, 11 Jan 2012 22:11:48 +0000 http://twitter.com/h3h/statuses/157223205893976065 http://twitter.com/damon/statuses/157221534501580801 @garrettdimon a good point. to me, the key seems completely irrelevant to the resource itself. it's purely for access control in this case. Wed, 11 Jan 2012 22:05:09 +0000 http://twitter.com/damon/statuses/157221534501580801 http://twitter.com/damon/statuses/157220973987373056 @hayesdavis @howardr Agree. I like Howard's word 'pragmatic' to describe it. It's less 'pure' but helps clients to know what to expect. Wed, 11 Jan 2012 22:02:55 +0000 http://twitter.com/damon/statuses/157220973987373056 http://twitter.com/garrettdimon/statuses/157220446041935872 @damon I would think including the key in the URL would be less restful because the key isn't a part of the resource identifier. Wed, 11 Jan 2012 22:00:50 +0000 http://twitter.com/garrettdimon/statuses/157220446041935872 http://twitter.com/howardr/statuses/157219742925590529 @hayesdavis @damon I agree. It is a very pragmatic approach which IMO is good. However it was the only example I could think of Wed, 11 Jan 2012 21:58:02 +0000 http://twitter.com/howardr/statuses/157219742925590529 http://twitter.com/hayesdavis/statuses/157218843457110017 @howardr @damon If the resource is significantly different due to an API change, I think a version # in the URL is valid. Wed, 11 Jan 2012 21:54:27 +0000 http://twitter.com/hayesdavis/statuses/157218843457110017 http://twitter.com/steveklabnik/statuses/157218697306587136 @damon as long as it doesn't affect the _addressability_, you should be fine. Wed, 11 Jan 2012 21:53:53 +0000 http://twitter.com/steveklabnik/statuses/157218697306587136 http://twitter.com/steveklabnik/statuses/157218627685326848 @damon as a means of authentication? I don't see a problem with that. Wed, 11 Jan 2012 21:53:36 +0000 http://twitter.com/steveklabnik/statuses/157218627685326848 http://twitter.com/steveklabnik/statuses/157218530507493376 @howardr REST apis should not be versioned in the first place. /cc @damon Wed, 11 Jan 2012 21:53:13 +0000 http://twitter.com/steveklabnik/statuses/157218530507493376 http://twitter.com/howardr/statuses/157218396776316929 @damon @steveklabnik Ex. API version should be in headers and not URL Wed, 11 Jan 2012 21:52:41 +0000 http://twitter.com/howardr/statuses/157218396776316929 http://twitter.com/howardr/statuses/157218304296091648 @damon @steveklabnik I always thought HTTP headers were pivotal to RESTful APIs. The URL is supposed to be specific to a resource. Wed, 11 Jan 2012 21:52:19 +0000 http://twitter.com/howardr/statuses/157218304296091648 http://twitter.com/damon/statuses/157218096782917633 @steveklabnik identifies the client by API key in an X- header Wed, 11 Jan 2012 21:51:29 +0000 http://twitter.com/damon/statuses/157218096782917633 http://twitter.com/steveklabnik/statuses/157217908110536704 @damon what does your header do? Wed, 11 Jan 2012 21:50:44 +0000 http://twitter.com/steveklabnik/statuses/157217908110536704 http://twitter.com/steveklabnik/statuses/157217886312726530 @damon almost entirely irrelevant. It depends on the specifics, really. Wed, 11 Jan 2012 21:50:39 +0000 http://twitter.com/steveklabnik/statuses/157217886312726530 http://twitter.com/damon/statuses/157217643252813825 #API geeks: does reliance on HTTP headers make an API not RESTful or less RESTful than one which includes key in the URL? /cc @steveklabnik Wed, 11 Jan 2012 21:49:41 +0000 http://twitter.com/damon/statuses/157217643252813825