We have asked the team to take a look at this. But it might take more time to fix. There are tens of thousands of AMOs fired at that time and traffic is very high at the market open. We suggest placing order after a few seconds.
The instruments master file doesn't require authorization header but a Quote API call does require.
You may enable debug logs for pykiteconnect and check the request and response json. As error message suggests, you might be sending wrong api_key or…
You will get postback for every partial fill as well, but we suggest you to use postback as an event and fetch orderbook and check filled quantity for latest status on the orderbook.
There are few edge cases wherein OMS sends multiple postbacks, on…
For order placement, the variety co must be used and product will be MIS. The product CO is only present in the orderbook. Since it is not prominently used, you can ignore CO product as it may lead to more confusionf for new users.
For all intraday…
Instrument token is derived from the exchange token and the segment. But you never know since exchange only keeps reusing token and two different exchanges might be using same exchange token. It is not guaranteed to be unique.
I think that is very difficult to solve because on the client machine it is disconnected. I think it is better to check why it is getting disconnected in the first place. One shouldn't block the thread that is receiving ticks.
If you have taken care…
Are you sure you are disconnecting properly? It could be because you have not closed the connection at your end but server has an active state at its end and hence you are getting too many requests.
Add on subscription will be active but you will only be able to use it if you have base subscription. If you subscribe for Kite Connect, you can use historical data API till 28th June 2024.
Pi is not available anymore. You will have to use Kite Connect APIs for everything. If you are developing a product for mass then we suggest speaking to compliance team by writing to kiteconnect(at)zerodha.com
You shouldn't block the main thread that is receiving ticks. If you block the thread that is receiving ticks then you may miss the data. We subscribe to 100 of ticks at a time on our apps, we haven't encountered this issue.
A pop up is shown for confirmation that a debit of 2k will be posted in the account while subscribing for Kite Connect app. Users are expected to type "I understand" and not just a button click.
If you have deleted app by mistake, you can write to …
The charting backend uses a different ticker source. It won't match 100%. The idea is to capture the trend or get a colocation setup at the exchange and use tick by tick data.
I don't think you should compare other charts. The idea is to capture the trend. The live market data on Websocket API is only a snapshot data. It is not a tick by tick data. There can be hundreds of ticks every second at the exchange but exchange s…
What you get from live market data is not tick by tick data, it is just a snapshot data. There can be hundreds of ticks in a second at the exchange, only one or two are streamed via internet. You can know more here.
So you could get 2 consecutive t…
You can go through this thread to know more about how to convert ticks to candle.
There is no adjustment, you just need first, last tick of the minute, high and low of the minute to form the candle.
The Postback json is same but the usecase is different. You will get order updates for all the orders in the Websocket API whereas on postback API you will receive update only for the orders that are placed from your Kite Connect app.
You need to create a developers console account and subscribe to Kite Connect. Kite Connect app is provided for personal use only. You can create two apps what use different Zerodha client id.
It can be funded using any of the accounts you wish to …
Kite Connect only provides live market data, you need to calculate the indicators at your end.
You can know more about the Websocket API here.
For instrument token, you need to fetch the instruments master every day morning and store it at your end.
Kite Connect doesn't offer Delta value. You can check out Websocket API documentation to see what are the data points available on Websocket API(live market feeds).
Can you enable debug logs which contains complete request and response json and private message the complete stacktrace? We will check and get back to you.
You need to print the exception.message and see what is the exact error message. Maybe if you can share the client library debug logs, we can investigate further.
For order related issues, it better to keep the debug level logs of pykiteconnect or any other client library logs which contains request and response json and report it on the same day for investigation.
The order history gets wiped out after BOD.…
We don't see any disconnections or error logs at our end.
PS: There are 10k+ Kite Connect production apps and even our internal apps use the Websocket APIs which is used by 46 lakh+ users during market. If there is an issue with Kite Ticker then i…
Are you using the same product type as the existing position? Can you private message the order id for which you have this issue, it is better if you have logs of current day. The order history gets erased after BOD.
Can you private message the api_key and complete stacktrace after enabling debug logs of pykiteconnect which shows complete request and response? We will check and get back to you.
It is because the day candles will have a time as 00:00:00 and any request for after that time is considered. Hence you are getting the next day candle.
You can check out the example here.
I think your system timezone is not IST. Either you can set it to IST or you need to set the timezone to IST after creating the date object.
We don't provide any support or solution for writing strategies. There are documentation and examples for all the APIs and the client libraries. You can refer to the same.
It is mandatory by the exchange that a user has to login manually at least once a day.
A refresh_token is provided only for the platforms that are built for mass and not for individual users.
You need to fetch the instruments data once a day and store it. Use it for the whole day since it will generally not change.
For more information about the search you can go through this thread.
