Hi,
You need to use Websockets to fetch live market data. phpkiteconnect doesn't support websockets. You need to use kiteconnectjs to fetch live market data.
You can check out more about websockets here and equivalent javascript documentation here.
Hi @raoulnair,
Though the feature is available. We don't recommend using historical data API for live market strategies. The historical data API is provided for backtesting purpose only.
For live strategies, we suggest generating candles at your end…
You shouldn't be storing request token in the app. It can be used only once and its validity is for a couple of minutes. Instead, you should store access token.
You don't have to generate session for every run. Check out more details here.
Historical data is an add-on subscription which will cost you Rs 2000 per month. Once you have an active subscription you can access that data.
The only restriction is 3 request per second.
We will look into this.
Please don't post personal info or session tokens on the public threads. You can write a private message if you have to mention those.
To modify a second leg cover order you need to send second leg order id in the URL route and parent_order_id in the body.
curl --request PUT https://api.kite.trade/orders/co/Second_Leg_Order_ID\
-H "X-Kite-Version: 3" \
-H "Authorization: token api_…
You will receive a csv file response for this endpoint. This is an endpoint for downloading instrument dump file.
The above line is clearly an HTTP API call, it has nothing to do with websockets.
@naz,
I have asked the concerned team for the explanation. I will let you know about the update.
We don't append tick timestamp, it is the timestamp which we get from the exchange.
A user has to authorize (for the first time only) for sharing data with third-party apps.
It seems to be working fine. Can you private message the user id with which you are getting the error?
@prakash_kite,
Thanks for the insight. We appreciate you taking time to post here.
@pandithurai,
It can happen when you pass instrument tokens as a string.
Yes, you can get today's data also in the Historical data API. The historical data API is provided only for backtesting purposes. For live strategies, we recommend generating candles at your end using the live market data provided via websockets API…
You can expect to get a list at the opening of the day and think that it will be allowed for trading in MIS whole day.
It is updated during the day also. We will look into this.
pykiteconnect supports reconnect feature. You can check out here.
But the real fix would be finding why is it disconnecting. Are you sure you are not blocking the main thread while you are processing the ticks?
We don't have a predefined list which is allowed delivery trades and intraday trades. RMS does these changes during the day because there was an exchange circular, there is high liquidity, circuit limits, and many more reasons.
This is more like an…
There is no subscription logic for getting order updates via websockets. In fact, there is no logic for order updates in any of the kite Connect clients. The only code written in Kite Connect clients is parsing order update messages.
Are you sure y…
All Kite Connect apps are by default a single user app. You can't use it for multiple users.
If you have a platform which is for mass then you can email talk(at)rainmatter.com for multi-user access with the description of your platform.
If the above…
Since you can't send a date object as request param in an URL. The API expects a client to send the date in this format.
In order to do basic validation of input data, javakiteconnect expects users to send a date object.
Make sure you are not passing numbers as a string like a price, trigger price, square off etc and send tradingsymbol, exchange, order type etc as strings.
