Kite Ticker saves the last tick it received so that it can serve user a cached data whenever user subscribes for a tick. If you check the last traded timestamp, it clearly says the date is 27th of April.
Please note, we just relay ticks that we rec…
Basically fetch orderbook and check before doing a retry. In case you get 4xx error then it might be Input exception, you will have to see what is the error and send appropriate params.
It is possible in any system, right? You need to catch the exception and handle it gracefully. If you get exception while fetching data, you can add a delay and retry but for a write request, you need to introspect and then take the necessary action…
Did you try without assigning custom pool? Difficult to pin point where this issue is arising from. Could be firewall or change cloud provider and check.
While creating an app it clearly mentions that 2000 credits will be used for subscription. User will have to select ok or cancel. Anyways, you can speak to the business team by writing to kiteconnect(at)zerodha.com
Postbacks are only sent for the orders that originates from your api_key, it is not sent for orders that are placed via other platforms or kite web or app. You will need to listen to order updates via Websockets to cover this usecase.
Kite Connect only provides the live market data via websockets API. You will have to calculate the IV and other data.
This library may help you get started.
An access token got using refresh token will not have any write permission. You will have to go through the login process and fetch a new access token to place an order or modify it.
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.
