Every request to place order also is counted. If order_place request is rejected by our mini-RMS then you will see http 400 status code with InputException and it won't show up on orderbook.
Only first tick you receive will be a cached tick. Post that you will only receive ticks when there is a change in any of the params. You can verify instrument token in each item.
You won't receive ticks for all tokens in every on_tick. Kite Ticker only sends info when there is a change in any of the params. You can know more about it on FAQs.
Are you using offsite execution or Kite Publisher js flow? You can know more about offsite execution here.
In recent updates of safari, there is a change in cookie management policy. Cross domain cookie management is blocked in iframe. Hence using o…
I had some queries,
1. It is a generic library which exists for both maven and non maven users. Why remove dependencies?
2. Is Maven compiler plugin 1.7 deprecated ?
3. I am using 1.8 java version without having to change anything. My local is not a…
This is a partial stacktrace, can you share the Kite Connect request and response with header information?
You can private message since it will have app and client specific tokens.
There will be one consolidated position created for an instrument and particular product type. You can see whatever fits your purpose. I would suggest using Kite web once to know the behavior of the platform.
@SAGARRD,
In the earlier versions of javakiteconnect it was working as is (we never intended to build library for mobile apps), hence we had added that line. In recent updates, it might have broken because of Kotlin dependencies. Hence the suggestio…
You will have to write the Kite Connect library first and then work on your project.
PS: If you are developing an app for mass then you need to contact compliance and get a go ahead before starting the project.
A 200 for place order, modify order, and cancel order means the request is placed successfully. It doesn't guarantee the execution. Once you get 200 response, it is better to fetch order history for that order or fetch orderbook to see if the new or…
Hi @ChandrasekarV,
We are glad that you loved our platforms. Thank you for choosing Zerodha for you investments.
The requested feature belongs to our back-office platform console. This forum is dedicated only for Kite Connect related queries. You c…
I don't think issue is with code. For semantic errors, it is better if we have request and response logs.
Can you enable debug logs while initializing Kite Connect?
Can you share the error json and http status code or, it would be better if you can share the entire debug logs. It will make it easier to see all request params and response json. You can enable debug logs while initializing Kite Connect client lib…
Can you enabled debug logs while initializing Kite Connect library and share the complete stack trace?
PS: Make sure to remove app and client specific tokens.
If main subscription expires the historical data becomes inaccessible, you will have to resubscribe to Kite Connect in order to use it. However the historical data subscription will also last for a month independent of base Kite Connect subscription.
We will inform the team to take a look at this, it could be because request is timing out before data is pulled from database. I would suggest, pull the data and dump it at your end and use that as source.
We have always recommended using header based authentication requests. Query params based authentication was allowed for legacy reasons only. You will have to switch to header based authentication.
Your open position and the GTT had same product type? This usually happens when you have MIS position and you placed sell GTT with CNC product type.
To exit a position, you need to place the same quantity order with opposite transaction type. The e…
@SZM059,
We have always mentioned to use authentication on request headers and not on query params. The query param way of authentication was always for legacy reasons. Users were directed to use auth headers from the very beginning.
It seems like you don't have order place permission. You can speak to compliance team by writing to kiteconnect(at)zerodha.com
PS: All third party platforms need to use Kite Publisher to place order.
This forum is dedicated for Kite Connect related queries only. You can write to support, someone from our team will guide you through the new TV chart usage.
You need to put some logs and see, we don't disconnect from our end. You might be blocking the thread or there might be an exception in secondary thread that isn't logged.
@akshay_thakker,
There was an issue with the developers console. Hence we have refunded the amount debited. You can pay again and subscribe for the Kite Connect app.
