@RJ0958 You'll most likely only get 1 packet per second irrespective of the number of instruments you've subscribed to as multiple ticks are combined into one packet. So, if you've subscribed to 20 instruments, the one packet you get could have tick…
1) Initiate a Connect login (just to be safe, at 9 AM before market opening), do the token exchange, obtain the access_token and set it in your application.
2) Set cron jobs (or some sort of an in-program timer) to trigger your orders. Do note that…
We have data for about 1+ years (expired contracts) but we don't have a way to expose the data in a continuous manner. This is something the data team is working on.
5 is the maximum depth available to broking clients in India.
However, as luck would have it, there's something we're doing in this regard (and this process started literally last week). Can't commit to a timeline yet.
It wouldn't make sense for the API to maintain a state at its end. Why not just build the watchlist very easily at your end? It can be as simple as an array of instruments.
1) Initialize a WebSocket connection, subscribe to those 100 instruments. You'll get data (including LTP) immediately after the subscription request is sent.
2) We rate limit requests to 1/sec, so you can only send 1 order per second at most. This …
Please look at the supported intervals here -- https://kite.trade/docs/connect/v1/#historical-data
You can fetch daily data and form weekly points out of it.
https://api.kite.trade/session/token only accepts POST, that's why it throws a "Route not found" when you try to access it from your browser (which sends a GET request).
Hi @gully -- Lot size changes happen abruptly and we do not get any realtime notifications ourselves, even as brokers. We have to rely on ad-hoc PDF circulars published by the exchanges.
Hence, the most authoritative way of getting these changes is…
@mightymosquito 'ws' (insecure) is just a test endpoint and will be deprecated in the near future. if wss (secure / https) isn't working, there must be some issue with the root certificates on your system, which you should try and resolve.
Run a client (daemon) process that subscribes to the instruments you want to track using the WebSocket API. Using our Python client for this will make things easier.
Every time you receive a tick, you run it against your price conditions, and if th…
Hm, if the hash matches, then it has to be an issue with the request. Can you paste the JSON body (this'll have the error message) accompanying the 403 response?
@dhavalp Is it possible to link the page where you have the buttons integrated? Can't really think of a point where a charting library would conflict with the Publisher js.
@cdesai1987 The APIs are meant for personal use, which means one API key can only work with one account at a time (you can change this ID at any point of time).
Multi user setups are only available for startups and businesses and require exchange a…
@sabyasm We absolutely understand your concern. "MSG_FAILURE" (as unhelpful as it gets) is a mysterious error thrown by the TR OMS. I've forwarded the log to them, and I'm awaiting a response.
@kiran @sabyasm Apart from the the req/sec limit, there are no other restrictions. You just have to space your requests apart so that multiple requests do not go through at the same second.
@jsudhams C# is not a part of our tech stack, hence the delay. We'd like to release it ourselves, but if someone ports one of our existing clients to C#, we'll be happy to feature it.
You don't need a redirect URL for using Publisher. You'll only need it if you want to jump start a Kite Connect session from a Publisher instance.
1) Kite Publisher is the right choice. In fact, we do this with the official Kite chrome extension.
…
@aarush11 You should not comment those lines out! They are critical for proper error handling. What is the exact error message you're getting?
If there's no user_id, it means you the request is not happening correctly.
@soumyadeep We recorded instances of this happening sporadically today. When you catch such an exception, please retry the requests.
As I've said in other threads before, once we replace the underlying TR OMS APIs completely, these issues should go…
All requests to the Kite API are over https, so there is no question of http.
Here are a couple threads with C#
https://kite.trade/forum/discussion/11/kite-connect-api-using-c?style=kite2
https://kite.trade/forum/discussion/210/websocket-response-c…
@dhavalp We're actively monitoring this at our end almost every day but we still haven't been able to reproduce the issue. As Vivek has said above, we've released a beta library that uses a different WebSocket library altogether. Can you give it sho…
These are the interim statuses that an order can go through before it is OPEN, CANCELLED, REJECTED, LAPSED or COMPLETE. Normally, you wouldn't be able to see them as they happen in fast succession internally.
PUT ORDER REQUEST RECEIVED
VALIDATION…
@k365 Where were you explicitly told about VB?
The APIs are simple HTTP requests, so they'll pretty much work universally with every programming language, including VB. Anything that can make HTTP requests (including browser addons, terminal etc.) …
You have to initiate the login flow in the browser. Please refer to the documentation -- https://kite.trade/docs/connect/v1/#login-flow
The flow is well described and illustrated.
@sumit.ssr207 This is on our list, although this most likely will not be built in house. We're looking for developers familiar with Amibroker to get this built.
@DV3508 Try logging in here (this is my app) https://kite.trade/connect/login?api_key=tfvg166w243x6qp0
The redirect end point is the exact script you've pasted above and it works fine. Once the login's done, it redirects to the script and you can s…
@k365 Your app's redirect URL is set to '127.0.0.1'. How do you expect to get the request token after the login without even setting a proper redirect url? Please do not make inflammatory comments and throw accusations at us if you do not have the t…
@DV3508 The request token comes to the redirect url after a successful login. I checked your app and your redirect url is just the url to your website, not the PHP script you have posted above. Obviously, without the request token coming as a query …
@anilbhatt You don't have to login every time, only when the access_token expires (We flush it at 8:15 AM every morning).
You can use WebSockets to receive ticks every second and compute your own 5-min data point and insert to the DB.
The Candles API is an addon to Kite Connect, so if you want that, you will have to subscribe to Kite Connect first (meaning, both the APIs).
Kite Connect gives you realtime OHLC + market depth updates for instruments every second. You may be able t…
Hi @gautam_s60 for buying 1 lot of crude, you have to pass 1, not 100.
Our OMS uses lots (1 = 1 lot) for all commodities, but the depth data comes directly from the exchange. An unfortunate lack of consistency
@abhishek01 Yes, but we're in the process of increasing the max number of subscriptions allowed on a single connection to 500. This should happen in the coming couple days.
@RJ0958 You should use a single connection and multiple subscriptions on the same connection.
Multiple connections are allowed as of now, but this will soon be disabled.
LTP may not have changed but values in the market depth may have. Most of your `orders` values are 65536, which is being casted incorrectly. It is usually a single or three digit number.
@gully app.min.js is a bundle comprised of many dozen smaller Angular modules. Not sure how easy it'll be to extend it. Let me see if I can send you an unminified app.js
@RJ0958 @soumyadeep We're releasing a new beta library that uses the Autobahn WebSocket client. Hopefully these issues (which we still haven't been able to reproduce at our end), will be resolved.
@gully This is actually something we have been contemplating for a while now. However, as it stands, the UI architecture itself is not extensible. We may do this at some point in the future.