Hi @arsh_makker,
There is a max cap of quantity set by exchange for each derivative order. I think for your order it exceeded.
You can get from equity derivative section of this nse page. I think it keeps changing every month and when there is a cor…
Hi @Saravanakumar,
Our old backoffice response is very slow while doing BOD process because of which requests might timeout. Please retry after some time. All these issues will be gone once our new backoffice is up.
Hi @sunnypatel,
Kite Connect doesn't provide order details in the positions.
In order to find the second leg of the bracket order, you need to find the order with the same product, tradingsymbol and which is not completed, canceled or rejected.
Hi @Abhishek Gupta,
When a user places the order, the system will first receive the request, does RMS check at broker level and then sent to OMS wherein a set of checks happen. After that, it will be placed at the exchange. Status messages correspon…
@Ones,
Make sure you are not logging into any of our platforms Pi or NEST. If you log into these platforms then you will be logged out. For monitoring purpose use Kite. Kite will use the existing session after successful login.
If you log out of Kit…
Hi @amit_aggrawal321,
The code is written in C# version 6. If you are using an older version of visual studio you will need to install extensions to enable C# 6. I would suggest you upgrade your visual studio since this is an outdated version.
Hi @pg1337,
1. If a position was initiated as MIS, but converted to CNC/NRML manually by the user, and kept open at close, what value will the API return ? MIS, or CNC/NRML?
Once a position is converted from MIS to CNC/NRML, it will give you CNC/NRM…
Hi @sachinstlko09,
We don't have PHP example.
You can check out python example here.
It is just an endpoint which will accept post request and expect data in the body.
Hi @karthik_selvaraj,
Since the fix is from TR, we can't give any particular timeline. We will get it resolved ASAP.
For now, the feasible solution will be to give trailing stop-loss as the whole number.
Hi @anupshinde,
It is not error implementation, it is lack of infrastructure. You may capture all the ticks only if you are at exchange co-location. With current infrastructure, it not possible for anyone to broadcast hundreds of ticks per second ov…
Hi @sachinstlko09,
Yes, instrument tokens are unique id which is provided by Zerodha.
Historical API requires an add-on subscription. Have you subscribed for the same?
Hi @rajtk,
You can check out all Kite Connect related exceptions.
MSG_FAILURE is something that we get from OMS, Can you let us know the scenario or today's example? We will check and get back to you.
Hi @haribabu, @Ones,
All HTTP requests are limited to 3 requests per second. It's not actually an error, it's just system flagging status code 429 ''too many requests".
Hi,
This is because old backoffice will take a longer time to respond while backend process is going on. The request might be timed out.
Can you try today and let us know?
Hi @suyashb,
We were doing some maintenance work yesterday. Hence sessions were cleared multiple times. You can try it today and let us know if you are facing the issue.
Hi,
With each Kite Connect. You can subscribe for up to 200 instruments with one connection.
Each app can simultaneously open a maximum of 3 websocket connections.
As an alternative, you can check out https://screener.smallcase.com/welcome
Hi @rondlasuman,
There is no multiple order placement API.
Error management becomes difficult.
Any client would expect feedback for each oder placed.
You need run it in for loop and execute each order.
Hi @varaprasady,
You need to write a loop and place market order of opposite transaction type and the same product type for regular orders.
For bracket and cover order, you need to do something like this.
Hi @hardik__,
In case of multi-leg orders like cover and bracket orders, second leg orders will have a parent order id field which refers to first leg order's id.
@Abhishek Gupta,
If you come across this scenario let us know on the same day. We will check and get back to you.
Order status logs are available only on the same day.
Hi @Thamarai,
Websockets API provides live market data. You need to store all the ticks and based on that you need to generate your own candles.
Websockets API is included in the base subscription. You can check out documentation here.
Hi @ramatius,
We don't stream positions data over websockets. We use the same APIs what Kite Connect users are offered.
P&L displayed is being calculated based on incoming ticks.
Websockets is a bad idea because in some cases the client will nev…
Hi @suyashb,
This is the following example what I am looking at,
{
status: "success",
data: {
candles: [
[
"2015-09-30T00:00:00+0530",
140.3,
144.1,
137.1,
141.05,
…
Hi @hardik__,
The request token is valid for one time and expires in a couple of minutes.
Once you get access token store it in preference and use it. Don't request for access token every time you run the app.
The access token is valid for one whole…
Hi @techietrader,
Every Kite Connect API calls are gracefully handled and passed to the client. We won't be able to help you without the error message.
The above error doesn't belong to pykiteconnect.
Hi @AntonyPrakash,
From the above logs, it seems like your order is not executed and you are trying to fetch the average price.
Since you are trying to fetch the average price for an order that is not even partially executed you are facing the issue…
Hi @techietrader,
Can you elaborate what is the error message?
Please brief a little bit about the scenario so that we can investigate what is happening.
Hi @AntonyPrakash,
Kite also uses the same endpoint to populate data. If it is displaying on Kite then it is available on Kite Connect.
Price field in API is the price entered by the user. To check average price check out "average_price" field.
Hi @Prem,
You can check out minute candles data which will give you cumulative volume.
To get volume traded in a minute,
consider t1 and t2 as two 1minute candles with volume,
volume of the minute = t2(v) - t1(v).
Hi @krtrader,
While reactivating the app postback URL validation is failing for your app.
Make sure your postback setup is up and working fine.
The error message is "The postback URL could not be reached. Please make sure the port is 80 or 443".
Hi @pinkpanther, @Shaj,
We don't use TR for live market data. We get live market data directly from the exchange.
We will include open interest in next version of websockets.
Hi @rktheinvestor1,
Check out example for placing bracket order here.
Square-off value, trailing stop-loss and stop-loss must be in points.
The minimum value of trailing stop-loss is 1.
@Shaha,
Yes, it can be maximum of 8 characters. There are no other restrictions.
We checked for MCX, it was working fine. We will check for equity today.
Hi @sahilsingh,
Check out this thread for more information about T2T segments. Usually, tradingsymbol will have the series name like BE, BL appended to it.
For EQ segment instruments, series is not appended.
Hi @Thamarai,
As of now, you need to subscribe for historical data for accessing same day's data also.
As an alternative, you can use streaming websocket API to generate your own candles.
Hi @sudhirshettyk,
I am afraid we can't give bulk CSV dumps as there are regulations around it.
If our historical API doesn't serve your purpose then I would suggest using any NSE authorized vendor.
In future, we will provide some kind of mechanism…
