To answer these questions ourselves: 1. We plan to include the documentation for the API at the root of the API i.e. https://api.verelo.com https://api.verelo.

To answer these questions ourselves: 1. We plan to include the documentation for the API at the root of the API i.e. https://api.verelo.com https://api.verelo.com will serve up the API spec. 2. One thing that I want to ensure we avoid is simply having return values that are not explained anywhere in the documentation, Facebook drives me nuts for this reason. 3. The main API i've worked with recently has been Facebook. I love how much info it exposes, but i hate how much it changes and the lack of documentation. There are also a bunch of surprise functions in there, very frustrating. 4. We use a lot of Zend functions today, the Zend framework is my initial thought...