Hi,
Can you let us know more details like browser, OS details about it?
We couldn't reproduce this at our end. Is this consistent or intermittent?
Can you also give screenshot or steps to reproduce?
Yes, @SRIJAN is right. The timestamp field gets updated whenever there is a change on that order record like partial fill or modification. But the exchange time will show exchange entry time.
The instrument token for equity changes very rarely. For example when it is moved from EQ category to Trade to Trade category. Hence it is advised to update the instruments list at your end every trading day.
I am afraid we can't provide an API for that. It is just a reading the tradingsymbol and construct the formatted name using the expiry and segment details.
@cskasm,
You can check out this thread.
Kite Connect doesn't have any relation to colocation server setup at the exchange. Zerodha can help you setup lease lines.
It costs upwards 18 lakhs/annum. You can write to kiteconnect(at)zerodha.com, if you…
@pat11,
You can use Kite Ticker with reconnect option on pykiteconnect. You can know more here.
pykiteconnect will handle reconnection for you and manage subscriptions after reconnection.
You will have to place a market order with the same params as position but with opposite transaction type.
If you have two orders of same product type then it will show up as one entry in positions.
It may change whenever they are moved to T2T segment. It won't change regularly but it may. So best solution is to download instruments file every day and use the instrument token from there.
If you are asking for making it primary on db then i woul…
It looks like you are not send a valid instrument token.
You can check out the pykiteconnect documentation, it looks like your order of params is wrong.
This is because of the new iframes cookie management policy change on the chrome. Our team is looking into the alternatives to the currently implementation.
Kite Connect only provides the trading platform features as of now. The reporting feature is a part of backoffice i.e. console app in Zerodha's context. You can check out console for that.
We don't provide holdings breakdown on Kite Connect APIs as…
For API related stuff you can read the official Kite Connect API docs here.
For pykiteconnect syntax you can check out the client library documentation.
We just redirect to the endpoint specified in the developers console. The request token will be part of the url and not really in the data.
It will be a query param on that endpoint, if you are doing some redirect then make sure you pass on the quer…
We don't have API for Kill Switch. You can kill session and pause the app.
Please note that pausing the app on developers console will not pause the subscription.
@onlineRaman,
We don't have any timeline for this feature as of now. It won't be backward compatible, since orders are deleted everyday and we don't store orderbook data.
You will need to cross check if you are using the right api_key and using the Kite Connect app's api_key and not a Publisher api_key.
Also, let us which API call is throwing the above error for that specific client? order placement?
For all price related info, you will have to divide it by divisor.
For CDS the value is 10000000, for BCD it is 10000 and for other segments it is 100
We use divisor here. I think this requires a client library update. We will inform the team to u…
The historical data API is provided only for backtesting purposes. We don't recommend using it for live market strategies.
For live market strategies, we suggest you to build candles at your end. You can get started here.
You seem to have entered a wrong api_key. You can check developers console to know the correct api_key.
PS: Please don't post app specific or client specific tokens on public thread. If you have to share tokens then use private message feature on t…
A third party website can't show Kite Connect data. You can write to compliance on kiteconnect(at)zerodha.com and explain the product you are building and then check if you can use Kite Connect data.
Getting a class name is not hack.
The Kite Connect API is written in a generic way, the whole point of client libraries is to avoid using these raw values and consume API in the style of the language.
The javakiteconnect is an open source repositor…
We can see 22 positions on your account. Can you elaborate the issue? Are you still able to see only 15 on positions.net list?
Do you have any filter applied?
@durghy_trades,
As per the exchange regulations, it mandatory that a user has to login manually at least once a day. We don't recommend automating login.
@sureshganta06,
Order updates are not pushed for AMOs and it is only sent when there is an update on the order like when there is partial fill, modification, completed. Order updates are not sent when an order is placed.
@arjunender,
A third party website can't display our market data and candle data. You can speak to compliance at kiteconnect(at)zerodha.com for more information.
This is because of the restriction on cookie handling inside iframe on the newer version of chrome client or webviews.
We are working on an alternate solution for this.
It is up to you, you can try with few milliseconds and if it works our for you then it is ok. There is no definite timeline that OMS has given us after which order history will show up. There are a lot of states involved and lot of systems. It may w…
You can add a couple of seconds delay and then try fetching the order history.
Order goes through a lot of systems before reaching the exchange, it takes a while for a record to be created at the OMS.
We only update the corporate actions that affect holdings here. Only extra-ordinary dividends affect holdings Hence only those are included in that sheet.
1)As I given to understand cover order can be modified and cancelled until the given position(buy/long or sell/short) is not executed and pending.
You can modify order but there is a cap, an order can be only modified up to 25 times. Once this limit…
You can will receive order updates for all the orders not only API orders on Websockets API.
On postback API, notification is pushed for the orders that are placed on API only.
@itsrahularora1990,
You will have to contact some exchange registered data vendor. A third party app can't show the market data provided by Kite Connect.
@neerleo88,
We have always informed, the historical data API is provided for backtesting purposes only. We recommend you to generate candles at your end using Websocket API data.
@whity,
Sooner or later every broker and every platform will enforce TOTP, there are already indications internally (among regulators and other stakeholders) as mentioned above.
You will have to store access token in a shared preference or external file and use that value while initializing object.
Make sure not to call generate session in every run then your issue will be resolved.
@devendrarathore,
Every request POST and PUT made to the orders endpoint is counted and the orders rejected by our mini RMS won't show up in the orderbook but you will see 400 error response with a message.
Kite Ticker caches the last received tick data from the exchange. Post market, there are ticks sent with empty depth data. Hence it serves the empty depth to the users. You can try it in market hours.
@zhkas,
As stated in multiple queries or FAQs, we officially recommend you to use only 3 Websocket connections per api_key. For some legacy reasons, it might be working as of now but it can be changed soon without intimation. If you want to open mor…
Kite Connect doesn't support bracket orders, you can use Kite Publisher if you want to just place regular order.
You can know more here. For rest of the functionality like knowing the status of the order, funds, positions, holdings you will need to …
Thank you very much. This made our day We use different things for different projects.
Generic icons are used from feather icons. This forum's avatar is from vanillicon.
The icons and illustrations on the coin app is hand-made by our designer. E…
One can't increase the rate limits. You will have to subscribe for another Kite Connect app and use that for fetching more frequent data.
If you want to create the candle data at your end then you can get started here for which you don't need to cre…
The historical data API doesn't support bulk fetch. The correct usage guideline is to fetch and dump the data at your end and use that as the source.
If you are looking for live market data then we suggest you to generate candles at your end using t…
Can you elaborate which library version you are using and the complete code and stacktrace?
You had ask the same query here couple of days back in another thread. From your previous error trace-back, you don't seem to be using official Kite Connec…
