This is because you are trying to modify an order which is not in open or trigger pending status.
You are trying to modify an order which is already undergoing the process of modification.
A 200 status code for order modification means the request f…
It is uncertain nobody can predict as the ticks are sent via the internet as mentioned on that thread by Nithin.
We use AWS Mumbai, not sure if the hosting location matters in this case.
This is because of the way it works. So when a user requests for 3minute candles, we fetch 1minute candles in the backend and group by 3 to make it 3minutes candle.
So 1:27 will be 3 minutes -> which will have 1:27, 1:28, 1:29
Since the request …
@ravishastry,
The cause could be your network or network connection between client and server or our internal hop connection issue. You can either add delay and fetch it or use Websockets API to fetch live market data.
@prmramit,
Yes, we do provide historical data of live options instruments.
PS: Please create a new thread. Don't hijack other threads as the discussion gets hidden and some other person who is looking for the same will not be visible.
You need to send auth header like this "Authorization:token :"
You need to send text token and then api_key and access_token.
If you have subscribed to historical data today then make sure to create a new access token since permissions are assigne…
@pavvu_kk,
Can you run pykiteconnect with debug logs on and paste the complete stack trace? You can private message the complete stack trace since it will contain your credentials as well.
There is no issue here. If an app is expired or inactive then one can't log in to that app.
Please write to kiteconnect(at)zerodha.com someone from the team will take a look at this.
This could be because of some browser plugin or older version of the browser. You can first try to do a hard refresh if it doesn't work try to update browser or try on some other browser.
If an order is not placed then it would have been rejected from the RMS, you would have got an exception while placing an order like this.
You need to log that and check. We don't have that data.
The correct format of the websocket order update is this
{
"data": {
"placed_by": "XXYYZZA",
"status_message": "Insufficient funds. Required margin is 3530.00 but available margin is 578.22.",
"meta_raw": null,
"exchange_order_id": null,
…
Kite Connect doesn't offer daily frequency for SIP.
PS: If you are developing a Mutual Funds platform for mass then I would suggest writing to compliance before starting the project. You can reach out here kiteconnect(at)zerodha.com
It seems like you have placed more than 12.7k orders, out of which only 43 are valid orders which are actually placed at OMS. The rest of them are not valid order requests which won't show up on orderbook.
You need to avoid doing this, maybe by pla…
@madshastry,
You can check out FAQs to know more about the redirect and postback URL.
If you don't renew your app, then the subscription will be paused. If you have linked Zerodha account for automatic renewals then make sure you go to the billing …
It is a different exception, it is not redundant of UserException. Permission Exception is when you are trying to access some features for which your app doesn't have permission.
We will update the documentation with this.
I can see that you received the order_id back in the order placement response and the order has not yet reached open status yet. How come your strategy thought order is not placed or rejected?
What is the logic to consider that?
Hi @rishiajmera,
One can cancel an order if the status is OPEN or TRIGGER PENDING. This is an error message when the user tries to cancel the order which is not currently in any of the above statuses.
If you are developing a platform for masses then I would suggest checking with compliance before starting the project. You can write to compliance with the description of your project here kiteconnect(at)zerodha.com
@rajdeep74,
The HTTP postbacks are only sent if the order is placed via your app. If an order is placed on Kite then it will not be sent.
On the other hand, websocket order update messages are pushed for all the orders.
It is possible that a request might fail by the time data is fetched. You can add a small delay and fetch it again. You just need to make sure that you don't hit the rate limits.
You can check out the latest updates here.
Due to the increased volatility, bracket orders have been blocked and there have been changes to the margin requirement for bracket orders. We will put it back on the margin calculator once, we start offeri…
For some instruments, it might be there are for some it might not be there. We had populated data from a vendor and had done some cleanup because of a lot of errors. You will have to do some trial and error since it is not a fixed date.
Hi,
If you are planning to develop an app for masses, then, please write to compliance at kiteconnect(at)zerodha.com with a description of the app. It is better to validate with compliance before starting the project.
You need to use multi-threading, don't make any calculations or processing inside on_tick. One should never block the main thread that is receiving ticks.
The only code inside on_tick should be to pass data to other threads and nothing more.
It is an array of different statuses in our system, any order placed by the user will go through the put order request received status. You need to find the entry where the order status is complete and check the param.
I think you are confused about the use-case. Please talk to someone from the compliance regarding this by sending an email to kiteconnect(at)zerodha.com
The first thing you need to make sure while using the Kite Ticker is that you don't do any calculations inside on_tick.
The only job on_tick has to do is offload the task to other threads and nothing more. If you do calculation or processing in that…
Hi @arunbharadwaj2009,
One can't use Kite Connect APIs to show real-time market data on third-party websites. You will have to contact some exchange registered data vendors.
For further compliance-related queries, you can write to kiteconnect(at)zer…
You seem to be sending the same order id for both order_id and parent_order_id param.
You need to send second leg order for order_id and parent_order_id for exiting cover order.
