I don't think you are making a convincing argument for your point. Most likely it will be a developer interpreting the api and generally speaking they are like

I don't think you are making a convincing argument for your point. Most likely it will be a developer interpreting the api and generally speaking they are likely to want some flexibility in how you query a resource. I would say your proposed suggestion is much more limiting, you have basically removed the query string and changed the name. So your proposed version returns all the data, in most notorious order, that could be tonne of data. You are going to need query strings for paging and filtering and sorting..this is perfectly good api design. I would recommend odata.org for a read. I would also recommend apigee.com white paper on good api design. Also with versioning in mind, you may wish too include api/v1.x/mostwanted