API Documentation

Subscription Plans & History Limits

Quotas & PlansStandard Spec

Subscription Plans & Historical Access Limits

GridMap enforces deterministic rate limits and dataset retention boundaries based on your subscription tier. Every request—whether initiated via the interactive web documentation ("Send Request") or programmatically using an API Key (x-api-key)—consumes 1 credit against your active plan quota.

Comparative Plan Matrix3 tiers configured
Plan TierMonthly / Yearly PriceRate Limits15-Min IntervalsHourlyDailyMacro (Mo/Yr)API Keys
FreeFREE
$0 / ₹0
5 req/min
100 req/day
7 Days30 Days90 Days24 Mo / 5 Yr1 Key
DeveloperPOPULAR
$19.00/mo
₹1,499/mo
30 req/min
5,000 req/day
90 Days365 Days1095 Days60 Mo / 10 Yr3 Keys
Pro
$49.00/mo
₹3,999/mo
Unlimited
Full History
(2012 – Present)
Full HistoryFull HistoryFull History10 Keys

Plan Tier Breakdowns & Target Use Cases

Free Tier

$0 / Free Sandbox

FREE

Essential sandbox telemetry for prototyping, validation, and learning the GridMap API schemas.

Rate Limit
5 req/min
15-Min History
7 Days
Capabilities
  • 5 requests / min (100 / day)
  • 7 days 15-min interval history
  • 30 days hourly aggregations
  • 90 days daily summaries
  • 1 production API key
  • Community email support
Developer Tier

$19.00/mo (₹1,499)

DEVELOPER

Designed for independent energy analysts, automated cron pipelines, and systematic algorithmic models.

Rate Limit
30 req/min
15-Min History
90 Days
Capabilities
  • 30 requests / min (5,000 / day)
  • 90 days 15-min interval history
  • 1 Year hourly aggregations
  • 3 Years daily historical summaries
  • 3 active API keys
  • Standard developer support
Pro Tier

$49.00/mo (₹3,999)

PRO

Enterprise-grade market telemetry with unlimited rate limits and full historical depth back to market inception.

Rate Limit
Unlimited
15-Min History
Full (2012+)
Capabilities
  • Unlimited requests / min & day
  • Full 15-min history (2012 – Present)
  • Full hourly, daily, monthly history
  • 10 active API keys with custom labels
  • Priority SLA & dedicated channel

Architecture: How Rate Limits, Expired Plans & History Restrictions Work

1. Rate Limiting & Expired Plan Handling

Every endpoint monitors request volume and subscription validity through deterministic checks:

Burst & Daily Quota: Evaluates requests per minute and per 24h UTC.
Expired Paid Plan (HTTP 403): Expired paid subscriptions no longer silently auto-convert to Free. Users can renew or call POST /api/v1/subscription/me/ with { "plan_code": "free" }:
{
  "detail": "Your Developer plan expired on 2026-11-16. Please renew your subscription or switch to the Free plan in your dashboard to continue using the API."
}
2. Historical Retention & Date Filtering (HTTP 400)

When you filter by date, start_date, end_date, year, or month older than your plan allows, the API returns 400 Bad Request with an upgrade message under that parameter key:

{
  "date": [
    "Your Free plan allows access to historical data from 2026-11-09 onwards. Please upgrade your subscription plan to access older historical data."
  ]
}