Kite Connect can't offer the FTP data services because of the regulatory reasons. You can contact any exchange registered data vendor for this feature.
Kite Connect API only contains trading APIs, it doesn't contain backoffice APIs. The trading platform will only contain order and trade related data for the day.
This is a webpage, I don't think you can use postman for that. You can know more from the API documentation. It is mandatory by the regulators that users have to manually login at least once a day. We don't recommend automating login.
@bhaskarsancheti,
Are you getting this after login or before that?
PS: Please create a new thread for the issues, it may help others who are looking for similar solution. Don't hijack existing threads.
@chpadma,
Are you sure you are using the right api_key and app_secret? Please create a new thread for the issues, it may help others who are looking for similar solution. Don't hijack existing threads.
The tradingsymbol is something that exchange decides and publishes. We have no control over it. The only way to keep our systems up and running is to maintain a static mapping at your end and use it. We also do the same as it is inevitable.
Have you added callTimeout for the interceptor? This looks like some issue with Okhttp library. You can google it and figure out.
It is not Kite Connect exception.
The historical data API is provided for backtesting purposes only. It is not feasible for live market strategies. We recommend generating candles at your end using the Websocket API.
You can get started here.
@kanika,
The instruments master is generated in the morning after BOD process, it will not contain live market data. You need to use Quote or Websocket API to fetch live market data.
We don't have the close price value from BHAV copy like NSE and BSE instruments. Hence whatever is the last price recorded on our platform is considered as close price. We have asked the concerned team to take a look at this.
We don't have a Kite Connect client library for RUST, if you are interested you can create and maintain one. We would be happy to feature your library.
@SJ2994,
Even if you pull positions after a minute it will give you old value. It is better to use Quote API or Websocket API to fetch latest LTP and calculate live m2m.
@RaviR,
The add-on historical data subscription is free but you will still need the base Kite Connect subscription to fetch historical data. Kite Connect provides json data in the response, you can populate it at your end into excel.
You can check o…
@namratasonawane, you will have to enter the new IP on the developers console to get it whitelisted. It is not like internet will go off everyday.
This is not something we are doing, it is a regulatory requirement. Hence all the brokers need to adhe…
@anandtiwari25,
Everything is looks fine, except don't use kite.zerodha.com domain as redirect url. That also results in throwing error as Token is invalid or has expired.
@developer,
This shouldn't be an issue for a platform, you will already have some kind of static address you may use that to get whitelisted on Kite Connect.
The historical data API is provided only for backtesting purposes. We recommend you to generate candle data at your end with live market data provided via Websocket API for live market strategies.
You can get started here.
You need to set debug flag true as mentioned here while initializing the kite object.
Make sure to private message the stacktrace as it will contain app and client specific tokens.
Can you enabled debug logs of pykiteconnect and share the complete stacktrace of that? Please do share on private message. It looks like you are not passing a valid api_key or access_token.
@amitbatra03,
The instruments master only contains what are the instruments that are trading for the day. It won't have information about OTM or ATM or ITM instruments.
Kite Connect sends postbacks only for the orders that originates from the Kite Connect app. It won't send postback for Admin square-off orders. You can use Websocket API to listen to order updates for this use case.
It is a Websocket API (long standing connection), you can connect once and subscribe for the data. It will keep streaming data until you unsubscribe or disconnect. I don't think you can make a REST like HTTP request and discard it on Postman.
Server…
The exchange feeds itself has some discrepancy, it is better to calculate at your end if you are not using our client library. You may refer to this thread to know more.
You can use the same api_key for your code but you can't be logged in on both at the same time.
The Websocket connection is per api_key, so make sure you don't exceed 3 websocket connections at any point in time.
