Infrastructure: Refactor API for consistency

[jdmedlock]

As a Web Developer I need an API that is consistent and logical so I can easily understand it.

Our API URLs are not consistent in their composition and the way parameters are passed. As an alternative consider the following API composition rules:

• Use lower case
• Replace %20 (spaces) with dashes
• Format as '/entity/parameters...' where

1. Entity is the name of the data element being operated on. For example, idea, user, review, agreement, etc.
2. The action to be performed is implicit by the type of HTTP request being made - GET: retrieve, DELETE: remove, PUT: create, POST: update
3. Logical keys identifying the entity to be operated on should be passed as parameters. Properties and their values should be passed in data.