Kite Connect offers much more with just Rs 2000.
> Kite Connect APIs are simple, robust and reliable.
> The Rs 2000 for Kite Connect charges include GST.
> Kite Connect API's historical dataset is bigger than any other offering.
> Kite C…
Instruments segments are obsolete, it was used in margins data API. You can use the new margins calculation API.
Kite Connect API supports CDS and BCD exchange for currency instruments. You can check all the values in the instruments master file.
CN…
It is mandatory by the regulators that a user has to login manually at least once a day. We don't recommend automating login. We don't recommend sharing credentials with any third party.
It was a legacy decision. Back in v1 of Kite Connect APIs, buy value and sell value wasn't there. It was calculated in the front end. Now that API is sending those values, it makes sense to change it to quantity.
We will change it in next release.
If order is blocked by our mini-RMS then you will see a 400 error but when it reaches OMS and it is rejected by the RMS then you will see order entry in the orderbook.
You will need a Kite Connect app to check the order status. One can only trigger place order for Kite Publisher.
If you already have Kite Connect and you are using the api_key for Publisher as well then you can get status update from Postbacks.
A change value is calculated in Indian market as the change between last price and previous day's close price that is streamed via ticker. In European markets it is the difference between last price and open price of the day.
There are some edge cas…
For Indices there won't be few fields, hence we set the bool tradable as false so that it can be used to check between tradable and non-tradable instruments.
You can refer to all the constants here.
We suggest using the order_update via Websockets API or postback as an event to fetch orderbook and check the latest status and filled_quantity to know the latest update about the order. There are multiple e…
Can you enable debug logs for pykiteconnect and paste the complete stack trace?
PS: Make sure to remove client and app specific tokens before sharing the logs.
The GetInstruments returns you a very large file. You need to fetch it and cache it at your end for the day. It gets updated everyday morning after 7:30 AM so it is better to download post that.
You can enable debug logs as mentioned here and share the complete stacktrace to investigate.
PS: Make sure to remove app and client specific tokens before sharing stacktrace.
There are hundreds of users using Websocket API and creating candles at their end. You need to write the code and keep doing trials and optimize code till you get the desired result.
You can check out this thread.
There is nothing called right or wrong data. The idea is to capture the trend. If you need accurate tick by tick data you need to be at the exchange in a colocation server which costs 20+ lakhs per annum.
The volume data on live market stream is a cumulative value. You will need to subtract the last tick and first tick volume to get current minute's volume.
For the first query, can you private message the client id? We will check and get back to you.
For the second query, an order_place success means the order place request has gone through successfully from Kite trade to OMS, it doesn't guarantee any…
The historical data API is provided only for backtesting purposes. You can use live market data from websockets to build the candle data. You can get started here.
@hrp,
The historical data API is provided only for backtesting purposes. You can use live market data from websockets to build the candle data. You can get started here.
@benny,
Our data team is working on the timeout issues.
There is no workaround for this. Browsers are blocking cross domain cookie management. The solution itself will be to open new tab or window for every Publisher request. For now, we suggest users to use offsite basket execution flow, we may do that …
Can you mention for which API call you are getting this? Is this consistent or intermittent? Can you let us know the steps to reproduce and share the complete stack trace with debug logs on?
Each Kite Connect app can only create only 3 Websocket connections. Maybe you are exceeding that. You can check out FAQs to know more about the rate limits.
PS: Kite Connect is purely an execution platform. We don't provide support or solution for …
Even in live market order update is pushed whenever there is state change or partial fill only. You won't receive order update for just placing an order.
Hi @HowUTrade ,
The API sends lesser fields for each of initial, final attributes. In normal mode, there are 13 props and in compact mode they have 5 props. Thank you for pointing it out. We will update the documentation.
You can private message me the client id. We will ask the RMS team to increase the limit for today but if this repeats then they may flag your account and freeze order placement.
Every request to place order also is counted. If order_place request is rejected by our mini-RMS then you will see http 400 status code with InputException and it won't show up on orderbook.
Only first tick you receive will be a cached tick. Post that you will only receive ticks when there is a change in any of the params. You can verify instrument token in each item.
You won't receive ticks for all tokens in every on_tick. Kite Ticker only sends info when there is a change in any of the params. You can know more about it on FAQs.
