We have verified on our end and found no issues in receiving the data, including OI, through the WebSocket. For the previous day’s OI, you may retrieve it using the Historical API.
We have verified on our end and are able to fetch historical data for NFO scrips (active contracts) successfully, as well as historical and live data for BSE instruments, which are working as expected.
You may try enabling debug mode to help ident…
When generating the request token, the redirect URL registered in the developer console for your API key will be used. For more details, please refer to the API documentation.
We have verified on our end and are able to fetch live Quote data successfully using the above method. If you are still encountering this issue, please enable debug logs and share the complete stack trace with us via DM so that we can investigate it…
We have verified this on our end and are able to fetch volume and OI through WebSocket. You can enable debug mode to help identify and resolve the issue. Volume represents Volume traded today at that moment and OI represents Open Interest recorded d…
Order updates will not be received through WebSocket for personal apps (API). You may use postback/webhooks instead. For more details, please refer to the documentation.
We have verified this on our end and are able to fetch YATRA details via WebSocket. We recommend enabling debug mode to help identify and resolve the issue. For more help on establishing a WebSocket connection, please refer to the WebSocket API docu…
A connectivity error may occur across all endpoints. The error displays when you try to reuse a connection at the moment the server closes it due to inactivity or a local session timeout. You can retry the request after a brief delay of a few millis…
We have verified that we are able to fetch the total buy and total sell attributes. The above response does not appear to be from our official API WebSocket.
You can refer to the updated API documentation for details. To calculate the total quantity in your portfolio, you need to combine the quantity field, t_1 quantity field, and MTF quantity field.
You will need to calculate the Delta value programmatically, as the Kite Connect API does not provide Greeks directly. You can refer to the option chain data and Python library .
GTT orders do not support the tag parameter directly. However, for regular orders, the tag field is useful for sending an arbitrary string to help track the order. In the case of GTT orders, you can use the returned trigger_id — which is provided u…
The instrument token appears to be incorrect. You can retrieve the correct instrument details by using the getInstruments() function, which provides a CSV dump of all available instruments.
For more information, you can refer to the Kite Connect do…
These scrips fall under the BE category. To fetch them, please append 'BE' to the scrip name. You may also refer to the instrument file for the latest list of scrips.
You can manually add the last_price while placing a GTT order; however, it is recommended to use the live LTP/last traded price to ensure accuracy. Hence, the GTT expects the last_price field to be provided in the request.
With the Kite Connect Personal app, it's not possible to access real-time or historical market data.
If you have created multiple apps, please ensure that you're using the API key and access token for the Connect app (paid version), rather than the…
The 20-depth market data is exclusive to the Kite web and mobile platforms due to regulatory restrictions. As of now, this data is not available via API because of restrictions from the exchange. This thread explains more.
