I too am facing the same issue today. The publisher key worked fine till yesterday and is still active. No changes have been done from my side. Please look into this.
@sujith , After April, INDIAVIX is no more supported by the exchange like you said. So, Could you please remove this from the Margins API at https://api.kite.trade/margins/futures accordingly? Because duplicate entries are still showing now for INDI…
Ah ok. I understand how to get it now, thanks!
Also, another requirement was to have the Open Interest data and Traded Value or Turnover (in INR) for the day for the contract in addition to the Volume data that's available.
Yes, I can get data for NIFTY17SEPFUT from 01-sep-2017 to 28-sep-2017 using continuous flag as true. But NIFTY17SEPFUT itself was also traded in the month of Aug 2017, for which the data is not available right now. Any way you could support getting …
Ok, let me clarify. By historical data for past contracts I meant that I should be able to get the data for NIFTY17SEPFUT contract or NIFTY16JULFUT contract, for example. I may not have the instrument tokens for these past years contracts, but shoul…
@sujith I am referring to the data for all the contracts starting from time you provide history for. The instrument dump only has currently active contracts list. Day candles for expired instruments are provided only for the respective current mont…
@sujith , the delivery intention period starts even before the expiry dates of the contracts. See https://tradingqna.com/t/which-commodity-contracts-are-compulsory-delivery-contracts-which-are-not-what-is-delivery-intention-period/2144 . These dates…
Now, the login has started working again. But the quantities for commodities are not getting correctly set in the basket.
On adding commodities , the quantity is being incorrectly set to the commodity multiplier value instead of the passed value.
F…
Basically, the margin shown here changes from day to day: https://zerodha.com/margin-calculator/Futures/
So, margin will be different on different days for the same instrument e.g. NIFTY futures. So, need a way to retrieve the historical margins for…
Are the commodity lot sizes guaranteed to not change in the future also? Otherwise, it is better to have these values in the API so that we can keep track of it...
@sujith , is it possible to send the commodity instruments weights also in https://…
@sujith , I still don't see it at https://api.kite.trade/margins/commodity from the link you mentioned above.
Let me know if I am missing something or has the commodity multiplier information not yet been added?
Hi @Kailash ,
Would you be releasing the official Android SDK? Or is it not planned any more?
An official client could be useful to minimize impact of API changes to user apps.
Hi @Kailash , @sujith ,
Regarding
Continuous futures historical data
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?
hi @Nikhil.A ,
Another option would be to have some amount of historical data bundled with the streaming data plan. This is also done by all real-time data providers (for e.g. globaldatafeeds, which provides last 1 month of intraday historical data…
@chaudhariapurva , thanks a lot for this amazing library! I was able to use this in RightEdge (a trading tool in C#) and it is working fine.
I have also modified the Login.Initiate() method to have a WebBrowser control which takes care of fetching t…
Yes, I understand that. The weights are required for some other calculations in the application. As an example, it is being used in slippage calculations. So, for a buy stop order, the Slippage Amount would be =
(average_price - trigger_price) x (N…
Hi @Kailash , Thanks for the fast response. Now, how can we get the weights for the Instruments? Can you arrange to pass this also as a separate column for the commodity instruments?
And how about for CDS segment? (USDINR16JULFUT in the example abo…
@Kailash , I was not referring to the size, which is fine. But the number of entries which currently is > 60,000. As an example, if we are using Google AppEngine as our backend, it restricts number of datastore entity writes to 20,000 per day (in…
Hi @Kailash , by making F&O tokens continuous for historical data, you mean for any given day, the price shown for the instrument will be the same as that of the corresponding contract with the nearest expiry, right? By when can we expect this?
…
Hi @KUL , I used the Google AppEngine for my Backend Server which receives the Postback Calls. See https://cloud.google.com/appengine/ . And then used Google Cloud Messaging to send these notifications from the AppEngine to my mobile (Refer: https:/…
Hi Kailash,
Thanks for providing the Postback API.
I implemented it and it's working fine, except for the values that I am getting for my Order.
The "status" field is giving the correct value - for e.g. "Rejected" but the "status_message" field i…
