Ask HN: Review my REST API and Website (api.seqcentral.com)
I'm working on a new REST API and corresponding Website for SeqCentral (found at http://api.seqcentral.com) and would greatly appreciate your feedback from both technical and UI perspectives. As you may know, once the API is "live" it's very difficult to change.
From a technical perspective, I've taken aspects from a wide variety of sources including Twilio, Zencoder, Twitter, 3Scale, and AWS. There are a lot of "best practices" but some conflict. For example, should the API version be in the URI? If no items are available should it return an empty array or "null"? Should authentication be done through cookies? digests? OAuth tokens?
If you don't have interest in evaluating the REST API itself, perhaps the greatest help could be undertaken in a couple of minutes by evaluating the UI of the API documentation itself: http://api.seqcentral.com/index.php/api
Thanks for the help.
-Jeremy