- Zerodha kite api price
Looking for:
kiteconnect · GitHub Topics · GitHub. |
Zerodha kite api price
Zerodha kite api price.Subscribe to RSS
It will cost you Rs. If it is monthly then why points? That is, one for trading and one for historical data feed. Currently, it is that you subscribe to basic trading package which is 2K and then add on the historical data package which is another 2K.
People like me who wish to access only historical data for the purposes of backtesting, will have to shell out 2K for services that they will not use, at least immediately. Let me know what you think?
Hi arkochhar , I will forward this request to the management. We will get back to you about this. Hi Sujit, we request you to provide some demo historic API access like 15 days trial period..
Also any timeframe for release of sandbox? Some information in this regard will be highly appreciated. Hi arkochhar , I have put a word across management. As of now to make it easy for users, we are not expiring historical API subscription when the base subscription ends. We will provide the sandbox feature in near future. However, deferring the Historical API expiry is not the solution. This is total waste of money I feel.
Also you must realise that your competition is fast catching up both in terms of quality and quantity. If you take these steps, there will less need for a sandbox. It is my sincere hope that some action is taken in this direction soon. I Up-vote this suggestion. I explained my reason after the quote- "Here is what I think you should do, split the Interactive and Historical API sign up and reduce the price for both.
Any login failure etc where you have to re-attempt a login and related session management is best managed when there is no inter-dependency of these processes and sessions. For the same reason having independent request rate for historical data and order placement is expected.
In summary, the order placement particularly exit on a volatile day is the most crucial one and must not be affected in any ways by other things like the historical data access. Sujith Kailash Nithin To further press my point, historical data API and order management API should be isolated fully and you should not have any reason to have common nodes at any point including both the backend hardware infrastructure or the software stack.
This doesn't seem to be in your system given the example of session management and rate limiting. Exchanges may reuse instrument tokens for different derivative instruments after each expiry.
The market quotes APIs enable you to retrieve market data snapshots of various instruments. These are snapshots gathered from the exchanges at the time of the request.
This API returns the complete market data snapshot of up to instruments in one go. Instruments are identified by the exchange:tradingsymbol combination and are passed as values to the query parameter i which is repeated for every instrument. If there is no data available for a given key, the key will be absent from the response.
The existence of all the instrument keys in the response map should be checked before to accessing them. If there's no data for the particular instrument or if it has expired, the key will be missing from the response.
Comments
Post a Comment