title: Profile/account REST API naming convention
body: <p>I have tried to search the net, but haven't found any example of best practice url naming convention for the following requests.<br>
  My API allows user to log into the system, retrieve secure token which can be used to access private data over the HTTPS.     </p>
  
  <p>So there following features will be support by API : </p>
  
  <ol>
  <li><p>Auth. Simple authentification. <code>/api/auth</code> will be used to log into the system first time and get token in response or refresh expired token if required.   </p></li>
  <li><p>View profile data (first name,last name, phone number ....). What is the best way to form url for this resource.  I have several ideas : <code>/api/users/me/profile OR /api/users/{id}/profile</code>. In the first case our client (REST API consumer) doesn't need to know exact ID of user, when user tries to access this resource it checks if token is valid,if passed user name exists and tied to the token, and than just returns data based on this information. In the second case we have to know exact ID of user, of course this ID can be returned in response to the auth.   </p></li>
  <li><p>Also other methods like <code>/api/user/me/orderlist, /api/user/me/someuserspecificinfo</code>.   </p></li>
  <li><p>What about making an order. I have read the if you need to create new resource you have to use POST, if update - PUT. How my url should look like ? </p>
  
  <p><code>/api/neworder (parameters in post body), /api/user/neworder , /api/orders (just with post method)</code></p>
  
  <p>.......</p></li>
  </ol>
  
  <p>Please suggest what the commonly used naming convention for such resources</p>