Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

2
  • I think that there is no "standard". I would approach this case by case. For example, I would do /api/language/en-us/people, and /api/country/uk/people, etc. well, true, this might not be as flexible as your query string approach, but do you need this flexibility? Commented Sep 7, 2013 at 3:40
  • That is a good idea, but unfortunately I'm looking to keep one resource (ie: people), and query based off of that. Also "people" is just an example and not my actual use case, but with the right pattern it can apply to anything I assume. Commented Sep 7, 2013 at 14:45