It looks like there aren't any issues with the 1-minute data for RELIANCE. Could you please share the specific data that you believe is different or incorrect? That way, I can assist you more effectively.
1. If you haven't already logged in using the Kite `login` MCP tool, please use the link shared in the chat by the AI assistant to log in first."
2. If you're already logged in and are currently using the Claude AI assistant, you may try switching t…
@james505 @vks1974 @adipkite It looks like Claude has made a change on their end, breaking the integration. We’re working on fixing this. Meanwhile, you can use Kite MCP via VS Code alternatively.
It looks like Claude has made a change on their end, breaking the integration. We’re working on fixing this. Meanwhile, you can use Kite MCP via VS Code alternatively.
The GIFT Nifty Index operates in two trading sessions: the first from 6:30 a.m. to 3:40 p.m., and the second from 4:35 p.m. to 2:45 a.m. the following day, as per IST.
The Quote API provides live market data at the time of the request, provided the…
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 Personal app (free version). This issue typically arises when the credentials from the Personal app a…
Once a tick is lost and not stored, it cannot be retrieved later through the Kite Connect API. However, you may consider exploring exchange-approved data vendors who provide access to historical tick data.
To calculate the average price of an Iceberg order, you need to filter all its associated orders using the parent_order_id parameter. By calculating the average price of these individual slices linked to a specific parent_order_id, you can determine…
Go to the app details and verify whether the redirect URL is updated correctly. If it is updated correctly, you can try this in an incognito window or clear your browser cache and try.
There are certain limitations on retrieving historical data. You can refer to the discussion here for more details and plan your data retrieval accordingly.
If you are holding a long position, the TRANSACTION_TYPE for placing a stop-loss order should be set to the opposite side of your position — i.e., it should be "sell".
You may retrieve the order details and check the filled_quantity/pending_quantity details. Check out the pykiteconnect documentation here.
You may also check out the API documentation here.
