API Documentation

Introduction & Architecture

Overview & Architecture

GridMap IEX Market Data REST API

Programmatic, low-latency market clearing telemetry for physical power spot markets, 15-minute dispatch intervals (fsv & fsv_*), renewable generation disaggregation, and regional transmission dispersion across India (IEX DAM, GDAM, State DAM & State GDAM).

Data Architecture: 15-Minute Single Source of Truth (SSOT)

Deterministic Ingestion & Mathematical Reconciliation

At GridMap, deterministic physical clearing telemetry is the immutable foundational layer and single source of truth across all supported IEX markets. We ingest raw clearing feeds directly from IEX 15-minute dispatch blocks (96 blocks/day), validate telemetry checksums, and store every discrete interval as permanent ground truth.

1. Base Ingestion
Native Clearing Feeds

Official clearing telemetry (96 blocks/day in IEX DAM, GDAM & 36 States).

2. Hourly Rollups
4-Interval Aggregations

Arithmetic & volume-weighted prices, spread analysis, and peak/trough bounds.

3. Daily Summaries
VWAP & RTC Metrics

Volume-Weighted Average Price, Peak vs Off-Peak windows, and total daily energy (fsv).

4. Macro Trends
Monthly & Yearly GWh/TWh

Long-term tariff benchmarks, seasonal volatility indices, and capacity analytics.

Active Market Architecture

IEX Live Grid
๐Ÿ‡ฎ๐Ÿ‡ณ

India โ€” Indian Energy Exchange (IEX)

96-Block Dispatch & 36-State Transmission Dispersion

Base Ingestion: 96 Blocks / Trading Day

Ingests 96 discrete 15-minute time blocks (00:00 to 24:00 IST) across Day-Ahead Market (DAM), Green DAM (fsv_solar, fsv_wind, fsv_hydro, fsv_non_solar), and State DISCOM drawals.

Rollup Hierarchy

Computes 4-block hourly averages, true 96-block Volume-Weighted Average Prices (VWAP), RTC base rates, evening peak windows (18:00โ€“23:00 IST), and state TWh balances.

Public Discovery vs. Authenticated Telemetry

The discovery endpoint (/api/v1/iex/meta/) and homepage metrics do not require authentication and do not consume plan rate limits. All market data list endpoints require a valid x-api-key header.