Data Fetch Using intraday_minute_data

Hey Team,

I’m trying to fetch the intraday data for a specific time for NIFTY and SENSEX using the intraday_minute_data function. Does it not support Indices or am I making a mistake here.
Here are the parameters that I am passing.
{
“securityId”: “51”,
“exchangeSegment”: “IDX_I”,
“instrument”: “INDEX”,
“interval”: “15”,
“oi”: false,
“fromDate”: “2025-06-11 09:30:00”,
“toDate”: “2025-06-11 10:00:00”
}

1 Like

+1 to this and I am seeing it happening daily from past 2 days in the night ,
It’s so annoying

1 Like

I can see the day for 10th though, I guess it’s a problem with data load? I can’t see T-1 day but T-2 and so on are available.
{

“securityId”: “51”,

“exchangeSegment”: “IDX_I”,

“instrument”: “INDEX”,

“interval”: “15”,

“oi”: false,

“fromDate”: “2025-06-10 10:00:00”,

“toDate”: “2025-06-10 10:30:00”

}

Hello @Kaushik_Kondu

Can you share your Client ID along with the time when you were not able to get the data?

Will get this checked on the logs. There is no such limitation on the API from our side in fetching data for current day.

69oh8
Bolo

Hey Hardik,
here’s the client ID - 1107333956 and time was around the same time when i had raised this query.

I also noticed a difference in response now.

Case 1: I fetched the data of T-1 today i.e data for 12th

PARAMS:
{
“securityId”: “51”,
“exchangeSegment”: “IDX_I”,
“instrument”: “INDEX”,
“interval”: “15”,
“oi”: false,
“fromDate”: “2025-06-12 10:00:00”,
“toDate”: “2025-06-12 10:30:00”
}

response:

Case 2: when I fetch the data for today, I get all the high instead of just the data in the given Time frame. This creates a discrepancy in the algo because I pick the first element always.

Response:
{
“open”: [
80833.48,
80861.23,
80965.13,
80979.74,
80976.19,
80929.3,
80951.96,
81018.09,
81026.76,
81035.67,
81109.41,
81056.97,
81031.76,
81039.4,
81031.32,
81171.88,
81093.38,
81113.51,
81101.07,
81016.33,
80946.62,
81135.43,
81118.6
],
“high”: [
80902.75,
80980.8515625,
81005.921875,
81027.0625,
81037.1015625,
80955.37,
81044.11,
81035.24,
81070.0703125,
81149.671875,
81113.22,
81057.3,
81045.79,
81077.39,
81180.640625,
81238.68,
81151.22,
81125.65,
81146.64,
81054.85,
81147.0,
81192.13,
81118.6
],
“low”: [
80763.55,
80811.02,
80930.97,
80951.56,
80925.9,
80876.88,
80942.44,
80990.23,
81012.33,
81035.67,
81040.71,
81003.57,
81005.46,
81025.66,
81031.32,
81085.15,
81084.58,
81088.89,
81012.46,
80898.26,
80941.02,
81070.18,
81118.6
],
“close”: [
80858.71,
80968.24,
80979.78,
80975.67,
80929.3,
80954.41,
81018.09,
81026.11,
81035.26,
81109.5,
81056.05,
81031.76,
81038.74,
81033.66,
81172.87,
81093.23,
81113.51,
81101.07,
81016.27,
80946.09,
81135.33,
81162.47,
81118.6
],
“volume”: [
0.0,
0.0,
0.0,
0.0,
0.0,
0.0,
0.0,
0.0,
0.0,
0.0,
0.0,
0.0,
0.0,
0.0,
0.0,
0.0,
0.0,
0.0,
0.0,
0.0,
0.0,
0.0,
0.0
],
“timestamp”: [
1.749789E9,
1.7497899E9,
1.7497908E9,
1.7497917E9,
1.7497926E9,
1.7497935E9,
1.7497944E9,
1.7497953E9,
1.7497962E9,
1.7497971E9,
1.749798E9,
1.7497989E9,
1.7497998E9,
1.7498007E9,
1.7498016E9,
1.7498025E9,
1.7498034E9,
1.7498043E9,
1.7498052E9,
1.7498061E9,
1.749807E9,
1.7498079E9,
1.7498142E9
]
}

Hey @Hardik ,

Can you please confirm on the below:

  1. During the market hours will the response structure include all the data irrespective of the time passed in the startDate and endDate? Is this a bug or a deliberate behaviour? The Response structure changes after the market hours where it fetches only the data within the duration passed in the start and End date.