NSE has introduced the new Nifty weekly options from today. In order to support that and make everything uniform, we have switched to the exchange specified format.
Your observation is correct. You can expect up to 1 tick per second for a highly liquid stock. You can subscribe for up to 3000 tokens per connection and with one api_key you may open up to 3 websocket connections.
The number of subscriptions will n…
The source for candles data and websockets API are different. It will not match the exactly but it will be near.
The use-case is same as mentioned the above tradingqna thread.
@manhat,
There can be thousands or lakhs of ticks at the exchange, it is not possible for any of the platforms to capture all the ticks via the internet. We as a member of the exchange just get Level-2 data which means you can expect a maximum of on…
The objective of providing historical data is for backtesting purpose only. We don't recommend using it for live strategies.
The way it works is, we listen to all the ticks for all the instruments that are being traded for the day and end of the min…
This could be because by the time candle is fetched from the database the request is timing out. We recommend using websocket data to generate live candles at your end. You can check out this thread to get started.
Recently, we had changed the infrastructure. Nginx by default changes the route to lower case.
We have now moved to HAProxy wherein the behavior is different.
Hi @enliyo,
The historical data is provided only for testing purposes. We don't recommend using it for live strategies.
You need to generate candles at your end using Websocket data. If you have data loss then you may have to backfill it in your dat…
Exchange re-uses the tokens once an instrument expires, so you can't really fetch historical data for expired instruments. You need to use continuous data feature to do so. You can check out documentation here.
Please do note that we only provide d…
The Kite Ticker module of pykiteconnect exposes a method called subscribe, you can keep the instance of ticker in your code and call the method.
on_connect is only called once after a new connection is established. You don't actually need to kill c…
Can you let us know more about your setup and the library you are using and version of the library you are using?
Make sure to paste a sample code to reproduce the issue.
OMS runs BOD process from post-midnight to early in the morning. This is the error message which is thrown when OMS is not responding.
We are waiting for APIs from our OMS vendor for Sandbox APIs. We can only provide Sandbox after they give us the A…
Hi @Mike,
Kite Connect is purely an execution platform wherein you just call REST-like APIs, we don't host infrastructure.
You can check out FAQs here.
You need to offload your stuff from on_tick to some other thread. Ideally, a user is not supposed to block on_tick. The main thread should always be available to listen to incoming binary data.
The depth error is because the first tick you receive …
Once you get an access token it is valid for one whole day. You will have to log in the next day before the trading session. You can know more about it here.
Hi @prat,
It is updated every day. You won't see any drastic change but maybe few instruments moved from EQ to T2T segment or adding new instruments after expiry and removal of expired instruments.
Please note that the exchange might re-use the toke…
Hi @musafirsafwan,
We don't have bulk fetch APIs for fetching historical data. If the provided API is not a feasible solution then I would suggest using the Websocket live streaming data to generate candle data at your end.
You can get started from …
Hi @vijoeyz,
Historical data subscription is an add-on subscription which can only be availed after a successful base subscription.
Once you create a Kite Connect app, you can go to the app details page wherein on the right side you can find the add…
Hi @enliyo,
We have enough bandwidth allocated at AWS and Cloudflare. I think it has something to do with the connectivity between Digital ocean and AWS/Cloudflare.
I would suggest raising a ticket with Digital ocean.
Can you paste a sample request for which it failed with exact params and response?
@balajimit,
The support team is aware of the technicalities of the APIs, they won't be able to provide you with a solution. Hence, they will ask you to post it here.
An access token is valid for one whole day. You don't need to generate it every time you run the script.
A request token is valid only for a couple of minutes and can be used only once.
Once you have an access token store it and re-use it until it i…
It seems like your website is down. But that shouldn't matter for redirects after a successful login. You just need to read the request token from the URL.
Can you run it in debug mode and paste the complete stack trace here?
Make sure to mention the pykiteconnect version, your system details and exact params you are passing while placing the order.
The historical data provided does have candle data of 1min interval but we provide it for backtesting purpose only.
For live strategies, we recommend using live market data provided using websockets to generate candles at your end. You can refer to …
Hi @AmitPal,
We have informed the data team to look into this. For now, a feasible solution is either you handle the exception and retry. If it is not a viable solution for you then I would suggest generating candles at your end using live market da…
You can only pass a maximum of 8 alphanumeric characters. I just tried and I got the tag in my orderbook.
For more information, you can check out documentation.
@neerleo88,
The library is being used on many production apps which includes our own products as well.
We don't see any issue.
I would suggest going through API documentation and pykiteconnect documentation to know more insights about the Kite Conn…
