Hi
I am creating Stock screener which will needed API to get Historical data of multiple stocks. As there are 6000+ stocks if I go one by one then API will hit Rate limit. Is there any API that can provide historical data for multiple strikes?
1 Like
Currently, there is no API available for retrieving historical data for multiple stocks.
Please introduce the option for getting historical data of multiple stocks in one API call.
Thank you for your feedback. Historical APIs are cached, and most of the time, responses are served directly from the cache, which enhances performance. Currently, we are not planning to introduce functionality for retrieving data for multiple stocks in the near future.
1 Like
@Pradeep_Jaiswar
You can provide API which accepts multiple stocks and you can internally get cached data for specified periods which will reduce API calls.
Thank you for the suggestion. We will forward it to the appropriate team.
Or you could simply increase the 30-minute rate limit on API calls from 2,000 to something like 5,000. The need for multiple API calls usually arises when someone is trying to build a custom stock screener that requires historical data for the entire universe of stocks, which most traders would want to do at some point. A limit of 2,000 API calls per 30 minutes is too restrictive for such a use case. You can keep the per second and per minute rate limits unchanged or even introduce a new 5 minute rate limit to avoid any misuse of API calls. But having to wait 30 minutes to get the data for the rest of the instruments is not very unfavourable.
@Aravind_1224407 - Thanks for sharing your thoughts. Weāll pass them along to the team and take appropriate action if aligned.
I am also facing a lot of issues with rate limits. It will be great if you can increase the API rate limits for the calls which are not related to orders.
any progress on this? so we could download only single instrument data at a time?
sir aap log websocket ko aggregate karke kyun nai dete customer time frame mein jaise elk layman ko chart mein dikhata hai real time mein . aapke websocket mein 1m and 1 day available let suppose kisi ko weekly chahiye kisi ko monthly kisi ko 15min dusri baat aaplog histroical candle ke sasaath usko attach kyun nai karke dete sir.
@ABHISHEK_2564441 bhai, Web socket live data k liye use hota hai. weekly, monthly data to live hi milta hai api se to usko web socket se fetch karne ki koi zarur nahi hai. but if you want for shorter timeframe like 5, 15 minutes than it can be use it but ek minutes se aap convert kar hi sakte hai isko.
mujhe pata hai mere bhai historical candle data ko jab websocket se merge kar denge tab tumko chart jaise dikhega and tabhi algo fast kaam karega . i hope if u have already made algo , only then u will be able to understand what i am trying to say
Iske liye aap pahele historical data fetch karlo API se jab paheli bar websocket connect ho tab fir web socket se jo data aa raha hai usse next candle banate jao. Me ye hi karta hu. Muje jo timeframe me data chahiye uske historical data download karke next minutes ka data websocket se bana leta hu. Because aap jo bol rahe ho wo Upstox nahi karne wala because unhone wo remove kiya hai websocket se. Pahele daily, 30minutes, previous minute, current minute ye data aata tha fir unhone sab remove karke sirf daily and previous candle ka data hi rakha hai
tab to upstox ne blunder kar diya hai because wohi to chahiye tha.
dear kya aap ek cheez bata sake ho let say mereko continous series of data chahiye to mein kaltak ka data historical se fetch kar lunga and use kebaad aap bol rahe ho ki aj mornign 9:15 se data ko aggregate karna padega but let say maine system on kiya dopahar 12:03:32secon pe tab kaise karenge 9:15 se leke 12:03:31 secon ka data kaha se leke ayenge . kindly reply
pahele historical then aaj ka data via intraday and then continue with websocket.
Ab to shayad historical v3 api bhi aaj ka data de raha hai
15 days pehle maine bhi yahi dimag lagake kiya tha and kuch had tak successbhi ho gaya tha but isme ek issue hai will get back to you