Hi @Shaha,
Is this happening from yesterday or you had faced it earlier?
Can you let us know if there is some kind of pattern?
We have asked OMS team to look into this.
The data constructed using both the sources are correct. It is just they won't exactly match because of the above-mentioned reason, it will be near.
In order to get accurate data, you need to have colo setup at exchange which might cost around 18 la…
The source for our historical data is different from Kite Ticker. The candles generated at your end will never exactly match the candles of Historical data. It will be near but not the exact match.
Check out this thread for more information.
Hi,
The historical data is provided for backtesting purpose only. It is not meant for live market. You will have to generate candles at your end for live market strategies.
I am not sure, it is not a fixed delay. It can happen because of anything. If one write slows then the delay can multiply. But it will be a few seconds away. You can try and use it if it is feasible but I would suggest generating candles at your end…
Hi @ankur0101,
Historical data is not meant for live market conditions. It is provided for backtesting only.
Our systems read all the ticks and generate a candle at the end of the minute and write to the database. It happens for all the instruments …
@cisk,
Are you trying to use Kite Ticker for order updates?
Can you paste the URL you are trying to connect?
PS: You need to be connected in order to receive order updates. If you open websocket connection after placing the order, it more likely th…
Hi,
The source for getQuote() and getLTP() is Kite Ticker and Kite web also uses Kite Ticker to fetch the last price. Both platforms fetch data from the same source. It can't be different. Can you give us some more details and steps to reproduce? If…
Hi Suarabh,
I tried and it seems to be working fine from our end.
I would suggest using new quote call. It provides all the data that is provided in this API call.
Hi,
Square off and Stop-loss values are given as points and not exact values on Kite Connect.
If you give indefinite points then square off value will sit at upper circuit value. You can check out more information about this here.
You can get it from positions API. You check out documentation https://kite.trade/docs/connect/v1/#portfolio
You can take a look at python documentation here https://kite.trade/docs/pykiteconnect/#kiteconnect.KiteConnect.positions
This is the new Kite Connect 3 on which we are working from past one year. We haven't officially announced it yet. There breaking changes. Hence all the clients will be given some grace period to switch.
We will announce once we complete our chang…
You can check out examples here
https://github.com/zerodhatech/javakiteconnect/blob/kite3/sample/src/Examples.java
You can take a look at ticker usage method. Use javakiteconnect 3 for Android.
@Shaha,
We have Kite Ticker 3 API as a parallel setup till everyone migrates. You need to connect to the different endpoint to use it as of now. It is already included in new version of client libraries. You can take a look at it in kite3 branch of …
@cisk,
We are doing some final changes, so pykiteconnect repository must have been updated multiple time in this week. You need to clone kite3 branch for latest changes. You don't have to subscribe to order updates explicitly. It is sent as a text m…
Hi,
It is included in Kite Connect 3. In the new version of javakiteconnect, you can fetch data for multiple instruments from the getQuote method.
You can check out new version of javakiteconnect here.
@cisk,
We are working on documentation for Kite Connect 3. Which Kite Connect client are you using?
Timestamp for ticks is already available in new Kite Ticker API. For now, we have kept it in another endpoint till everyone upgrades to the new vers…
@aakashps1995,
Don't call the requestAccessToken method every time you run the app.
Once you get access token, store it and re-use it for subsequent runs.
The get order API will return a list of statuses that an order has gone through in the system after the user has placed an order.
The status complete will be in the last item of the list.
Hi,
We only provide OHLCV data in historical data as mentioned here. Our historical data doesn't contain average traded price, change and open interest.
You can get all these in live market data. You can dump it at your end and use it.
The instrument token can change. The instrument token can be assigned to some other contract once a contract expires. We use a combination of exchange and tradingsymbol like NSE:INFY.
You can use bulk fetch APIs. Check out example here.
As of now market depth is not included in bulk fetch APIs. It is added to new quote call of Kite Connect version 3.
Yes, it is a bug from OMS end because of which instrument token is returning the wrong value. We are following up with them to get a fix. This is observed only in AMOs only.
You can use either tradingsymbol with exchange or instrument token as the …
@jitendra,
yes, you can get it in the new version of Kite Connect. What Kite Connect client are you using?
@cisk,
You can get data for a particular instrument for a particular time interval as well. You can check out this thread.
Hi,
All the API calls are authenticated using access_token. Right now, we use public token only in Kite ticker(websockets). We are soon going to migrate to access token authentication for that as well.
The real use-case for public token would be fo…
Hi,
Generally, mock trading will be on 1st Saturday of every month. This week we didn't participate in mock trading.
You don't need to connect to separate endpoints. You can use the regular endpoints.
For MCX, mock trading will go on till 14:00 and…
Hi,
When a corporate action happens, instrument token may change or may not change.
We don't have mappings for old and new instrument tokens.
Yes, a position will be adjusted automatically.
You need to use instrument token for receiving ticks, you seem to be using exchange token.
The correct instrument token for COALINDIA BSE is 136519172.
This issue was resolved at that time only. It won't cause API to throw invalid API error though. The behavior would be getting cached value(same value).
