The only thing the 1 point minimum does as far as I can tell is disincentive users from adding them for smaller stocks. And per the thread you sent me, its because of load on your servers. But this seems like basic functionality dont you think?
Im asking because these seem like basic functionality you need to offer.
I get that you are putting out all this new code for new platforms, new versions, etc, etc. But you still lack a basic functionality like having trailing stop losses not be …
"Nifty contributes to over 75% of trades on exchange, if we allow less than 20 ticks, clients are bound to place it. Nifty typically moves 10 to 20 ticks every couple of seconds, which would mean SL having to be modified every 1 second. This can add…
I mean, for scalping it becomes difficult when we're going for small moves with low value stocks. Plus AFAIK its not a limitation from the exchange. So why is there a minimum.
@Nikhil.A ... im not sure how this was from the exchange itself.
Please see the response from @sujith
"
There was some corrupted data in the system which was cleared today. It happened to all the scrips. We have informed data team to monitor so t…
Thats exactly what Im trying to tell you.
1. Why didnt you get back to me yesterday?
2. What is the root cause of this problem
3. Will this happen again
4. How many instruments we affected with this CORRUPTED DATA???
5. What is the timeframe that …
Did you not see my reply from yesterday which i will paste again for your reference:
"
Im seeing timestamps like 13:07 for 5m data...Shouldnt they all be multiples of 5m?
{"date_time": "2017-07-10T13:07:00+0530", "symbol": "VEDL", "period": "5m", …
@sujith This is ridiculous . The numbers have changed this morning.
{'close': 259.85,
'date': u'2017-07-10T13:10:00+0530',
'high': 260,
'low': 259.5,
'open': 259.75,
'volume': 15339},
WHy was the date showing 2017-07-10T13:07:00+0530??? …
Im seeing timestamps like 13:07 for 5m data...Shouldnt they all be multiples of 5m?
{"date_time": "2017-07-10T13:07:00+0530", "symbol": "VEDL", "period": "5m", "last_quote": true, "volume": 34364, "high": 260.2, "low": 259.5, "close": 259.8,...
This is what your website says about KITE CONNECT
"Connect APIs to execute real orders, obtain live market data, manage portfolios and more."
And now after paying you're saying you cannot provide live data??
Can someone respond that this is being looked at?
I called the Zerodha office and they say to email Rainmatter... there is no response from rainmatter.
This is happening for the 15m period also.
Request for 15m data at 2017-07-06 13:46:02,283 HINDALCO
(truncated)........{'volume': 136289, 'high':
198.05, 'low': 197.65, 'date': u'2017-07-06T12:45:00+0530', 'close': 198, 'open': 197.75}, {'volume…
Thanks I looked at it. In your example from the thread:
order_place(exchange = 'NSE',
tradingsymbol = RCOM,
transaction_type = 'BUY',
quantity = 44,
price = 19.6,
product = 'MIS',
order_type = 'LIMIT',
validity = 'DAY',
trigger_price = '0',
disclo…
Im assuming the 10:00 AM candle is for 9:45 AM to 10:00 AM and thus should be already constructed.. So why is it changing at 10:02 and 10:03 right up until 10:15 after which it seems stable
Please can you explain to me whats going on here...
Here are some historical requests that I made at today for INFY 15m period
10:02 AM - INFY
{'high': 970.95, 'volume': 6806, 'low': 970.35, 'date_time': u'2017-06-02T10:00:00+0530', 'close': 970.3…
I think its only fair that you dont put the onus on the customer to figure out previous inst tokens considering this is a paid service and on your website you state pretty explicitly that you provide "HTTP/JSON API for accessing historical (OHLC + v…
