There is no straightforward way to map positions and orders as of now on Kite Connect. I am not sure if @HowUTrade has come up with a solution for this.
@nikkite15 There are thousands of tick for any given instrument (even more for an instrument as active as Nifty) each second. You could receive any one of these ticks when you fetch data from the trading platform, because we may have recorded differ…
Positions don't have any relation to the orderbook. You will have to check the quantity and place a market order with the appropriate transaction type to exit the position.
If your order reaches exchange then it will have values, if it is blocked at RMS then your order will not have an exchange order id or exchange timestamp.
Hi @bhaskar_nair2,
Thank you for your interest. This forum is dedicated only to Kite Connect related queries. Please write to support for other platform queries.
The exchange value for all FNOs is NFO for NSE future and options instruments. This is our convention. You can find the correct value for the exchange in the instruments master dump. For NSE currency it is CDS.
Kite Connect subscription offers all the features like placing order, fetching orderbook, positions, funds, holdings and much more. The historical data subscription is an add-on on top of the base subscription.
If you are looking for candle data of…
Though we have forwarded your query to the data team. It is important to keep some bullets while working with historical data.
There is nothing called a accurate data. Each platform will create candles using the data that is captured using the live …
One has to specify a redirect URL while creating Kite Publisher app to which Kite trade will redirect post successful login. You seem to have given a wrong redirect URL.
I am not sure what you are referring to. It should be of the same value. I just checked on Kite Connect and we still have the open value as 10797.85 on 28/1/2019 09:25 AM.
If this is not regarding the Kite Connect then please contact support here.
You need to send a valid tradingsymbol. This above tradingsymbol is a human-readable format we convert to just to make it easy for users.
You can find the correct tradingsymbol in the instrument master dump as mentioned here.
The exchange re-uses tokens once an instrument expires hence you won't be able to fetch data using the old instrument token since it would be pointing to some other instrument. This behavior is not consistent but randomly keeps happening often.
In pykiteconnect, on_tick is not called for every heartbeat tick.
Yes, you will receive the tick of the instrument whose LTP has changed and not all the instruments.
The heartbeat ticks are of size 1-byte always.
In pykiteconnect, on_tick is not called for every heartbeat tick.
Yes, you will receive tick of the instrument whose LTP has changed and not all the instruments.
PS: Please don't hijack threads, this thread talks about an issue in Websocket and not…
-Multiple account support - We have 3 accounts with Zerodha, can we trade via any of the 3 accounts after developing our own system? What configuration parameters we need to set for this? Please explain.
You will have to create 3 Kite Connect apps f…
Hi,
-If we build the system via API, how will we do the testing? Will Zerodha provide some testing platform for testing?
You will have to try in the off-market hours or place an order with the account balance 0. But make sure you don't bombard with …
BANKNIFTY20FEB30900CE is a monthly expiry instrument and BANKNIFTY2020630900CE is a weekly expiry instrument.
You can refer to this thread to know more about the weekly tradingsymbol format.
We don't provide fundamental data. Kite Connect is purely an execution platform. I am afraid we can't provide 52 week high low data as of now.
We will forward the feedback to add upper and lower circuit data into the websockets.
As of now, you can …
We offer day candle data for expired instruments. You can check out the documentation for more information.
For intra-day candles, you may have to check with some exchange registered data vendors like TrueData or Global DataFeeds.
In order to persist session inside the webview, you need to enable cache and app storage for the webview.
A webview session and browser session are not shared, so the user has to login again on the browser.
If you send only order id and not parent order id then the system will think you are trying to cancel the order.
One can't cancel an executed order. It looks like you are trying to cancel an executed order.
The above order looks like a parent order…
To exit a bracket order you need to send variety, order id and parent order id. You seem to be passing a wrong variety, the correct variety is bo.
You can check out the Python documentation here and API documentation here.
You might have logged out or logged in somewhere else. Hence that access token would have become invalid.
Ideally, you must be able to use it throughout the day.
Authentication is done only while connecting to websocket and not while sending every tick. Hence even though your session had expired you kept getting ticks. You will have to create a new access token while doing the re-connect.
It seems like path /orders doesn't exist, I got 404 while trying to access however /zerodha exists. You can re-check by just opening it on the browser.
Even we are annoyed by this. We keep getting calls every day. One or the other person on the team gets it.
Hence we decided to do something from our end. You can check this out.
The Z-Connect post I posted above has all the details regarding this as well.
Do check out the How do these tipsters get the contact details? section to know more.
Kite instruments file is a huge csv dump that contains data about all the instruments that are traded for the day. It is recommended to fetch this and cache it locally at your end every day once. The local cache should be the source for all your ins…
A read timeout can happen because of many reasons, there is no deterministic way to fix this. I would suggest using a try-catch and retry for timeouts.
These are the async events pushed by our OMS vendor, we have raised this issue multiple times with them but we haven't got any resolution yet.
I would suggest not to assume the order of events, it would be better to check the status of an order to c…
One can open up to 3 websocket connections per api_key. This may change in the future.
One can subscribe for up to 3000 instruments per websocket connection and hence a total of 9000 instruments per api_key.
If there are duplicate tokens then your c…
Postbacks are sent only when there is a partial fill on the order or an order is modified or order is executed whereas websocket order update pushes are done for open order as well and above-mentioned events.
This is a standard practice like OAuth. Giving out a user's access token in the public URL is not a good practice.
Usually, in a standard auth mechanism, a user would get a public token after authentication which is again used to get a private acces…
