If you are getting non 200 status from API and keep on continuously sending requests, you will get blocked by CDN. You will have to wait for 10 seconds and then retry.
You can send an email to business team with the payment id and date and time details. They will check and get back to you. You can reach out to them on kiteconnect(at)zerodha.com
You can write to the business team and send the payment id with date and time. They will get back to you.
You can reach out to them on kiteconnect(at)zerodha.com
@srkhedkar,
Can you private message the api_key? We will check and get back to you.
Make sure you have entered the client id with correct case and remove all the spaces before and after the client id in the app details page of developers console.
@hrithikgupta,
Kite Connect is provided only for personal use. You need to use it with the client id that was provided while creating the Kite Connect app.
As the error message indicates one can place a stoploss order above last price. If you need to place an orer below last price then you need to use limit order type. You can know more about the stoploss orders here.
@raju_ns,
What type of order is that and what is the transaction type?
Edit: Let us know the order type, product type, instrument name, order type, price/trigger price
You get 429 error code with this message only when you are exceeding the rate limits. Maybe add timestamp and check if you are within the rate limits or not.
It is happening because of the large url length. We have asked the team to fix it. In the meanwhile, the ideal solution is to use instrument token as the params for request to squeeze in more instruments or slice the request.
Yes, it is a rare scenario as mentioned by you. The logic of generating tradingsymbol at your end is flawed. You need to always fetch instruments master file for the day and use that as the source.
Minute canlde data will have the last LTP captured for that minute which will be same for day candle data.
The next day early morning, it will be updated with the BHAV copy close price value published by the exchange late in the evening, which is th…
Can you enable the debug logs and paste the complete stack trace here? We will check and get back to you. Make sure to remove app and client specific data.
Only order collection happens from 09:00 AM to 09:07 AM, and when an equilibrium price is achieved at 09:08 AM, an LTP is published. The behavior on Kite web and Websocket API are same.
Monthly expiry is on 25th October 2024 (SENSEX24OCT80200PE) and the weekly expiry is on 31st October 2024 (SENSEX24O3180200PE)
You need to look at the tradingsymbol format and figure out which one is monthly and weekly expiry.
You can know more abou…
The Kite Connect app is provided only for personal use. It can't be used with any other client id. You need to use the app with the client id that was entered while creating the Kite Connect app.
The historical data API is only meant for backesting purposes only. We suggest generating candles at your end for live market strategies.
You may get started from here.
Can you mention which endpoint you are referring to? How you are searching, example tradingsymbol?
Please note that from November 2024, many of the weekly expiry instruments are being discontinued. You can refer to the bulletin here.
There are few edge cases wherein order updates are received twice. The solution is to use this as an event to fetch orderbook and look for the latest status of the order and filled quantity for partial fill. An UPDATE status could be partial fill or…
You place an order and wait for order updates on Websocket API. If you get disconnected or reconnected then fetch orderbook and check for the latest status of the order.
On order update, you can place OCO GTT for exit and keep modifying the required…
You should never generate symbol at your end. It may go wrong in production. One should always find the tradingsymbol from the instruments master which has all the symbols that are traded for the day.
How often do you fetch balance? Is it after every 10 minutes? At what time did you get the error?
Can you enable debug logs for pykiteconnect and share complete stack trace?
Maybe there was some backend process that was being run. Hence you didn't see the holdings. Both Kite web and API are powered by the same backend. It is not possible that on Kite web it is showing and at the same time on Kite Connect API, it is not …
A close price in a minute candle data is the last tick received in that minute by our system. The close price of the day candle data is usually updated the next day early morning, the value comes from the BHAV copy which is declared by the exchange …
Is this on the day, you took trade or the next trading session? Can you enable debug logs for pykiteconnect and share the complete request and response json?
Make sure to remove client and app specific tokens.
