Rate Limit Trigger in get_hist

Khor

caling get_hist for historical data.
the flow is getting the consititute of Index like IDX and SPX, knowing the constitute then enquiry history data of 500 company for 20 days data , for example SP500.
Then, for top 100 most traded company, find option chain for each of them, getting the option ticker RIC.

get history data multiple of 100 of symbol.

flow :
1. get consittuate of SP500 from Chain
2. get_hist of 500 company for 20 days data, interval = day
3. get top 100 most traded company
4. each company get option Chain
5. get history of option chain symbol in mutplie of 100, start day 8/7/2025, end day = 9/7/2025, interval = minute
from 1-4 getting NVDA option Chain, up to 2000+ option symbol.
5 ld.get_history(universe=[ here is 100 option symbol], startday, enday, onterval=minute)

• using python lseg.data as ld, calling ld.get_history

end up i have call the get_history in number of 40++ times, accumulated dataframe return size of 200MB, and then trigger 429 rate limit.

Please assist

Gurpreet

Hello @Khor

There is no way around the rate limit. Workspace and API data is bound by hard limits as described in this Usage Limits document. If your application has need for more data, then an enterprise product like RDP or DSS would be a better fit. Please speak with your LSEG account manager to get access to these products.

Khor

Hi there,

i just want to know in my case which part of my calculation of the limit is wrong and causing rate limit trigger.
based on my calculation, it seems not reasonble.
100symbol and in minute interval, given the feiield is around 10 * 100 symbol * around 390 row

even i chg to 5min and 65 symbol per rest api call, and call take 30s, and still i get 429 tooo many request… I only call 50 times and dataframe size is just less than 1MB and less than100 rows

https://community.developers.refinitiv.com/discussion/comment/127118#Comment_127118

Gurpreet

https://community.developers.refinitiv.com/discussion/comment/127149#Comment_127149

Unfortunately, we don't have access to product/server logs. I would suggest contacting the LSEG MyAccount to raise a ticket for product support and refer this discussion.