Hi @Chandramohan,
You can get it from Kite Connect but the in order to use it you need an active subscription. Instead, you can check out NSE Bhav copy which will have all the above details and it is free.
Hi @varaprasady,
Trigger price must be multiple of tick size always.
Kite Connect is by default for only personal use. You need to have two active Apps to use it with two client ids.
For now, we are running a promotion campaign you can promo code "W…
Hi @varaprasady,
Can you elaborate?
We haven't released anything yesterday. Stoploss value doesn't exist in case of cover order. Stoploss value is used only for bracket order.
Hi @Ajax,
Check out this thread.
It is available for only future contracts and not options contracts.
For options contracts, it won't be continuous charts data since it will end at zero every month.
If you want data then you can check out NSE websi…
Hi,
You will have to use historical data API to get open and close of previous day.
Open is previous day's open which you will get it in previous day candle data and for a previous close, you need to fetch current day's candle and check for close pr…
Hi @ashwinjain1,
Yes, it does support fetching data in min and day intervals. You will have to create weekly candles using day candles. You may check out here.
Hi @sashiks1009,
All Kite Connect API calls are authenticated using access_token.
The access_token is valid for one whole day whereas request token is valid for one time and valid for a couple of minutes. Once you get the access token, store it in p…
@Encrypted,
In .NET client session hook is invoked for every 403 errors which can be any other issue like invalid api_key(ForbiddenError in KiteConnect's context). We will change it to only invoke session hook when there is TokenException.
Hi,
I just tried and I got this response
{
status: "error",
error_type: "InputException",
message: "No candles found based on token and time and candleType."
}
Hi @rampellisrinu,
The app secret is only available for Kite Connect App and not Kite Publisher.
We don't have sandbox environment yet. We will add it in future. As of now, you need to subscribe to Kite Connect in order to try it out.
Hi @lazydragonfist,
Please don't hijack the thread. Your query has no relation to this discussion's heading.
Open a new thread for new queries always as it might help others who are facing the same issue, we will look into this.
Hi,
Continuous future data is available for future & options contracts.
We only provide day's data for expired contracts.
You can check out documentation here https://kite.trade/docs/connect/v1/#historical-data
Hi,
You can check continuous feature mentioned here https://kite.trade/docs/connect/v1/#historical-data
You just need to pass continuous=1 as param to get historical data for expired contracts.
PS: We only have day's candle for expired c…
Hi,
It might be 10 to 15 seconds but that is just arbitrary as anything can while writing to database like disconnection, if one request for some reason gets slowed down it will affect next writes also.
But it won't be as late as 1 minute.
Hi,
This might have happened because you logged into Pi or NEST or if you log out of Kite.
If you haven't logged in then can you let us know, when you logged in and please add some more information like is it happening only for historical dat…
Hi @shankar1318,
Whatever you are doing is correct. The values will not exactly match because the source for historical data is different from Kite ticker. It will be near but not exactly same.
Candle data of two platforms will never be same as it i…
Hi @sidverm,
I would suggest using multi-threading. Your main thread should only receive data and nothing else.
Once you get data pass it to a worker thread to generate panda frame and store it in the database.
@shankar1318,
We are doing some maintenance work. Hence we had taken authentication down. It will be up in a couple of days.
Can you let us know your use case, we will let you know if it fits your purpose or not?
Hi @premkumar,
KiteConnect API subscription is bound to client id and not strategies.
You don't need Pi bridge for using KiteConnect.
You can automate, but you need to login everyday once as it is mandatory by the exchange that a trader …
Hi @haribabu,
We have rewritten the backend from scratch at our level and upgraded numerous things at the OMS level for increased speed and stability. We've released some new features last month and will continue releasing more this month.
Hi @razcads,
I think you need to create a new session when it happens.
Quote and positions are from the source.
Don't use PI or NEST for monitoring, use Kite for monitoring purpose. If you log out from any platform then also this can happen.
Hi,
You just need to store access_token and public_token in text file or database and re-use it.
You just need to make sure request_access_token is not called in subsequent run.
Hi,
Most of the APIs are already migrated. There are a couple of APIs for which response format will change(minor changes), we will announce changelog soon.
Hi @kartik.trade,
The source for Quote API is different from websockets and multi-quote. I am afraid we can't add it in Websockets or in multi-quote fetch as of now.
Hi @Manjunathan,
Both sources are different. Kite Ticker might not have received the tick wherein depth was updated.
You can go ahead and place the order, if it matches then it will be executed.
Why there is a difference ?
Check out this thread.
Hi @krsacme,
As of now postbacks are only sent for executed orders like COMPLETE, CANCELLED and REJECTED.
You won't get postbacks for pending orders.
In future, we will include postbacks for every status change.
Hi @gkannan1965,
It seems like your websocket connection is lost. You will have to re-connect again. You can also use the re-connect feature provided by pykiteconnect.
Hi @tns_ranjith,
In order to implement postbacks, you need a simple server setup which is live all the time so that Kite can post data whenever an order is executed.
As of now, you can't do it in the local client application.
In future, we will addr…
Hi,
You can get candle data of a particular minute in Historical API.
You need to subscribe for Historical data, in order to use that API endpoint.
The response from historical API is JSON. I am afraid we can't provide data in any other format as th…
Hi,
Kite Connect has only two types of subscription, one is base subscription and an add-on subscription for historical data.
You need to create a new app and use that api_key for subscribing to rest of the tokens.
Hi @razcads,
For a given contract with one type of product, there will only one entry in the positions. There is not id for positions.
As an alternative, you may try to find a position with instrument_token and check for the product type.
@sachinstlko09,
Please don't spam with same question.
You can check out answer here https://kite.trade/forum/discussion/2241/php-api-what-should-be-the-product-attribute-value-for-the-bracket-order#latest
@sachinstlko09,
You can go through the above example, we use it for testing. Please read and understand before you implement something.
If you have doubt you can go through documentation for details about each parameter.
Hi,
You can take a look at this image wherein the value of 14:28 candle on 27 September 2017 is 271k.
Following is the value of historical API,
[
"2017-09-27T14:28:00+0530",
419.55,
420.9,
419.55,
420.1,
270665
]
PS: Kite charts data is served us…
Hi,
Open of the day is based on pre-market order matching which happens at the exchange.
There is no relation between yesterday's close and next day's open.
Hi @Ajax,
It's not about the platform. It is the source of data. Source for historical data and websockets data are different.
It is not guaranteed that ticks received at one endpoint will exactly match on another endpoint. It will be near but not e…
@sachinstlko09,
It depends on your requirement. If you don't want postback then don't set it up.
Please open a new thread for new queries. It might help others.
Hi @arsh_makker,
Place order API takes care of only placing an order. If orderPlace API is successful then it means order placement is successful not execution. It will not know what is the status of the order.
@Gyan.Sikdar,
Can you let us know tradingsymbol for which you are trying and HTTP status code?
You can't request to websockets. It will keep streaming data. You need to store it once you get it inside onTick() and read from there.
@krtrader,
Not really, let's say an MIS order was partially filled at 3:20 and it was canceled by Admin then you might get postback as canceled but filled quantity field can be non-zero.
Currently, postbacks are sent whenever OMS sends us notificat…
Hi @krtrader,
An order can be filled in multiple trades. Let us say you placed an order for 1000 quantity, only 500 got filled in one trade then pending_quantity and unfilled quantity will be 500 and filled_quantity will be 500.
In future, we will b…
Hi @v4vikash,
Gateway timeout is different from TokenException.
TokenException means your session is expired. Gateway timeout means request timed out before fetching data.
Historical API is used by all our platforms and Kite Connect users. There are…
Hi @arsh_makker,
We don't have this data at our end. For now, that is the only source. We will try to find out if data is available somewhere to provide it in Kite Connect.
Hi @v4vikash,
Your session might be cleared when you log into Pi or NEST. I would suggest using Kite for monitoring purpose and if you log out of Kite then you will be logged out of everywhere.
