Hi @rohit3389,
I am not sure how you are doing the test. But, we have verified the total buy and total sell quantity, it seems fine.
The total buy quantity is the sum of all the buy pending order quantity at the exchange and there will be no correla…
@RH1558,
We couldn't observe the behavior on our latest version of client libraries.
There are two things to be noted here, total buy and total sell are not cumulative values. Those are just the snapshot values. There is no relation between the tota…
The order status will remain same as is in partial fill scenario.
In this case if a limit order has PENDING status before partial fill it will remain same after the partial fill.
You can check filled quantity field to figure out a partial fil…
You can use user margins as mentioned here.
You can find python documentation here.
For response structure and its details, you can check API documentation.
There can be hundreds of ticks at exchange per second but it can't be captured by any trading platform via internet. You need a colo setup at the exchange to get all the ticks.
You can check out Nithin's answer here for better understanding.
We don't have API for that as of now. You can use the same google sheet to track equity instruments and for banned F&O instruments you can check out this link https://nseindia.com/products/content/derivatives/equities/sec_ban.htm
You can subscribe for any token any time during the execution. Consider you already have a connection and getting ticks for RELIANCE and HDFCBANK, you can subscribe to TATASTEEL as follows,
Ticker.Subscribe("TATASTEEL")
The same rule applies to u…
Kite Connect is purely an execution platform. You will have to write strategies at your end and place order using any of the Kite Connect client libraries.
One can only give trigger price to the SL-M order, once a trigger is hit a market order is punched at the exchange.
One can't guarantee the price of execution in case of stop-loss market order.
You can check out more about cover order here.
Hi @rvsw,
There may be inconsistencies in the data minute-level data pre-mid-2016. This was before the time when our system for constructing minute candles was fully stable. As such, for the older entries, it is possible that you see inconsistencies…
Hi @Parva,
In simple words, Kite Connect is just a library which makes HTTP API calls. Once you have access token you can make an API call from any thread. There is no restriction at the library level. You can just spin off a new thread and make API…
Hi,
The second leg of a cover order is of type SL-M which means you can only set trigger price for the stop-loss order.
You can't set a price for the same.
Hi,
We are looking into the issue. Debugging this is an issue because it is not consistent behavior. According to your observation, it is very often.
Can you let us know more about your application so that we can make a similar setup and reproduce i…
Yes, your order modification request will be rejected if the circuit limit is not revised. So you can only modify after the new circuit limit is published by the exchange.
There are two types of stop-loss orders we support one is SL (stop-loss limit) and SL-M (stop-loss market). A SL will have price and trigger price. A SL-M will have only trigger price.
For more information check out this article.
Yes, you are right. When you place a modification request it goes through RMS validation and other series of processes before it is being modified. If it fails in between then order entry will have the status message which explains the reason of fai…
If you have set the mode to full then you will receive data whenever there is a change in any of the fields in the full mode.
If you feel like data is repeated then probably you should be using some other mode.
You can check the documentation for mo…
You will receive tick data whenever there is a change in any of the fields. The snapshot can be exactly the same as the previous one and only one of the values must have changed. We just stream whatever we get, we don't publish ticks on our own.
In a generic way what I would suggest is create a ticker connection and keep receiving ticks on the main thread.
Inside onTick, create a new thread or use an existing second thread which will only do DB writes. In this way the DB writes are offloade…
If you subscribe for full mode then you will receive data for every change in any of the market depth field.
If you want the tick only when LTP changes then subscribe for LTP mode.
You will receive order id in response after successful placement of an order, you can fetch the orderbook after placing an order and check for order status.
It is not a bug from the system's end. It will just place an order with whatever input user gives. If your stop-loss and target are nearby it can happen.
Even though you have enough difference between target and stop-loss during volatile markets it …
You can check out the status_message field of the response. It says "BO: Self Trade Rejection". This is because, at that point in time, the same user was buyer and seller which is why the order was rejected.
Both the orders are rejected with the sa…
Yes, you need to pass the quantity every time. Kite Connect doesn't provide default quantity.
You can check out documenation for information about live market data.
Hi,
We only provide historical candle data. We don't provide EOD report.
For more information about the historical data, you can check out the documentation.
The tradingsymbol would be UNIONBANK18OCTFUT and lot size is 6000.
You can download the CSV file using the URL provided in the documentation and find the entry in the dump for more information.
Hi @nikhilbansal,
You need to use multi-threading, the idea is to never block the main thread on which you are listening to ticks. I am guessing your DB writes are the reason for unavailability of the process when the tick arrives.
The right soluti…
Can you elaborate on which instrument you observed this and on which date?
Are you referring to normal or bracket order?
Do you see order type field changing from SL-M to SL?
The Kite Publisher will just make API call in parallel, the order of execution is not guaranteed. A feasible solution would be to use Kite Connect app.
Hi @Dinesh1473,
This forum is dedicated only for Kite Connect related queries, please write to support for other queries.
AFAIK, this means bracket orders are not allowed for that instrument.
The philosophy of the PHP is a little different than other languages.
I don't think PHP supports websockets either. You can try javascript or python client of Kite Connect.
Kite Connect is purely an execution platform. We don't provide support or solutions for developing strategies.
You can go through announcement threads, it has some example resources built by the community developers which might help you to get start…
Posting on behalf of @HowUTrade,
@catchmaheshkcf
RTD is client-server model and works on the principle of Push-Pull mechanism.
GetOrder* is a function and you (Excel) need to call this everytime you want result.
Event handling in VBA is more com…
This is an endpoint to generate the session. Kite Connect doesn't provide a dedicated endpoint to check if a session is active. You can make any API call, if you get 403 then it means your session is invalid.
An access token is valid for one whole day.
It will not expire unless you try to generateSession again.
You need to store access token and reuse it for subsequent runs.
