I wish to write a webservice which serves lists of JSON objects. Is it valid JSON to return the following:
[
{"keyA1":"valA", "keyB1":"valB"}
,{"keyA2":"valA", "keyB2":"valB"}
,{"keyA3":"valA", "keyB3":"valB"}
]
Or is the "right" way to do it to put it in a single object to return:
{"elements":[
{"keyA1":"valA", "keyB1":"valB"}
,{"keyA2":"valA", "keyB2":"valB"}
,{"keyA3":"valA", "keyB3":"valB"}
]}
Answer
Both forms are valid. However, for an API, I would recommend the second form. The reason is that it gives you a path for expansion of your API.
For example, if you have an API getUsersInGroup
which returns an array of user objects, and later you decide you want to include, say, some aggregate statistics about the users being returned, there's no easy way to do that without breaking existing clients (or including lots of redundant data in each user object). If you use an object, you simply add another field to the object which is silently ignored by clients on a previous version of the API.
In short, try to avoid top-level primitives wherever possible in your API, and you'll find it easier to expand in the future.
No comments:
Post a Comment