DSWS API returns invalid data

sam.macaluso
sam.macaluso Newcomer
edited December 2024 in Datastream

Hi,

When I execute the following via the DSWS API I receive the following data:
ds.get_data(tickers = '8857RL', fields = ['DSCD','ENAME','ISIN','RIC','T1C','LEI',] ,kind = 0)

image.png

When I use the same DSCD in the web portal, the ISIN is correct.

image.png


When I try to search the web portal for the ISIN returned by the API, I receive no data

image.png

The same happens when I try and search the API for the ISIN the web portal returns, I receive NA for all values.

image.png

This happens often and I don't know if I can trust the data received from either source. Is this a bug?

Best Answer

  • JamesBright
    Answer ✓

    The Datastream product is reflecting the correct ISIN, I can see there was a stock split (4:1) yesterday which is why the ISIN changed:

    Type

    ISIN CODE

    8857RL

    US0404132054

    Navigator changes take 24 hours to reflect so I expect the update will be made within the next few hours

Answers

  • Hi @sam.macaluso,

    Please note that this LSEG Developer Q&A Forum is for LSEG API technical questions only. For content questions such as yours, we would usually ask that you please use myaccount.lseg.com.

    With that said, I reached out to our internal team myself to let them know that I checked this dicrapency myself. Indeed, the ISIN showing up in the Datastream Navigator for company ‘ANET.K’ (tickers = '8857RL') is incorrectly showing as US0404132064 when it should be US0404132054.

    I will reach out to you on this Developer Community Q&A Forum as soon as I have an update.

  • Hi @sam.macaluso, Thank you for your participation in the forum.

    Is the reply below satisfactory in answering your question?

    If yes please click the 'Accept' text next to the reply, and then close the question. This will guide all community members who have a similar question.

    Otherwise please post again offering further insight into your question.

    Thanks,

    AHS

  • Hi @sam.macaluso

    Please note that the answer above was marked as accepted. Please let us know if that's incorrect.