@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.
Order update is not pushed when order is placed on Kite app but it will be pushed only when there is a partial fill or the trigger is hit or order is modified.
This is the formula and everything is available in the API. Latest LTP is available on Quote API or Websocket API.
pnl = (sellValue - buyValue) + (netQuantity * lastPrice * multiplier);
@ashishbajaj,
You won't receive postbacks if order is not originated from your app. You will have to create a websocket and listen to order updates on that. You may use that order update as an event to fetch orderbook and check order status or do an…
@MayurVirkar,
You can read the support article that is pointed out there and create a support ticket if you want more explanation. Kite Connect forum is dedicated only for technical queries only.
@sathyatej,
Kite Connect is purely an execution platform. We don't provide one to one support or coding support.
We are all developers like you, we work on our projects and take some time out to help community members. Kite Ticker doesn't have any i…
An order id and tag will never change once created in the system. Only new trade entries will be there for that order. For partial fills, you can check filled_quantity field.
Kite Ticker doesn't have any issue. It is used by thousands of production apps. You need to check code at your end. Add logs and also make sure to enable Kite Connect debug logs as well.
Every instance of KiteException has a message attribute like this.
Can you print the same in the catch block and paste the message here? If you are placing order then it could be the exception from the http API as well.
