Hello @vlad.dimanshteyn,

I suggest for the best explanation of the Refinitiv Eikon content to engage with Refinitiv content experts directly, via Refinitiv Helpdesk Online -> Content -> Eikon.

My limited explanation, re your comment:

"/" in the instrument, "0#/SPXW*.U" is the delayed version of chain RIC "0#SPXW*.U". That is the instrument your Eikon user is permissioned for. The delay is set and differs per exchange and sector, a very common delay is 15 min, you can also check with the public listings of the delays, including Delayed Market Data Timing, or to confirm the delay for the specific instrument- Refintiiv content support are the experts who can help you the best.

Many of our APIs and libraries, including Eikon, if you do not have the permissions for the realtime instrument, and if there is an analogous delayed instrument, will switch you to the delayed instrument, seamlessly. However, in this case, the chain is still very large, and will still sometimes time out on the request.

What I have suggested, is the explicit workaround, that should allow you to proceed as of this time, as permissioned. And again, once Refinitiv Data library matures, there will likely be a more elegant approach available for this use case, but the specifics will depend on the API improvements. In my opinion, at a minimum, you should be able to do both of the steps, expand and request, with RD lib, without needing to use RDP lib for the fully reliable chain expansion.

Hi @vlad.dimanshteyn ,

For questions on content, such as how to identify the content that you require, the best approach for a customer is to submit them directly to Refinitiv content support, via Refinitiv Helpdesk Online -> Content -> Eikon and your question will be assigned to the appropriate content expert.

This developers forum can be of most help to you with API usage questions, the moderators of the forum do not have the in-depth knowledge of the many types of content that is made available by Refinitiv.

From my looking, this chain is an OPRA .SPX option chain. You can test "0#SPX*.U" which is also an OPRA .SPX chain, results now in 7363 results, which is also a lot. You may wish to increase the timeout, as discussed in this previous discussion thread.

To get a definitive answer on the instruments/chains available, and per your requirement, please engage with content support directly and include all the details of the requirement for content. If you are not able to proceed as suggested- also let us know, and will give a hand by submitting on your behalf.

Hi @vlad.dimanshteyn ,

If you would like to request 0#SPXW*.U , every time, guaranteed, here is a little "divide and conquer" approach example that is not very elegant, but works, from my testing, consistently:

1. Expand the OPRA chain into constituents with RDP library:

import refinitiv.dataplatform as rdp
rdp.open_desktop_session(APP_KEY)  # your valid APP KEY
stream = rdp.StreamingChain(name="0#SPXW*.U")
stream.open()
constituents = stream.get_constituents()

2. Chunk the list and request the fields in chunks- this part can be done with RDP, RD or EK, I am including EK, as this is what you have been working with prior:

def list_to_chunks(long_list, chunk_size):
    chunked_list = list()
    for i in range(0, len(long_list), chunk_size):
        chunked_list.append(long_list[i:i+chunk_size])
    return chunked_list
#
import eikon as ek
ek.set_app_key(APP_KEY)  #you valid APP KEY
myRicChunks = list_to_chunks(constituents, 5000)
for i in range(len(myRicChunks)):
    print("Chunk #", i)
    option_chain, err = ek.get_data(myRicChunks[i], ['TRADE_DATE', 'ACVOL_1'])
    print(option_chain)
    print('Err=',err)

... as RD lib matures, it should allow for the best implementation for this requirement, as for many of the others it already does

Hi @vlad.dimanshteyn ,

The test with CodeBook console should work. You can either print constituents, or the quickest is just printing their length.

I test in CodeBook with Python Notebook, as that allows to test one by one, the sections of the book, but this is just a convenience:

I see 13106 at this time. Let me know

Just ran the whole thing

Hi @vlad.dimanshteyn

As a sanity check only, the exact same code in CodeBook with name="0#SPX*.U" works for you and returns 6490 constituents after a wait?

And with invalid instrument name="FAKERIC" comes back very quickly and returns 0 ( because the stream will be opened, even if the instrument is invalid or you are not entitled), but returned constituents will be empty?

If that is the case, as the code is the same as works for me, in Codebook (same libraries and same versions) and you are failing on your side for this chain, I would suggest to open a support case with Refinitiv helpdesk, to verify that you are permissioned for this instrument.

I did not think so from your initial question, as you have mentioned a timeout, that I have seen as well on my side, from time to time.

Hello @vlad.dimanshteyn ,

Try replacing in streaming code

import refinitiv.dataplatform as rdp
rdp.open_desktop_session(APP_KEY)  # your valid APP KEY
stream = rdp.StreamingChain(name="0#/SPXW*.U")
stream.open()
constituents = stream.get_constituents()
len(constituents)

This should allow you to retrieve chain constituents as delayed, which for the purpose of identifying the constituents should not make any difference, in my understanding.

In addition, with my chunking code, go 2k step:

def list_to_chunks(long_list, chunk_size):
    chunked_list = list()
    for i in range(0, len(long_list), chunk_size):
        chunked_list.append(long_list[i:i+chunk_size])
    return chunked_list
#
import eikon as ek
ek.set_app_key(APP_KEY)  #you valid APP KEY
myRicChunks = list_to_chunks(constituents, 2000)
for i in range(len(myRicChunks)):
    print("Chunk #", i)
    option_chain, err = ek.get_data(myRicChunks[i], ['TRADE_DATE', 'ACVOL_1'])
    print(option_chain)
    print('Err=',err)

Let us know how this works on your side.

Thank you Zoya, you helped me out big time !!!!!!!!!!!!!!!!!!!!