There can never be enough articles and books supporting API best practices.

Here are two of my favorite REST resources (pun intended).

Richardson Maturity Model: steps toward the glory of REST

http://martinfowler.com/articles/richardsonMaturityModel.htm...

RESTful Web Services Cookbook: Solutions for Improving Scalability and Simplicity

http://www.amazon.com/gp/product/0596801688

And I am looking forward to widespread adoption of the REST problem standard posted here a few weeks ago.

http://www.ietf.org/id/draft-ietf-appsawg-http-problem-00.tx...

Try the REST cookbook:

http://www.amazon.com/RESTful-Web-Services-Cookbook-Scalabil...

I'd recommend this book http://www.amazon.com/RESTful-Web-Services-Cookbook-Scalabil...

It's amazing, really. It's not just a recipies list, it explains a lot of very important REST cases, and also when to use or not to use REST.

If you want an example app that is a RESTful API with JS front end, please excuse me pimping my own project: http://phreeze.com/ (the REST server is in PHP)

Here's a language-neutral book that goes into RESTful services: http://www.amazon.com/RESTful-Web-Services-Cookbook-Scalabil...

In this same vein, I am curious what you guys think of using semi-colon and comma characters in URLs when pointing at an endpoint that generates a response that would typically be provided by a query string, e.g.:

    http://site.com/generate;lang=en,size=32,weight=78 

RESTful Web Services Cookbook[1] gave me the idea (a fantastic book) and what I like about it, is that interstitial proxy software seems to molest the URL less where as some refuse to pass through query string params for some reason (e.g. CloudFront).

Anyone see any glaring issues with this?

[1] http://www.amazon.com/RESTful-Web-Services-Cookbook-Scalabil...