Problem Retrieving 1 time series via Python API


I’ve been using your Python API successfully for some ttime, but I’m unable to retrieve this specific dataset:

When debugging, I found that series with data are initially retrieved fine, but then in your “fetch_series_by_api_link” method (lines 233-236) it breaks in a loop where it tries to retrieve “Industry” dimension, which, I think, maybe was not populated properly for these time-series.

Could you advise me how I could retrieve these time series with Python?


Thanks for your feedback. If I understand well, the problem is:

df = fetch_series('BEA/NIPA-T11706/A191RX-Q')

KeyError  Traceback (most recent call last)
<ipython-input-9-da4c1b56e5b7> in <module>
----> 1 df = fetch_series('BEA/NIPA-T11706/A191RX-Q')

~/dev/jailbreak/dbnomics/dbnomics-python-client/dbnomics/ in fetch_series(provider_code, dataset_code, series_code, dimensions, series_ids, max_nb_series, api_base_url, editor_api_base_url, filters)
    167             raise ValueError("When you use `series_ids`, you must not specifiy `provider_code` nor `dataset_code`.")
    168         api_link = series_base_url + '?observations=1&series_ids={}'.format(','.join(series_ids))
--> 169         return fetch_series_by_api_link(api_link, filters=filters, max_nb_series=max_nb_series,
    170                                         editor_api_base_url=editor_api_base_url)

~/dev/jailbreak/dbnomics/dbnomics-python-client/dbnomics/ in fetch_series_by_api_link(api_link, max_nb_series, editor_api_base_url, filters)
    233         if 'dimensions_values_labels' in dataset_dimensions:
    234             for dimension_code, dimension_label in dataset_dimensions_labels.items():
--> 235                 dimension_value_code = series_dims_by_dataset_code[complete_dataset_code][series['series_code']][dimension_code]
    236                 flat_series[dimension_label] = dict(dataset_dimensions['dimensions_values_labels']
    237                                                     [dimension_code])[dimension_value_code]

KeyError: 'industry'

I created an issue in our Gitlab to treat this. I can’t tell when we’ll plan to treat this. Probably not this week unfortunately.

But, as DBnomics is open software, if you identify the bug (and apparently you did well :+1:) and find a way to solve this one, we’re very open to pull requests ! You can communicate with us here to ask questions if you have some.

Have a good day

Hi @bruno.duye ,

Thank you very much for your quick reply.

Yes, I believe this is the problem, but I’m not sure yet how it could be resolved (DBNomics is a new thing to me, I need to spend some time understanding how it works). But I will think about it and will let you know if I get any ideas.

In the meantime, I think I found a lot more examples that fail in the same for loop that we identified above. Not sure if it helps to resolve the issue, but I’ll summarise my findings below just in case.

  1. I cannot retrieve any except Total index (i.e. FED/G17_IP_MARKET_GROUPS/IP.B50001.S) time series from this data group:{"FREQ"%3A["129"]%2C"SA"%3A["SA"]}

  2. I cannot retrieve some time series in this data group:{"FREQ"%3A["129"]%2C"SA"%3A["SA"]}. Examples:
    – FED/G17_CAPUTL/CAPUTL.G325212.S
    – FED/G17_CAPUTL/CAPUTL.G32522.S
    – FED/G17_CAPUTL/CAPUTL.G33611.S
    – FED/G17_CAPUTL/CAPUTL.N325211.S

  3. I cannot retrieve many (maybe all, haven’t tested all) from this data group: Consumer Credit Outstanding [G19_CCOUT], examples:


I think all of these are related to the same for loop issue.

Thanks a lot for looking into this and your work developing this amazing database! Once I get something useful out of my economics research, I’ll make sure to share the credit :slight_smile:


Hi Aiste,

I can explain your FED problem, which is different from the BEA problem. We had to modify a bit the series code of FED series, sorry (the Fed gave sometimes more than ones series even when we specified a value for each dimension).

Now you can download all the series if you use the mask, as explained here (, Fetch time series by code mask). In your example 1, you should write : fetch_series("FED", "G17_IP_MARKET_GROUPS", series_code="129..SA") and you will obtain the 63 different series, as in the DBnomics website.

Equivalently, you could use the Fetch time series by dimension :
fetch_series("FED", "G17_IP_MARKET_GROUPS", dimensions={ "FREQ": ["129"], "SA": ["SA"], })
and you will obtain the 63 series.

Thank you for your interest in DBnomics!

Not sure if this is the same issue, but some things are kind of weird in the FED/G17_CAPUTL area. For example the series CAPUTL.B50001.S. If you download this (JSON) with


you get 53 valid observations (out of 637 periods). The data are supposed to be monthly, but these values seem to pertain to the 28th of February in each year, with other months’ data all missing. But if you use


you get 637 (apparently) non-missing observations. This is not easy to understand!

Hi @thomasbrand,

Thank you very much! I will be looking into this again this week. I’ll try your workaround and will you know if it works.

Many thanks,

Hi @thomasbrand,

I hope you’re well!

I’ve been looking at this issue, but I still can’t figure it out…

So I extracted 3 examples that either work or don’t when retrieving data using Python API:


  1. Germany GDP: DESTATIS/81000BV007/DG.VGRPVK.X13JDKSB.VGR014

Not working:

  1. Spain GDP: INE-SPAIN/30679/72.b1gq.l.y.00.index
  2. US GDP: BEA/NIPA-T11706/A191RX-Q

I find that the issue with the not working series is in this method: fetch_series_by_api_link(api_link, max_nb_series=None, editor_api_base_url=default_editor_api_base_url, filters=None), lines 233-237, i.e. that’s where the code breaks for not working series.

If I look at ‘series_infos’ when trying to retrieve each of the series, I can see that in the case of Germany, ‘dimensions’ and ‘dimension_labels’ objects match, i.e.: there is a key equivalent in both the objects.:

‘dimensions’: {
‘DINSG’: ‘DG’,
‘WERT05’: ‘X13JDKSB’,
‘freq’: ‘Q’,
‘ind’: ‘VGR014’,
‘unit’: ‘jew_me’

‘dimensions_labels’: {
‘DINSG’: ‘Germany’,
‘VGRPB5’: ‘Price base (current prices / price-adjusted)’,
‘WERT05’: ‘Original and adjusted data’,
‘freq’: ‘Frequency’,
‘ind’: ‘Indicator’,
‘unit’: ‘Unit’

But when I look at Spain time series, I can see there are 2 additional key-value pairs in it’s dimension_labels object.:

‘dimensions’: {
‘3’: ‘72’,
‘482’: ‘b1gq’,
‘501’: ‘l’,
‘544’: ‘y’,
‘nac’: ‘00’,
‘units’: ‘index’
‘dimensions_labels’: {
‘3’: ‘Type of data’,
‘501’: ‘Prices_ESA’,
‘544’: ‘Correction of effects’,
‘nac’: ‘National Total’,
‘units’: ‘Units’

Similar thing happens with the US GDP:

‘dimensions’: {
‘FREQ’: ‘Q’,
‘concept’: ‘gross-domestic-product-gdp’,
‘metric’: ‘millions-of-chained-dollars’,
‘unit’: ‘level’

‘dimensions_labels’: {
‘FREQ’: ‘Frequency’,
‘concept’: ‘Concept’,
’industry’: ‘Industry’,
‘metric’: ‘Metric’,
’sub-industry’: ‘Industry precision’,
‘unit’: ‘Unit’

So because of these additional key-value pairs, the code breaks when it iterates over ‘dimensions_labels’ object and tries to find all key-values in the ‘dimensions’ object.

Unfortunatelly, I don’t know why in the case of Spain or the US these ‘dimensions’ and ‘dimensions_labels’ objects are different in terms of lenght.

There are many more time series like this, I was wondering if you guys are aware of this issue and or know the workaround?

Thank you!

Have a great day,

Hi @enzo,

I hope you’re well!

I was wondering if there is any chance you could update me on this issue? I was wondering if maybe it’s so blocked that it’s perhaps impossible to resolve? :confused: In which case I would try to get that data somewhere else… which would be a shame because I love using DBNomics!

Thank you :slight_smile:


Hello @snaiste,

I have notified our developer of your issue and he will be working on it this week. We will keep you informed of the progress :slight_smile:

Thank you for contacting us!


Hi @enzo,

This is great, thank you very much!


1 Like

Hi @snaiste

I hope you’re well!

I’ve a good news for you (and this is not an April fool!): the problem you mention in the top of this thread has been fixed :tada:
The new version 1.2.1 should fix this problem.

I’ve to congratulate you: you isolated the problem on this comment !

Let us informed

Thanks again, and sorry for the delay !


Hi @bruno.duye,

I’m well, thank you, I hope you’re enjoying the Spring time too!

Wonderful news, thank you very much! I’ve just installed the new version and now it works very well for all examples I’ve given in this thread! Thank you very much, this is super helpful!!!

Have a great day,


Great, I’m happy to read this ! Spring is strange this week, it snowed today in France :astonished:

Have a good day !

1 Like


O wow! London is colder than usual, but no snow since winter :relieved:!

Thanks guys for your work once again, very helpful!

1 Like