Order update from the Websocket API can be considered as an event to fetch orderbook and check the latest order status and filled quanity.
For order placement, you need to add a couple of seconds delay and check the orderbook, order update is not se…
Yes, all the order place requests are considered. It includes the one that may show up in the orderbook with status complete, pending, rejected, cancelled, trigger_pending and also orders that don't show up in the orderbook but rejected by our mini …
You can use it for personal use. One can't use it for building a product for mass. For more information you can write to kiteconnect(at)zerodha.com and speak to the compliance team.
You need to go inside the app details screen and click on renew button or create a new Kite Connect app.
Adding credits to developer account will not automatically renew the app.
It seems like you have connected Zerodha account to your developer console account. Money gets debited from your Zerodha account and the debit instruction will show up in the trading ledger by tomorrow EOD.
It is available for the current month, next month and far month instruments.
Can you share the complete stack trace by enabling debug logs of pykiteconnect?
It doesn't matter if it goes in to success or fail block. Can you enable the debug logs of kiteconnectjs and paste the complete stack trace here?
You can enable debug logs as mentioned here while creating the constructor.
Can you run kiteconnectjs in debug mode and share the complete stack trace here?
PS: Make sure to remove app and client specific tokens while pasting here.
One can't test postbacks using local. You need to give a valid https url for Kite Trade to make a request to your endpoint.
You may use postb.in like service to try it out.
@rajatgupta431,
If this is a product developed for mass then you can speak to compliance team by writing to kiteconnect(at)zerodh.com with product description. You may ask for multi-user access.
Kite Ticker broadcasts tick to all subscribed clients at once. It doesn't matter from the Kite Ticker's perspective.
As long as you are using the same access token and within the rate limits it is fine.
@tradernoob,
We just relay the tick that is received from the exchange. We don't throttle ticks. We get Level 2 data from the exchange an we send the same to the users. You can check out Nithin's reply on this thread to know more about how ticks str…
Kite Connect app is provided only for personal use. It can't be used with multiple client ids. You will have to use the same client as mentioned while creating the Kite Connect app. If you are not sure what client id you have given then go to dev co…
You can place two limit orders with validity IOC(immediate or cancel). You can use Kite web or app to know the features offered on Kite for better clarification.
Once an order is sent to the exchange it becomes regular order. The fetch orders API will give you variety as amo because of a legacy issue on the OMS. But you will have to cancel with variety as regular.
The logic we use on our front end apps is
…
@arunkumarr,
Please spend 10 minutes and read the documentation, all these are the covered there and few that are missed are present in the FAQs.
Websocket API gives day OHLC values. You need to generate candles at your end for live market strategie…
You may get one or you may get 3000 which is the maximum number of tokens allowed for subscription. You can read more about Websocket API behavior on FAQs.
Please note, if there is no counter order for the orders placed in pre-open, it will be unexecuted in pre-open and the order will execute in the normal market if the criteria are met.
You may also refer to the NSE website here.
A holding in you DEMAT will not have any exchange associated with it. I would suggest not to deactivate BSE segment.
You can read more about this behavior here.
There will always be one trade that happens in pre-open. Till 9:07 AM there will be order collection and at 09:08 AM there will be one trade at equilibrium price. That is how pre open market works.
You may refer the example here.
Correct way to resolve the error is to print and paste the complete request and response. There are many combinations for order place API.
Websocket API data is a snapshot data and not tick by tick data. While the volume data is cumulative, LTQ will just give information about the last transaction.
You will need a very high bandwidth and colocation servers at exchange to get tick by ti…
The historical data API is provided for backtesting purposes only. We suggest creating candles at your end for live market strategies. You may refer to this thread to know more about generating candle data.
Postbacks are only sent for the orders that originate from your app. You may use order updates via Websocket to get order updates of all the platforms.
This is because websocket connection is closed. There can be many reasons for this. You need to check the firewall rules, antivirus, VPN or switch to different ISP and try.
I would say let it fetch multiple times. It is far better than having stale data after aggressive optimizations to cache data. Scheduling positions fetch at fixed interval may also lead to more unnecessary fetches.
@arunkumarr,
The historical data API is provided only for backtesting purposes. It is not an alternative for screener or scanners. You may use Tijori for screener data.
Realised param in the positions API is a legacy field. You can use this formula,
pnl = (sellValue - buyValue) + (netQuantity * lastPrice * multiplier);
GetInstruments doesn't do authentication. You can ignore first API call working.
Maybe don't do Base64 encoding while fetching historical data.
PS: Do you have add-on historical data subscription?
@hrp,
I am afraid that is not possible and there is no cache data like that. You can generate candles at your end using the live market data. You may check out this thread to know more.
Kite Connect API doesn't retry placing orders. It could be the okhttp library doing the retry. I would suggest sending GUID for each order to avoid this.
You can check out the login flow documentation here.
You may also check out this thread to know more about the request token and access token handling.
You can refer to the example here.
PS: Please don't post app or client specific tokens on public threads. You may private message, if you have to share any of the tokens.
It is not a re-use of token issue. It is how the Kite Ticker works. Kite Ticker sends a last stored cached tick first time when user subscribes for a token. Post that a tick is sent only when there is a change in any of the values.
We handle the exchange token reuse and you get the OI of the current instrument under that instrument token. If they want historical for expired instruments then you may use continuous mode.
