Hi @sahilsingh,
There many instruments which are of T2T segments in that dump. Normally instruments are traded on EQ segment. So, if you are requesting data for T2T segments then it will not have data. There can be F&O instruments also if you ar…
Hi @sahilsingh,
It is not an error. It means candles doesn't exist for the instrument user has requested for.
Maybe the instrument was not traded on the day you had requested for.
Hi @sudhirshettyk, @skk,
We understand your concern.
We are planning to increase the number of requests in Kite Connect 3.
We have also provided ohlc and ltp endpoints for up to 200 scrips in one HTTP calls.
In order to back populate, historical API…
Hi @sunny,
Yes, you need to open an account with Zerodha to use Kite Connect APIs.
You can start from here.
Unfortunately, without a PAN, opening an account is impossible as it's a regulatory requirement. Perhaps open a family member's account who …
Hi @mastertrader21,
If you log in to Pi or NEST then your existing session will be cleared. I would recommend using Kite for monitoring purposes. If you log out of Kite then you are logged out everywhere.
Hi @harjee,
We will add new Quote APIs and make a release soon. There are some new fields being added to responses, we will announce changelog also soon.
Hi @jvimal8080,
If an order-modify request is successful then it means the order-modify request is placed successfully. After that, there will be some RMS checks after which order is modified. If RMS checks fail then order won't be updated. You can …
Hi @abhash2610,
You need to exit cover order.
You can check out the example for bracket order exit here. You need to pass same params to exit cover order.
Hi @phneoix,
This forum is dedicated only for Kite Connect related queries, please send a mail to support(at)zerodha.com for other platform related queries.
Hi @jvimal8080,
When you are placing a bracket order, stop-loss and target are not placed at the limit price you have entered instead it will be placed according to the price at which order got executed.
The Same scenario has happened for both of th…
Hi,
In developers console, you need to specify a postback URL to which Kite will make a post request when an order is executed and your endpoint will have to accept the data coming in.
In simple words, it is like a notification sent to the client to…
Hi @jvimal8080,
It looks like the case of self-trade wherein you are buyer and seller.
If your stop-loss and target are not far away then after taking the position if there is no buyer and seller then your order will be the best bid and best offer w…
Hi @shankar1318,
You can use the new version of pykiteconnect. It supports continuous chart data feature.
@manyamrajesh,
Please open one new thread for an issue, it will help others.
Hi @Purushottam,
161930244 - TCS6 of BSE is not being traded today.
216486661 - INBM17SEP105.00PE of BFO, currently we don't support BFO.
14779394 - AXISBANK17OCT720CE of NFO is not being traded today.
12227074 - TATASTEEL17SEP770CE of NFO is not a …
Hi @suyashb,
Kite Connect serves historical data based on instrument tokens. Check out documentation and you will get instrument token from instrument dump.
Instrument token for Nifty 50 is 256265.
Hi @abhishekr21,
The getOrder(order_id) method returns different states of an order in the System.
Check out example response in documentation https://kite.trade/docs/connect/v1/#retrieving-an-individual-order
Hi @Encrypted,
I don't think you should be doing.
If you send more than 3 seconds server will not respond.
It will keep returning "too many requests" HTTP status code 429.
Hi @c00kie,
Kite Connect is by default for a personal use. I am afraid we can't provide this.
As an alternate, you can post to the postback URL from your end itself, whenever session hook is invoked you can make an API call to that URL.
Hi @hardik__,
It means your session is expired and you need to re-login.
If you are getting this every time you are running the App then it might be because you are requesting for access token every time you run the App.
Request token can be used o…
Hi @RA5800,
After placing a cover order, you will get an order_id which will be same as parent_order_id of second leg SELL order(SL-M).
When an order is executed Kite will send you a postback.
You can check out documentation for postbacks here.
Hi @hardik__,
Sandbox is not yet available. It will be included in phase 2 of new APIs.
If you place orders now, it will hit the live market. You can wait till market closes and then continue your testing.
Hi @Encrypted,
This is quote call which will give you a market snapshot. It has nothing to do with Historical data.
For 200 instruments, you will have to create your own candles using Websockets API.
Hi @puneetbijnor4020,
Since there is no limit on how much stop-loss value one can place an order with. The maximum value one can give for stop-loss = LTP - lower_circuit_value
Margin requirement varies based stop-loss value you give.
@prakash.jj,
Yes, you might be losing many ticks on highly liquid scrips. Do all your operations on another thread and not on the main thread.
Make sure your main thread is always available for receiving ticks.
Hi @traderx,
If the minimum value is 1 then the frequency of modifying an order for all the clients will be less which will significantly reduce the load on our servers.
Hi @hardik__,
The statement is wrong.
If the last trade has happened on at 10042.3 then it doesn't mean the next best bid will be lesser than the LTP or next best offer is greater than LTP. It can be anywhere based on what is the price at which next…
Hi @avinashsringeri,
Can you name an example scrip for which you are getting the error?
We will check and update. Please do post the from and to date also.
Hi @thepanoramix,
We will include it in bulk quote call which will be provided in future.
@arsh_makker,
It seems to be working fine.
You need to send params like this,
i=NFO:NIFTY17SEP10000CE
Please post these questions on a new thread so that it w…
@thepanoramix, @manyamrajesh, @avinashsringeri,
Is this still happening?
Can you give us more details with params? We are trying to reproduce the issue.
Hi @puneetbijnor4020,
The SL-M trigger price is set based on the price it was executed and not the according to the limit price given by the user. Hence there can be a different trigger_price if a bracket order executes in multiple trades.
For cove…
@prakash.jj,
Are you doing this on a single thread?
If you are doing all of this on one thread then it is very likely that you might be blocking incoming ticks.
Hi @Abhishek Gupta,
It seems like pykiteconnect still doesn't support continuous charts feature. We will include it in next version.
For now, a feasible solution would be to reimplement kite.historical() method at your end and add continuous = 1 as …
Hi @Abhishek Gupta,
We don't have minute level data for expired contracts, you can get day's data.
You can call like this,
kite.historical(12865538, "2017-04-01", "2017-09-08", "day",1)
Hi @puneetbijnor4020,
Appologies for late response.
Let us consider a scenario if CO trigger range for an instrument is 4.5%, you are placing a BUY order, LTP of the scrip is 100, the best bid is 99 and best offer is 101.
1. Parent leg is bought @…
Hi @sandeepmaganti,
On the mock trading day, we don't provide ticks. Today morning we had a server maintenance which wiped off cached values. Hence you won't get prices on websockets.
As an alternate, you can use new APIs mentioned here.
Hi @vaga,
Instruments tokens are reused by exchange once it is expired.
If you are looking for historical data for expired contracts then you can use continuous historical data feature.
Check out documentation here.
You just need to pass continuous …
Let's consider a scenario wherein you place a LIMIT order for an instrument for 1000 quantity, if for the same price offer is there for 500 quantity then 500 will be executed and for rest quantity, it will be cancelled.
Hi @chiragkeswani,
You can go to developers console and subscribe for historical data.
You can get previous day's OHLC.
You can check out documentation here.
