# DBnomics API v22 released

**URL:** <https://dbnomics.discourse.group/t/dbnomics-api-v22-released/204>\
**Category:** Community\
**Created:** [December 20, 2018, 5:36pm UTC](https://dbnomics.discourse.group/t/dbnomics-api-v22-released/204 "2018-12-20T17:36:19Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![acottrell](https://avatars.discourse-cdn.com/v4/letter/a/c68b51/32.png) [@acottrell](https://dbnomics.discourse.group/u/acottrell)\
**Post date:** [December 25, 2018, 6:37pm UTC](https://dbnomics.discourse.group/t/dbnomics-api-v22-released/204/4 "2018-12-25T18:37:42Z")

</div>

Having experimented a bit further I have two comments on the v22 APIs.

1. The new path `/datasets/{provider_code}` (“Respond datasets of a provider.”)

This could do with fuller documentation. The “limit” and “offset” parameters are  
not mentioned under apidocs/v22, and it’s perhaps surprising that the default  
limit is 10 (given that some providers have thousands of datasets).

1. The element “observations\_attributes” which appears under series.docs  
in some cases.

This element is represented as an array of arrays. For example under  
`IMF/CPI/Q.BE.PCPIT_IX` we have:

`"observations_attributes" : [["REFERENCE_PERIOD", "2013A"]]`

Making the inner element here an array suggests that “REFERENCE\_PERIOD”  
and “2013A” have the same logical status, but I guess it’s actually a matter of  
key plus value, in which case it would be more transparent to represent the  
inner element(s) as JSON object(s):

`"observations_attributes" : [{"REFERENCE_PERIOD" : "2013A"}]`

---

_[View the full topic](https://dbnomics.discourse.group/t/dbnomics-api-v22-released/204)._