@shailesh,
Are you sure you didn't call generate access token again?
Websockets API only authenticates while connecting and not while sending every tick. So it is possible that your session has expired and you are still getting ticks.
@Akshay15,
Please don't post app or user specific keys on the public threads. It can be easily misused.
As mentioned above, you need a historical add-on subscription to use the same.
PS: We have regenerated your api secret, please use the new one.
Hi @kapilaggr,
There are multiple hops in the system. It is not a single server doing everything. There are multiple hops(layers) of the complex systems in place which are used when a user places an order. An order can move from one hop to another i…
Hi @pawan,
You need to send a valid tradingsymbol which can be found in the instrument master dump which is published by the exchange while placing an order.
The order quantity has to be in multiples of the lot size which can be found in the instrum…
One can't place a target and stoploss for a cover order.
I would suggest checking out these threads to know more about the cover order and bracket order.
If you place a cover order, the system will take care of placing the second leg order. You don't have to explicitly place another order.
The order place response will give you an order id which is the parent order id of the second leg order. You ne…
We don't have a sandbox environment.
The data you receive from the websocket is binary data. You can read more about the packet structure here.
I would suggest using one of the client libraries instead of reinventing the same thing.
Hi @vina,
I would like to repeat our stance on this again as mentioned earlier. We provide historical data for backtesting purposes only. We don't recommend using the same for live strategies.
If your strategy requires intra-day candles then you ca…
You get error messages in the text format. You need to listen to text messages to know the error.
You might be sending a wrong subscribe message to the Kite Ticker.
You can receive up to 1 tick per second for an instrument generally and maybe in case of highly liquid instruments you might receive 2 ticks per second sometimes.
We merge data of multiple instruments in a single tick binary data. So the number of b…
I don't think you can do the authenticity check. A user could have gotten shares from ESOP, corporate action, IPO, transfer-in wherein the user enters a dummy order id.
Your platform has to be built in such a way that it always considers the user ha…
You need to pass a valid instrument token or exchange:tradingsymbol. You can get it from the instrument master dump. You can check out the documentation here.
This is because you seem to be sending an invalid tradingsymbol and invalid quantity. You can get details from the instrument master dump.
You can refer to the documentation here.
You can place an order at the opening. Since we also fire tens of thousands of AMOs at the opening, there can be a few seconds delay.
We just relay ticks whatever we get from the exchange. I don't think there is any lag in the live market data.
You…
I am not sure what you are referring to. It is not a specific issue to go fix it. It can happen because of many reasons, it could be the client's connection with Kite trade, Kite trade's cloud connection to OMS data center or OMS overload, or OMS in…
That is an older version of the Kite Connect APIs. There are new fields like day_buy_price and buy_price to denote each day's activity for a position.
You can refer to the example response here.
@akhileshKhajuria,
Order history is an API that shows all the states of the order that it has gone through in our system, the OMS and the exchange.
It is available only for the current day. A user can't fetch it post BOD.
You can know more about ord…
Kite Connect APIs didn't receive a response from the OMS vendor when you placed an order. Hence it throws an exception.
When a read request times out, you can just directly retry but in case of a write request time out, the system doesn't really kn…
Can you paste your complete code here and paste the complete stacktrace?
Make sure you run it in debug mode.
PS: Remove your auth header before posting stacktrace here.
@rajesh_shig,
This is because Postbacks were really developed for partner platforms like smallcase wherein they need postbacks for the orders that they have placed and not for every order that was placed on Kite.
If you are an individual user then …
@babansfolio,
It can happen when Kite trade doesn't receive a response from the OMS. In such cases, you need to catch the exception and check orderbook before you retry placing the order.
Kite Connect is not meant for HFT.
You need to be colocated at the exchange to get a better results for HFT.
It would cost you around 18 lakhs per annum. We can help you with that. You can write to [email protected] for further assistance.
Streak is an independent platform. It has nothing to do with the Kite Connect subscription.
It is like an alternative to Kite Connect for users who are not familiar with coding.
@adjas,
I think this is more to do with the OS, in some cases we had observed that upon reconnection, the system was using the old connection itself. In your case, it looks like it is using a new connection.
Can you paste the complete code here and mention your setup details?
It seems like you are using an explicit variable to check if it is connected or not. Kite Ticker already exposes a method to do that. You can know more here.
The pykiteconnect takes care of the re-subscription of all the tokens upon a reconnection. End-user app doesn't have to do anything for that, it even keeps track of mode it is subscribed to.
You can receive live market data for all the instruments. You need to get all the required instrument tokens from the instrument master dump and fetch market data for all those.
You can get started here.
Hi @vSeelin,
There are two fields included in the Kite Connect API. One is exchange_timestamp which denotes the exchange entry time and exchange_update_time which shows the update time as well.
At the time of the javakiteconnect release, there was o…
@Guhan,
All the tick data are received in the binary format whereas order updates are received as a text message. Hence on_ticks callback is used to read ticks and on_order_update is for listening to order updates and on_message is for listening to …
@DD3516,
You can check out the documentation for historical data and Websocket data.
Please don't hijack threads, create a new thread for a new query, it might help someone who is looking for the same. You may also use the search feature.
@write2onkar,
There is no issue with the code. It is the access token that seems wrong. Since api_key, you have specified is right in the above comment.
PS: Please don't post your app or user-related keys on public threads. If you have to do then I…
From version 3.0, you need to send access token and not a public token for connecting to WebSockets.
PS: Please create a new thread for new queries, it might help others who are looking for the same.
