A third party app can't show our data on their website. You can speak to the compliance team and check.
You may reach out to them on kiteconnect(at)zerodha.com
It is the name of the third party app that our users are logging into. That is how it is intended to work.
Users must know that they are not logging into Kite web. They are logging in to the third party app.
Kite Connect offers only placing order for one instrument. You will have to create a list or queue at your end and use that as the source for placing order.
You can speak to compliance team before starting the project with product description to check if you can get approval for the product from exchange. You can reach out to them on kiteconnect(at)zerodha.com
A 500Mbps should be fine. At max 1000 instruments in full mode will be 184kbps, given all the instruments are highly volatile.
Again it depends on your implementation as well. If you are making other HTTP API calls also in parallel then you may need…
Multi user support is provided only for a product that is built for mass and has to go through compliance team and exchange approval process if required. You can speak to the compliance team in detail. You can reach out to them on kiteconnect(at)zer…
You won't receive postback for an order that is triggered from GTT. You will have to rely on order updates on Websocket API for this. You can use order update as the event to fetch orderbook and check the latest status and filled quantity.
The OHLC in the Websocket API is the day OHLC. You can refer to the documentation here.
For intraday OHLC candles, you need to generate candles at your end using the same API. You can refer to this thread to know more about it.
For backtesting, you …
You will not receive a response like HTTP API call. You need to set callback on_connect and then call connect. You can refer to the Websocket API usage here.
we use LTP to decide direction of breach of target/sl for single leg and two leg. By the time GTT is created at the backend, LTP might have changed. Hence a correct LTP is required while placing GTT.
We don't have ASP.Net example. You can refer to the sample python example here.
It is just a simple server which accepts form POST requests which will be called from Kite Trade.
You may test postbacks using postb.in
Generally, the series won't change from EQ to T2T segment or vice versa during market hours. It will change in the next trading session.
If there is an issue with exchange published file then only it will change series during market hours. But it is…
You need to specify the correct order variety. Minimum legs for an iceberg order is 2. You will get 400 (Input exception) error if you send iceberg order with iceberg_legs=1.
A regular order will not consider iceberg params.
You don't need to poll orderbook. You can listen to order updates on Websocket API and use that as an event to fetch orderbook and check the latest status of the order.
Kite Connect doesn't have a separate API for freeze quantity. You need to place an order and in the 400 error response you will see the freeze quantity number.
We will try to improve this experience in the future. For now, this is the only way to c…
Kite Publisher has issues with new version of chrome and safari because of the new cookie management policy in iframe. It may not work in all cases. You can use offsite order execution.
For fetching holdings of a user, you need a Kite Connect app and that API call is a http request it has nothing to do with offsite order execution.
We don't have any work around for the cross domain cookie management in an iframe.
It is because of the recent cookie management policy change on chrome and safari.
You can use offsite order execution.
This is the possible way because you will open a new tab.
It is because of the recent safari's new cookie management policy inside the iframe or popup.
You may try your luck with offsite basket execution, but not sure if it works or not.
Yes, the callback is invoked but we suggest using that as an event to fetch the orderbook and check the latest status and filled_quantity to handle all the edge cases.
Though you get current day's data on historical data add-on subscription. For live market strategies, we suggest building candles at your end with the live market data provided on the Websocket API.
You can know more about generating candles here.
The acceptable tag length has been updated to 20 characters. You can refer to the documentation.
For now, '@' is whitelisted for some technical reasons. We suggest using only alpha-numeric values only for tag as it might be stopped any day.
The jav…
You can refer to the FAQs to know about the usage of Kite Connect APIs and javakiteconnect examples here.
Kite Connect is purely an execution platform. We don't provide support or solutions to write strategies.
@techcoze04,
We have included all the required fields in the funds POJO of javakiteconnect. You may refer to this thread once, if something is missing. We can include in the next update of javakiteconnect.
It is a method from where all the HTTP requests originate. It has nothing to do with Kite Connect.
You can either check your firewall settings or antivirus or it could be because of network itself. Maybe try on some other network.
Are you closing the websocket and connecting again or are you doing unsubscribe and subscribe again?
Do check out the tick frequency in the FAQs thread to know more about the Kite Ticker behavior.
The total number of orders per day is an account level limit. But the number of order place requests per minute and other API rate limits are Kite Connect app level restrictions. Thus one can create more than one Kite Connect app to place orders sim…
It depends on the market, if there is a match then it will be executed immediately or your order will sit in the pending state until there is another match.
We don't have an API for that. You can however check the google sheet that is used by our RMS team to push the updates. You can refer to the Utilities section here.
We just redirect to the URL provided by the end user. If that endpoint is throwing timeout then you need to debug at the endpoint which receives the redirect.
The order limit will only consider the order place request only and not modify or cancel or place GTT API calls.
It includes the requests made from all the platforms. It is the Zerodha account level limit.
Kite Connect doesn't offer one to one support. There are no support agents here. We are all developers like you who work on our projects and take out some time to help fellow community members.