Websocket order update are asynchronous messages pushed by the OMS, order of the event or duplicate events are triggered in the few cases. Hence, we suggest fetching orderbook on order update event.
I am afraid we can't do this. There are thousands of platforms that use Kite Connect APIs, every platform doesn't need to know the activity of the client that is happening outside of their platform. It becomes a case of security lapse.
I just tried and it seems like it is not redirecting to your redirect url since it is an exception. You will be redirected to kite.zerodha.com and url will have a session id.
Kite trade will place order for the account for which access token belongs to. Anyways, a Kite Connect app is enabled only for one Zerodha account. It can't be used for another account.
@nickel12,
You can write to compliance team asking for multi user access with your product description. They will decide and get back to you. It is usually provided for an exchange approved platform which is built to cater mass.
It is mandatory by the exchange that a user has to login manually everyday at least once.
Hence access tokens are flushed everyday and users are required to create a new session.
@Prav,
I would suggest write to compliance and seek advise before building any kind of platform for mass.
You can reach out to the compliance team on kiteconnect(at)zerodha.com and make sure to include the complete description of the product you are…
Hi,
Though coin flow looks fine now. Many underlying process, code and dependencies are changing. Lot of actors involved in mutual fund processing are changing. Underlying process is still in chaos. We won't be able to provide this feature yet.
It could be because of the redirect url. You might have set the kite url. You can change that.
Only one user is allowed for a Kite Connect app. You need to create multiple apps to use it with multiple clients.
Every app is charged Rs2000.
Postback is not sent when an order is placed. It is sent only when there is a partial fill or there is a status change like TRIGGER PENDING to OPEN or COMPLETE.
For all the APIs you need a valid access token to access data. It is same for HTTP calls and Websocket API.
You can know more about it by reading the API documentation.
The postback status for an order that is filled partially or a status change from TRIGGER_PENDING to OPEN will have the status as UPDATE. These asynchronous events are pushed by OMS, there are some scenarios wherein OMS sends multiple postbacks for…
Kite Ticker publishes whatever data is published by the exchange. We don't modify or process anything so whatever you see is what exchange is publishing.
You need to include exchange and tradingsymbol. You can check out documentation here for LTP API. You can find the correct tradingsymbol and exchange for all instruments in the instruments master dump.
The instruments master dump is a huge file whic…
Kite Connect app is provided for personal use only. It can be only used with the client ID that is mentioned on the developers console while creating the Kite Connect app. Go through the FAQs here.
These are async events sent from the OMS. We haven't done any changes at our end. The recommended way is to use this as a event to pull orderbook and check the latest status and pending quantity.
We don't provide support for programming. Kite Connect is purely an execution platform. We don't provide support or help for writing or developing strategies.
Kite Connect APIs are provided only for personal use. It can't be shared with other users. You will need a separate subscription to use with other family members account.
1. Historical Order Data - while you can fetch it daily and save at our end, next day reconciliation isn't possible. This is something I consider very important - and shouldn't be a hard implement.
Kite Connect only has trading capabilities. This in…
@monikanareshkumar,
The historical data provided by Kite Connect are for backtesting purposes only. You need to generate candles at your end using the live market data provided on the Websockets API.
You can get started here.
Close price of the day is updated post settlement session and we update the same from the BHAV copy late in the evening when exchange publishes the file.
You can refer to this example, the only difference will be exchange, that is NFO. The tradingsymbol anyways you can get it form the instruments master dump.
This requires a change in DB level, the team has informed they will do it over the weekend. You may follow up on Friday evening once.
For now, you can use url shortener.
The question of creating a state in the Order history doesn't even occur since the request is rejected at the Kite Trade level only and you will see 400 response from Kite Connect instead of 200
If order is already executed, you will receive a 400 Input exception when you make a modification request.
You will have to send quantity field only while modifying the order's quantity. You can know more here.
Close price in the day candle is the settlement price published by the exchange after 6:00 PM. Hence it won't match the day candle close that is generated by the intraday data.
There can be hundreds of ticks per second at the exchange but only 1 or …
