You can will receive order updates for all the orders not only API orders on Websockets API.
On postback API, notification is pushed for the orders that are placed on API only.
@itsrahularora1990,
You will have to contact some exchange registered data vendor. A third party app can't show the market data provided by Kite Connect.
@neerleo88,
We have always informed, the historical data API is provided for backtesting purposes only. We recommend you to generate candles at your end using Websocket API data.
@whity,
Sooner or later every broker and every platform will enforce TOTP, there are already indications internally (among regulators and other stakeholders) as mentioned above.
You will have to store access token in a shared preference or external file and use that value while initializing object.
Make sure not to call generate session in every run then your issue will be resolved.
@devendrarathore,
Every request POST and PUT made to the orders endpoint is counted and the orders rejected by our mini RMS won't show up in the orderbook but you will see 400 error response with a message.
Kite Ticker caches the last received tick data from the exchange. Post market, there are ticks sent with empty depth data. Hence it serves the empty depth to the users. You can try it in market hours.
@zhkas,
As stated in multiple queries or FAQs, we officially recommend you to use only 3 Websocket connections per api_key. For some legacy reasons, it might be working as of now but it can be changed soon without intimation. If you want to open mor…
Kite Connect doesn't support bracket orders, you can use Kite Publisher if you want to just place regular order.
You can know more here. For rest of the functionality like knowing the status of the order, funds, positions, holdings you will need to …
Thank you very much. This made our day We use different things for different projects.
Generic icons are used from feather icons. This forum's avatar is from vanillicon.
The icons and illustrations on the coin app is hand-made by our designer. E…
One can't increase the rate limits. You will have to subscribe for another Kite Connect app and use that for fetching more frequent data.
If you want to create the candle data at your end then you can get started here for which you don't need to cre…
The historical data API doesn't support bulk fetch. The correct usage guideline is to fetch and dump the data at your end and use that as the source.
If you are looking for live market data then we suggest you to generate candles at your end using t…
Can you elaborate which library version you are using and the complete code and stacktrace?
You had ask the same query here couple of days back in another thread. From your previous error trace-back, you don't seem to be using official Kite Connec…
Kite Connect API is the base subscription. In order to fetch candle data you will have to subscribe for historical data API. For live strategies you can generate candles using Weboscket API data which is part of Kite Connect API.
You need to use the tradingsymbol that is mentioned in the current day's instruments dump.
It is moved to T2T segment so the tradingsymbol is FCSSOFT-BE
The historical data API is provided for backtesting purposes only. For live market strategies, you need to generate candles at your end using the websocket API data. You can get started from here.
I was not using WebSocket when I got this error, I was using plain API calls in a loop.
'Connection aborted.', OSError(107, 'Transport endpoint is not connected'
The above error is because of the socket or thread connection dropdown. Are you sure ab…
You can use postback or order update as the event to fetch orderbook and check the latest status of the order or filled quantity to check the partial fill.
Are you blocking the main thread that is receiving the ticks?
You shouldn't block the main thread. You can use on_order_update callback and use that as an event to fetch orderbook. Again make sure you don't block thread while fetching orderbook
It …
It is still one single order. Kite Connect will not split orders.
You can cancel an order at any point in time.
You can check the outstanding net quantity by fetching the positions API.
A 7 seconds for completing a get API call is too much. I would suggest trying it on a different ISP. It is very unlikely that Kite Connect takes that much time, you can probably do a trace route at that time and post the details here.
One can't fetch historical data for an instrument that is not present in the instruments master today.
You can contact some exchange registered data vendor.
@Ramji,
We don't see any issue from our end. All the requests are completed within a second for me. Can you try on an alternate network?
If your strategy can't afford to account for a couple of seconds delay then you need to go for colo setup at th…
@Kamalv,
Kite Connect just places order with the quantity provided by the user. It doesn't split order if quantity is high.
You can place order for the quantity up to freeze quantity.
If you receive error then you will have to place order with lower…
@Gjain75,
Kite Connect only supports the bonds that are traded on the exchanges. NSE and BSE in particular.
Bonds of CCIL are not traded on the exchange.
PS: Please create a new thread for new queries, this answer gets hidden and others looking for…
@genesis,
You can use postbacks or order updates on websocket API as an event to fetch orderbook and not poll.
We don't have any API to check the number of order requests a user has made in a day.
If you are blocked then you have exceeded the limit…
A third party app or website can't embed Kite web app. You can contact any exchange registered data vendor for historical data and use some charting library.
For triggered ideally you should get postback or order update but the current version of GTT doesn't have that feature. In the next version of GTT we will include this.
If the last thursday is a trading holiday then it will be prepone to last Wednesday. If Wednesday is also off then expiry will be prepone to tuesday.
This is the practice but there is no written document or circular about this.
AFAIK for few illiquid scrips it is exchange modifying the market order to limit. You can know more here.
But I have asked team to check what happened in the above SL-M case.
These are async messages pushed from OMS. We have reported it multiple times to the team. For now, I would suggest using order update as an event to fetch the orderbook and check the latest changes on the order.
@rubaljhavar,
Others are also facing the same issue? I just tried on chrome latest version and it seems fine for me.
Just trying to gather more information to debug this issue.
