Wrong historical data
-
@admin one more issue I have been through is that it gives wrong closing price, sometimes the difference with actual closing price is bigger..so plz take a look at this also
-
Hi @Asif-Khan we have noted this.
-
@admin again today
2021-04-28T13:50:00+05:30 916.5 919.0 916.3 918.15 116747
2021-04-28T13:50:00+05:30 916.5 919.0 916.30 918.75 72718
just look how the close value is vast different for the same candle data
-
Hello @Asif-Khan we have noted this issue we have passed the issue to the team we will update you.
-
Hi @Asif-Khan please specify the time at which you hit the historical API both the time and what time you got the response also provide us with your client id to further assist you.
-
@admin hi my client id is S429972
first response I got at 13:55
second response at 14:00 -
Hi @Asif-Khan for what time frame you are trying to get the data.
-
@admin FIVE_MINUTE
-
Hi @Asif-Khan as per the discusion on the mail us your code snipet.
-
@admin yes I have mailed already
-
@admin Hi, I haven't got any reply for my query, could you please check and revert ??
-
Hi @Asif-Khan historical data API is working fine from our end.
-
@admin but I have shown the response as well as my code, what m I doing wrong?
-
hi @Asif-Khan called @ 16.19
req:
{
"exchange": "NSE",
"symboltoken": "3045",
"interval": "FIVE_MINUTE",
"fromdate": "2021-04-28 13:00",
"todate": "2021-04-28 13:50"
}response:
{
"status": true,
"message": "SUCCESS",
"errorcode": "",
"data": [
[
"2021-04-28T13:00:00+05:30",
363.2,
363.2,
362.5,
362.65,
478210] ]}
-
called @ 16.21
{
"status": true,
"message": "SUCCESS",
"errorcode": "",
"data": [
[
"2021-04-28T13:00:00+05:30",
363.2,
363.2,
362.5,
362.65,
478210
], -
This post is deleted! -
@ikishor99 said in Wrong historical data:
{"data":[["2021-06-21T09:15:00+05:30",1769,1776.8,1750,1776.25,60273]],"message":"SUCCESS","errorcode":"","status":true}
["2021-06-21T09:15:00+05:30",1765.05,1776.8,1750,1776.25,60273]
This is huge, and there are many places where data is wrong everyday
-
HI @ikishor99 this issue is already noted on another thread our team is working on this.