We have been hard at work rebuilding every bit of Kite, Kite Connect, and the underlying low level APIs over the last many months. At the same time, several internal components have already been rebuilt. We're very close to finishing and announcing Kite Connect 3.0 that'll feature several enhancements. Detailed changelog and transition guides will be published as we start rolling the updates out over the next several weeks.
Reduced latency on all HTTP requests
Dedicated, low latency, WebSocket channel
Order and fill / trade updates via WebSockets
More live data fields on WebSockets
Reduced rate limits
Availability of over 2000 mutual funds via Kite Connect
Continuous futures historical data
Margin calculation APIs (phase 2)
Backoffice reports (phase 2 -- trade and PNL history, funds and ledgers etc. from the new back office that's being built)
Welcome Back to Kite Forum...Almost After 4 months (Last Comment 28 Feb).
Its Great...We are eagerly waiting for the update.
@Kailash Can the sandbox be used for paper-trading too?
Also, is there a major divergence from the current api endpoints?
That would help engineer apps better without the workaround. Some data like: And may be nice to haves:
@Kailash Congratulation! for great job.
Maine abhi kuch din pahle hi Zarodha Kite se trading karni shuru ki hai. Ab main robotic system se trading karna chahta hun. please mujhe bataye ki Zerodha ki PI Bridge, Kite Connect ya NEST plus main se kon se fully automated hai. aur kaise ese apply kiya jata hai. kya cost aati hai. Ami broker ka software free milta hai ya chargeable hota hai. Please help me.
Kya ye possible hai ki koi mere system main demo de de full setup ka jo bhi jyada achha ho.
@anupshinde That's a good idea, programmatic access to ecosystem health data. There are no changes to endpoints, but there are a few minor (very minor!) breaking changes (renaming certain fields).
Kite Connect is purely an execution platform. If you want to integrate with Ami broker or any other platforms then you will have to do on your own.
Check out documentation here.
Could you give some rough date and would it be possible to notify on email pls ?
most ppl will be happy to pay for api on live environments, but not for developing their app itself.
@sachet_singh The sandbox is something we've been trying to get from our OMS vendor (TR) for over a year unfortunately, but now we finally have it. We plan to get it going after the 3.0 release. Can't give an exact timeline, but a few weeks, hopefully. Yes, we'll send out an announcement when it's ready.
@pybull There will be a 30 day window where both versions will run in parallel. Please see my comment above about the sandbox. While we're ready with the Kite Connect layer, the delay has always been the underlying engine from the vendor. But soon, we hope.
@Kailash - What can we expect in this? Would you give data for expired series and how far back will this be supported?
@iTank -- I'm getting the exact numbers from the data team.
Will this be available for MCX instruments too?
We don't have MCX data, we have plans to back-populate that data if available at the source.
In next couple of weeks, we will start the migration. We are testing new APIs parallelly right now. We will announce it on the forum.
"Continuous futures historical data" ...
Would data from 2011 be available for ***Options*** also ?
If not then for how many years Options data would be available ?
Superb. Keep it up.
Bring BO & CO in publisher api as well.
1. Comparing traded volume and delivery volume wrt historical volume is one way.
2. Other way is:
a. Comparing traded volume and delivery volume wrt "Total Mkt cap" is very misleading.
b. It makes sense to compare traded volume and delivery volume with "Free Float Mkt Cap"
can you please add master table like instrument table for master field list with field type and length
You can check out data type of each field here
Regarding I assume this feature will be available for all time intervals including 1-minute candles too, right? And will this be available for futures in CDS segment also?
One quick question, will the POSTBACK_URL continue to exist even with kiteconnect 3.0?
Or can the server post event through kiteconnect 3.0 dynamically to client(our python/jave code etc) when an orderstatus change?
I am asking this to just to see whether the webhook implementation can be avoided with this upgrade as it needs all personal domain/public ip etc which might be too much for retail traders.
We are planning to provide order updates via websocket in next version of websockets.
Users might not need to setup servers for postbacks after that. Since it will take some time for the next version of websockets, you will have to setup a server for postback for now. You don't need a domain to setup postback.
The above used to work fine, now its not. Removing the same however fixed the issue. Hope migration will be smooth.
@sujith any ETA. I suppose currently the ball is in TR's court and thus beyond your control.
Any idea when kiteconnect (Python) version 3.0 would be available? I am looking for these main features:
- Order and fill / trade updates via WebSockets
- Margin calculation APIs (phase 2)
Also is there an easy way, given a symbol (500570), to obtain reference info such as Name (Tata Motors), Margin Requirements or corresponding active futures for the stock?
And how can I query current holdings of the portfolio?
Thanks again for your help.
I am afraid we can't give any exact timeline as of now.
Maybe in a couple of weeks.
We are rolling out updates internally and testing it.
We will announce change log on the forum.
Please create a new thread for new queries, it might help others who are looking for the same.
Yes, you can expect Mutual funds API soon. We will announce it on the forum.
So basically I want the kind of data in the here from nse
It will take some time for continuous charts for currency segment. Currently, our data team is working on MCX data.
====>More live data fields on WebSockets
I assume timestamp will be available ? Also is there any plan to give the OI(open interest) info for F&O scripts ?
Not all of us require Live Market Data or Historic Data.
Is it possible for Zerodha to sub-divide Kite API access in the following way:
1. Basic Package
2. Live Market Data Access
3. Historic Data Access
In the Basic Package
1.1 Order and fill / trade updates via WebSockets
1.2 Margin calculation APIs
1.3 Backoffice reports (trade and PNL history, funds and ledgers etc.)
1.4 Opening price for subscribed instruments
1.5 End of Day Closing price (after market close) and EOD LTP
1.6 After Market Order / status of AMO
1.7 Pre-market / Market / After Market is open / is closed
1.8 Exchange holidays
1.9 Zerodha emmergency messages (For example, NSE glitch in trading system)
1.10 Expiry dates for subscribed instruments
1.11 Price Alert
I think pi-bridge (costs only 500/-) provides some of the features. But Kite connect with these basic features will be great as
1. it will be platform independent
2. later up-gradation to Live Market Data or Historic Data with Kite will be smoother
3. It will reduce end user cost for semi-automation
4. End users will be capable of implementing Good Till Date / Good Till Canceled Odrers
'Not all of us require Live Market Data or Historic Data' is quite an assumption.
So basically I want the kind of data in the here from nse
We will add it to our list. We will provide this in future.
First resolve my issue which is same as the following
Instead of releasing new version first try to make your infrastructure proper scalable. I already paid money for your data services and you are having fun with that. No service till now
Before Paying for Historical Data API, Do Look for Forums and other Issues which other are facing with Historical API,
Support is worse, I seriously comment If you cannot provide an email support or call support why the hell you people are charging it, Provide it for free and let the users discuss what could have gone wrong through Kite Connect Forum.
One of the issues which I am facing :
There other posts also complaining about support policy, So beware before paying up.
@jvshk78trade , @arsh_makker , @pinkpanther , @Shaj , @abhizerodha , @iTank , @anupshinde , @ping2balaji , @ishwarm , @joy , @botany02 , @Gopal , @ketanshah
Need your help, Are you facing problems fetching data with Historical API as specified in the post above. Or am I the only one here stuck?
If I am offending someone for posting here, Its because this is my last option to get some support from fellow members.
Please take a serious thought on it. As your pace looks to have reduced. And i am afraid your competitors are running like anything.
Its understood, that you have so many customers and so you need to be more robust, and think twice before introducing new things, so that it doesnt hamper the old stable platform. But... at the end customer demands is the paramount.
But, our pace hasn't reduced. Our tech team has doubled in strength and over the last one year, the entire team's been working on revamping every bit of our infra (including Kite) for scale. Our trading activity has grown exponentially and it takes great amount of effort to keep scaling the systems behind the scenes to keep up. Now, like I said, most of it is behind the scenes, which is why you feel we've slowed down, where as we've upped our throughput manifold
The culmination of one year's worth of non-stop work is going to start hitting the markets soon!
You said that "The culmination of one year's worth of non-stop work is going to start hitting the markets soon!"
Really I am waiting hungrily. But don't know when it will be available.
Make some tutorials for people like myself to start off. Please start tutorials section ASAP, before the expiry of my first paid app I want to atleast once see my trades successfully automated.
Exchanges are very clear that 20 bid and ask market depth is only for displaying on trading platforms. I am afraid we can't provide this feature in Kite Connect.
It will be available on Kite soon. It might be included on Pi in future.
'we know you guys(traders) want it,but there are some reason(our beloved exchanges dnt give or wont give or some reason) why we cant have it now or anytime in future,but from business perspective lets not say we cant give it to you,therefore just use an indefinite term "soon" which can be inferred to as- in the next millisecond to the next 1000 years ' .
Few other examples - feature coming soon as 'the sandbox' .Last year when you guys came up with Kite Connect you said the sandbox feature would be soon..if I ask you now again you would say its going to come soon.
Point being it doesn't help saying 'soon' . I fully understand that you guys are actually putting a lot of effort to make things happen and I appreciate it, but telling things as it is Helps to get a better direction.
Unfortunately, our "soon"s are bounded by so many external variables that we find it extremely hard to commit exact dates. Significant parts of Kite 3.0 has been running in production for months, but we're still waiting on the 5% external variables before we can make a full release.
Just like you guys are developers waiting on us, internally we're also developers waiting on others, slowed down by bureaucracy Personally, I'm positive the 3.0 release and the new features will make up for all the waiting.
@soumyadeep Yes, this is definitely happening. Dedicated ticker instances for the developers. Updated protocol with more fields (this'll take some more time). Order postbacks and other updates via WebSockets. Also, the quotes call will take multiple tokens and return OHLCv for all of them at once. This'll simplify polling to a great extend.
We will add it to our list.