You can buy credits and use it create and subscribe for a Kite Connect app. You will need a Zerodha client id to trade or fetch data and hence it is mandatory to enter client id for subscribing to Kite Connect.
A third party app can't display the data from Kite Connect APIs. You will have to speak to compliance team. You can write to them on kiteconnect(at)zerodha.com with product details.
While we strive everyday to make all the transactions happen smoothly. API errors can occur because of various reasons. It is not a single machine you are connected to. It is a complex network which connects clients, CDN, multiple cloud setup, multi…
You need to enable debug logs and give complete stacktrace. It is not possible for anyone to help without having complete context.
PS: Make sure to remove app and client specific tokens.
It is not working because of the new cookie policy by safari which blocks cross domain cookie management in the iframe. You will have to try out offsite order execution.
The historical data API is provided only for backtesting purposes only. It is not meant for live market strategies.
Since the candle is generated for all 93k+ instruments at our end. We can't guarantee any time line when candle will be generated, si…
We don't have Sandbox environment yet. You will have to subscribe for Kite Connect to do this.
It will require you to connect to websockets API and check price for every incoming tick and take action or continue.
You need use instruments token to subscribe for tick data. The instrument token is present in the instruments master that updates once a day in the morning.
You can check out documentation here.
@SurbhiS,
You can use Websockets API, you will have to connect and subscribe for tick data. You can find the instrument token from the instruments master and subscribe using that.
You will only need the base Kite Connect subscription for this.
Whe…
It is not about the bandwidth, it is more because of hops unavailability or if you are polling then cloudflare might block you. It is difficult to conclude it is issue in our server or vendor systems or CDN or issue at user ISP.
I would suggest add …
It can happen because of many factors since everything is happening via internet, difficult to pin point. You may try handling it or play around with firewall, switch network/cloud provider.
Kite doesn't support this feature.
This forum is only dedicated for Kite Connect related queries. You may write to support for other platform related queries.
It is mandatory by exchange that a user has to manually login at least once a day.
A `refresh_token` is a special long-standing token for read-only requests issued selectively to exchange approved platforms and not for individual users.
We don't provide one to one support for Kite Connect. You can post your queries here, we will help you out.
You can create a session and do whatever you want.
One can modify order quantity, if it is not executed.
Brokerage charges are per order and not per trade. Brokerage will be calculated for one order that is 1000 qty.
Every request is counted and not the number of parameters one changes and one can m…
You don't need to poll orderbook every 10 seconds. You can use order updates on Websockets API and use that as an event for fetching orderbook. You get order update for partial fill, status change, order execution.
The instruments master file is generated at the beginning of the day around 7:30 to 8:00 AM. It will not contain last price. You will have to use Websocket API or Quote API.
You can try moving logging also if you are subscribing to multiple instruments. Check your firewall settings which may be closing a long standing connections and sometimes it could be ISP also, you may try alternate network as well.
Postbacks are sent only when there is a partial fill, or trigger is hit or when order gets executed. If you are placing a limit order postbacks are not sent until there is a partial fill or order is executed.
Can you elaborate for which API you got this error? What is the Kite Connect library version you are using?
Maybe enable the debug logs and see if you are sending all the valid params.
All the restrictions on Kite web and mobile app applies to APIs as well. You can try placing order on one of our platforms and check.
You may also refer to this support article.
You can run with debug logs enabled and check if it is 400 or 403. If it is 400 then you are not sending access token, if you it is 403 then your session is expired and you need to re-login.
The historical data API is for backtesting purpose only. We suggest generating candles using the live market data via Websockets API. You can get started here.
Can you remove onNewTicks and just keep logging for the day? Try on an alternate network also wherein you only log tick received and not do anything else.
Kite Ticker is being used on our internal apps and 1000s of production Kite Connect apps, we d…
You can refer to the date format here. It is 24 hour format. Also, make sure you are sending dates as DateTime objects, not as strings. Here is an example code.
Can you elaborate what is the issue and for which instrument? We just stream data that is published by exchange, we don't do any processing on the data.
pykiteconnect comes with reconnect support. You don't have to do anything, library itself takes care of reconnection and re-subscribes after reconnect. You can check out documentation to know how to enable it.
The ones that you pointed out were placed from Kite web according to the logs. Kite web orders will not have tags. You can let us know next time when the order which is placed from pykiteconnect, we will check and get back to you.
We checked a couple orders and that seems to have been placed on Kite web. Are you sure you sending tags for all orders? Can you give an example order for which tag is not updated?
