Collections are a resource so /appointments is fine as the resource. Collections also typically offer filters via the querystring which is essentially what users=id1,id2… is. So, /appointments?users=id1,id2 is fine as a filtered RESTful resource.
Option 1: $http service AngularJS provides the $http service that does exactly what you want: Sending AJAX requests to web services and receiving data from them, using JSON (which is perfectly for talking to REST services). To give an example (taken from the AngularJS documentation and slightly adapted): $http({ method: ‘GET’, url: ‘/foo’ }). success(function … Read more
The reason you get no hard answers is because there is no hard RESTful standard. So I can only suggest that you create a hard standard and stick to it within your own APIs I used this as a guide for RESTful services http://www.vinaysahni.com/best-practices-for-a-pragmatic-restful-api It says respond with a 204 status and an empty body … Read more
RESTful can be used as a guideline for constructing URLs, and you can make sessions and users resources: GET /session/new gets the webpage that has the login form POST /session authenticates credentials against database DELETE /session destroys session and redirect to / GET /users/new gets the webpage that has the registration form POST /users records … Read more
I have been doing some extensive research into this and other REST paging related questions lately and thought it constructive to add some of my findings here. I’m expanding the question a bit to include thoughts on paging as well as the count as they are intimitely related. Headers The paging metadata is included in … Read more
General principles for good URI design: Don’t use query parameters to alter state Don’t use mixed-case paths if you can help it; lowercase is best Don’t use implementation-specific extensions in your URIs (.php, .py, .pl, etc.) Don’t fall into RPC with your URIs Do limit your URI space as much as possible Do keep path … Read more
Best practice for RESTful API design is that path params are used to identify a specific resource or resources, while query parameters are used to sort/filter those resources. Here’s an example. Suppose you are implementing RESTful API endpoints for an entity called Car. You would structure your endpoints like this: GET /cars GET /cars/:id POST … Read more
You should use hyphens in a crawlable web application URL. Why? Because the hyphen separates words (so that a search engine can index the individual words), and a hyphen is not a word character. Underscore is a word character, meaning it should be considered part of a word. Double-click this in Chrome: camelCase Double-click this … Read more