@ttsdev We have raised this issue with the concerned team. In the meantime, the suggested workaround is to use the postback message as a trigger to fetch the order book and verify the latest details, or alternatively, fetch the order history and ch…
The Market Protection feature has not yet been implemented in the Python library. For the time being, you can use a raw HTTP call to achieve this functionality.
We tried fetching the data using the quote LTP endpoint, and it appears to be working fine. You may try fetching it again from your end. In case of any discrepancies, please share the instrument token so we can verify it from our side.
Please verify whether you are placing the orders using the app’s API key. You will receive notifications only if the orders are placed through that key. You can refer to the API documentation.
You may refer to this forum discussion for more details. Additionally, you can refer to the ChartIQ documentation for information on the ChartIQ Kite chart indicator formulas.
You can enable debug logs in PyKiteConnect and share the complete stack trace with us.
Kite Connect Personal offers free access to your Zerodha account with all the key functionalities of Kite Connect, excluding market data (both real-time and hist…
Currently, there are no direct API endpoints available for placing basket orders. You may refer to this discussion for more details on MTM calculation.
We have verified from our end that the first candle starts at 9:15 AM when using the historical_data() API parameters. Please share a screenshot of the discrepancy.
We have verified this and found that there has been a Corporate Action (dividend) for the scrip. Kite displays the adjusted price, whereas TradingView and NSE show the unadjusted price.
We have verified this on our end, and the Kite data appears to match the data received from the API. Please share the raw data and a screenshot highlighting the discrepancy.
The Instrument Token for F&O change only during expiry and not on a daily basis. However, it is recommended to download the instrument file daily to ensure you have the latest data.
1: TTL orders are applicable only to normal orders and not to GTT orders. The TTL parameter specifies the order validity in minutes. GTT orders are long-standing orders with a default validity of 1 year, which cannot be modified.
2: You can place AT…
You can retrieve historical OI data for active contracts using the Historical candle data endpoint. However, it is not available for expired contracts. Please refer to the API documentation for more details.
We have verified from our end and it appears to be working fine. You can share us the raw API response along with a screenshot of the chart or timeframe where you are observing the discrepancy.
You can get historical data for the active options contract. Go through the documentation here.
PS: Historical data won't be available for the expired option contract.
You can subscribe to up to 3,000 instruments on a single WebSocket connection and receive live quotes for them. API key can have upto 3 websocket connections. For more details, please refer to the API documentation.
In the above instance, you can receive tick data (i.e., live quotes) through WebSocket. Additionally, you can fetch historical data for a 1-minute interval.
The average price fetched through WebSocket reflects the day’s average price. If you wish to calculate the average price for a selected interval using Ticker/WebSocket, you would need to fetch the tick data and compute it at your end. For historical…
VWAP and average price are the same. However, a difference arises when the data is fetched through the quote() API, as this value is provided directly by the exchange. On the other hand, the average price obtained via the ticker is calculated based …
For users of the Kite Connect Personal API (free version), order updates are available through Postback/Webhook. For the Kite Connect API (paid version), order updates can be received via WebSocket. You can refer to documentation.
This issue may be due to invalid token details. You can verify the token details in the instrument file section of the documentation. If the issue persists, kindly enable debug mode and attempt to resolve it accordingly.
The request token is visible in the URL, not on the webpage data. Request you to regenerate the request token. If the issue persists, kindly share a screenshot along with the URL and webpage data for verification.
The attachment shared does not appear to contain debug logs. You can enable debug logs and share the complete stack trace so that we can investigate further.
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…
