Show HN: Eligible API for 700+ Health Insurance Companies
The deeply nested JSON (9 levels) seems difficult to understand without some kind of schema/detailed docs - though maybe domain users are already familiar with the underlying data's schema?  Part of the problem is intrinsic data complexity, aside from EDI format. <a href="https://eligibleapi.com/restful-json-api/response" rel="nofollow">https://eligibleapi.com/restful-json-api/response</a><p>Also, it's simulating JSON [] lists as objects with fields named <i>"Item #1", "Item #2", ...</i>  Seems an odd choice. e.g.<p><pre><code>  "Deductible": {
    "Item #1": {
      "Calendar Year": "1500"
    },
    "Item #2": {
      "Remaining": "500"
    }
  },
</code></pre>
EDIT: To clarify, below is the same snippet using JSON lists.  The list syntax gives schema information (i.e. that it is a list), and is standard, readable and concise.  Most parsers will map it to a list in the destination language, making it more natural to address and loop over; i.e. easier to process in general.<p><pre><code>  "Deductible": [
    {
      "Calendar Year": "1500"
    },
    {
      "Remaining": "500"
    }
  ],</code></pre>