Please don't paste app or client-specific details on the public threads, it can be misused. If you ever need to share session or client-specific details then use the private message feature on the forum.
You seem to have created an app for masses, y…
this means your session is expired, you need to log in.
If it is the first time login then you may need to grant permission for the app.
Can you let us know what is the browser version you are using? and paste a screenshot here of the error.
A success for order place API means the order is placed successfully, it doesn't mean the order is executed.
Once you get a success response you need to fetch orderbook and check the status and status message of that order.
@gkaranam,
Are you sure you are checking for the right segment?
It looks like the segment is disabled for your account.
You can check on the Kite web funds page once and contact support.
You can go to the app details page on the developers console and find an option to subscribe for add-on service like historical data there (on the right side of the page).
For cover and bracket orders, there is already a pending child order, the system just has to modify that to a market order.
For an end-user to exit co or bo, one has to send an exit order request, this can be done by sending a cancel order request w…
Hi @devarajh,
We can see that there was a time out at 2020-10-12 12:04, you need to receive and respond to the request. Are you doing any processing in that thread itself?
Since your system didn't respond in time, it was considered a timeout.
Kite Connect app is provided only for personal use. Are you sure you are trying to access the APIs with the same client id provided while creating the Kite Connect app?
Due to the power outage in Mumbai, we had connectivity issues with one of our leased lines to the exchange. Some of the orders placed during this time are affected.
Kite Connect doesn't offer support. This is a community-driven forum for helping fellow Kite Connect community developers. We are all developers who hang out here to help and also work on our projects.
Asking a generic query won't help you get an a…
The quote API does provide OI data but you need to send each and every instrument token you need data for or send the exchange:tradingsymbol data.
You can check out the documentation to know more.
Due to the power outage in Mumbai, we had connectivity issues with one of our leased lines to the exchange. Some of the orders placed during the affected time might be showing the status as open pending.
Due to the power outage in Mumbai, we had connectivity issues with one of our leased lines to the exchange. Some of the orders placed during this time are affected.
@sbdavra,
We don't have an API to check the number of connections open at the Kite Ticker.
I will forward your query to the concerned team and check if they can do something about it.
@prakash.jj we have always recommended users to use a maximum of 3 websocket connections per api_key.
We didn't have a hard limit till now for legacy reasons, we are going the put the hard limit now. If you need to open more websocket connections th…
@livekrish,
We only have data in this format. You can check out webocket documentation and historical data documentation.
If you are looking for live market data candles then we suggest generating candles at your end using the websocket data.
@Bhavninder, You need to use one websocket connection unless you are subscribing for more than 4k instruments.
Edit: Current limit is 3k, the new limit is 4k
@Bhavninder,
I am afraid you can't use our Websocket data to display live market data on a third party website. You may need to check with compliance first. You can write to kiteconnect(at)zerodha.com to reach out to the compliance team.
@sbdavra,
We don't see any issue from our end. Even I tested it multiple times. Anyways we have asked the team to revert it for now. We will take it live again soon.
@all
Please make sure you don't exceed a maximum of 3 websocket connections per api…
@sbdavra, @sunny,
The change mentioned here was taken live yesterday.
We had given the deadline way before 8th October 2020. We have always told people to keep the maximum simultaneous connections up to 3.
@rahulbhayana,
We don't provide one-to-one…
This happens when some required field is missing while modifying an order. Can you run javakiteconnect in debug mode and give the request and response logs when this happens?
This is a message from the OMS. Can you private message the client id and order id for which this happened?
We will check and get back to you.
This could be because you modified order more than 25 times.
We have provided the curl examples and the response structures in the documentation.
For type strict languages, we have provided a detailed explanation in the client library documentation itself.
You can check out the javadoc here.
It seems like you are doing processing upon receiving the postback. You just receive the data, return the response, and then do your logic.
We see a lot of timeouts because your system didn't respond.
The target order is limit and the stoploss order is SL, but you may also need to note that once the trigger is hit the stop-loss order also becomes LIMIT type. In that case, you need to look at the price and decide.
The OHLC API gives you the day's OHLC but the candle data will give you OHLC for the minute or any other specified interval. Can you let us know what are you looking for?
