In JSON API, representation of multiple similar objects are in arrays form, is problematic. For example,in entrypoint /api/hosts: The XML for options under power_management is: <options> <option name="port" value=""/> <option name="secure" value="false"/> </options> but the JSON representation is: "options" : { "options" : [ { "name" : "port", "value" : "" }, { "name" : "secure", "value" : "false" } ] } so options inside powerManagement is an object containing an "options" field which is an array of objects. I think it should be that options field of powerManagement is an array of objects directly. This is happening in other locations too, I think the code groups similar xml objects in a single json field with plural form name. in cases where it's the only type of elements, it should be grouped directly.
i'm aware of this issue, but this is schema modelling since 2.2 which cannot be changed in sake of backward compatibility