Historic API data format inconsistency
-
Hi Team/ @admin ,
Two things I wanted to highlight:
- Historic data API data is not formatted. Would expect some formatted data like a json or array like below.
['2021-02-26T09:36:00+05:30', '398.45', '398.70', '397.55', '398.70', '369539']
['2021-02-26T09:37:00+05:30', '398.70', '398.80', '397.70', '398.15', '160988']
['2021-02-26T09:38:00+05:30', '398.20', '398.45', '398.00', '398.25', '92355']
['2021-02-26T09:39:00+05:30', '398.25', '398.50', '397.85', '398.50', '236942']
['2021-02-26T09:40:00+05:30', '398.25', '398.25', '397.80', '398.00', '171589']- Also the formatting also not consistent. For example, below snippet doesn't have comma in the highlighted place. in fact it is missing every now and then..
2021-02-26T14:59:00+05:30,393.35,393.50,393.20,393.25,96383\n2021-02-26T15:00:00+05:30,393.15,393.15,391.60,391.60,6875652021-02-26T15:00:00+05:30,393.15,393.15,391.60,391.60,687565
-
Hi @Ashok we have change our historical data format.
-
@admin Any updates on the deployment date ?
-
Hi @Ashok we are ready with our change in format. Testing it now we will update you once it is deployed.
-
@admin Any ETA on the format change and fix ?
-
-
@rjbanna Thanks, json would be much better.
Also I think a parser function can be added in the SDK to return then as OHLC, volume ... ie key pairs
-
@Ashok I had discussion with @bhaveshjain regarding same issue. They are discussing internally. I also suggested them to return data in JSON format.
