@Bhavninder, You need to use one websocket connection unless you are subscribing for more than 4k instruments.
Edit: Current limit is 3k, the new limit is 4k
@Bhavninder,
I am afraid you can't use our Websocket data to display live market data on a third party website. You may need to check with compliance first. You can write to kiteconnect(at)zerodha.com to reach out to the compliance team.
@sbdavra,
We don't see any issue from our end. Even I tested it multiple times. Anyways we have asked the team to revert it for now. We will take it live again soon.
@all
Please make sure you don't exceed a maximum of 3 websocket connections per api…
@sbdavra, @sunny,
The change mentioned here was taken live yesterday.
We had given the deadline way before 8th October 2020. We have always told people to keep the maximum simultaneous connections up to 3.
@rahulbhayana,
We don't provide one-to-one…
This happens when some required field is missing while modifying an order. Can you run javakiteconnect in debug mode and give the request and response logs when this happens?
This is a message from the OMS. Can you private message the client id and order id for which this happened?
We will check and get back to you.
This could be because you modified order more than 25 times.
We have provided the curl examples and the response structures in the documentation.
For type strict languages, we have provided a detailed explanation in the client library documentation itself.
You can check out the javadoc here.
It seems like you are doing processing upon receiving the postback. You just receive the data, return the response, and then do your logic.
We see a lot of timeouts because your system didn't respond.
The target order is limit and the stoploss order is SL, but you may also need to note that once the trigger is hit the stop-loss order also becomes LIMIT type. In that case, you need to look at the price and decide.
The OHLC API gives you the day's OHLC but the candle data will give you OHLC for the minute or any other specified interval. Can you let us know what are you looking for?
Our RMS blocks all the orders after market hours which will throw a Kite exception with a message as mentioned here. However, for the convenience of the Kite Connect users, we allow placing orders for ICICIBANK of NSE. You can use that for placing d…
The OHLC API gives you the day's data and not 5 minutes candle data.
If you are looking for candle data then you need to build candles at your end using live market data provided on Websocket API. You can get started here.
You will have to maintain a data structure of the holidays and use that to remove unwanted data.
You may also need to note that during muhurat trading the trading starts at 05:30 PM.
@haricoolharan,
We provide whatever data we have. If you are not satisfied then you can go ahead and get the data from any other exchange registered data vendor.
We don't guarantee any timeline for order processing. If you are working on a latency-based strategy then I would suggest not using Kite Connect.
You may go for a colo setup at the exchange which would cost upwards 18 lakhs/annum. You can write to …
Though only one session is allowed for an app, you can run multiple programs with the same access token.
You can listen to ticks, do calculations, and place orders.
I would suggest going through this thread. Make sure to read comments as well.
If you need data for every 5 minutes then I would suggest using quote API.
One can have only one active session at any point in time for a Kite Connect app.
@tfKamran,
We don't have any plans of providing an API for fetching the list of illiquid instruments. You can write a script and take it from the google sheet.
If you are sending a current month instrument token and the current month from and to date then you will receive the current month instrument data.
If you pass the current month instrument token and send last month's from and to date then you will r…
We provide continuous data for only futures instruments and in day interval only.
Can you elaborate, what is the meaning of assumptions regarding the roll dates?
The historical data is built using a different stream which is the same as the Websocket API. It is off because it might have missed ticks. We have asked the data team to take a look at this.
You can track progress on this thread itself.
@rajeesh31,
The Quote data comes from the exchange, so it will be the correct data always. We will ask the data team to take a look at the candle data.
It is not available yet. We will include it in future releases.
If you want it right now then I would suggest fork the kiteconnectjs and add oi param here.
The exchange allows institutions to settle or close positions after market hours. Hence you need to use the OI provided in the BHAV copy since it includes the post-settlement data for the day.
Though you receive 200 for delete request which means your request was successfully placed, the action was not carried out by the OMS because of the variety mismatch.
@Gopikrishnan,
It is on our list of things to do. I am afraid we can't give any timeline as of now. If you want to use it now then you can go ahead and fork the library, the client libraries are open source.
It is basically an exit order which uses the same cancel order API with parent order id.
If you don't send a parent order id then API will cancel it as a normal order and you will be in trouble end of the day since RMS looks at it as a hanging posit…
