india macro.api

Every Indian macro release,
one clean REST API.

RBI MPC decisions, CPI & IIP, GDP estimates, GST collections, Union Budget, SEBI board meetings, weekly forex reserves. Pre-computed dates, post-release actuals, one consistent JSON shape. Stop scraping PIB.

RBI MPC CPI / IIP GDP GST Union Budget SEBI Forex Reserves WPI

Macro data for India is fragmented. This isn't.

Every other macro API is built for the US. The Indian releases — RBI, MoSPI, PIB, SEBI — live across a dozen government sites in PDFs, press releases, and HTML tables. We did the scraping so you don't have to.

One JSON shape

Every event — MPC, CPI, GDP, Budget — returns the same fields. No source-specific parsing. Drop into your model in 30 seconds.

📅

Dates ahead, actuals after

Future release calendars pre-computed for the full fiscal year. Actual values backfilled within hours of each release.

🇮🇳

India-first, not US-first

Fiscal year mapping, IST timestamps, INR units, official sources from RBI/MoSPI/PIB. Built for the desks that actually trade Indian macro.

One curl call. Real data.

Pass your API key via the X-API-Key header. That's the whole auth.

curl -H "X-API-Key: imk_..." \
  https://indiamacro.ameeshkatariya.com/v1/next/rbi_mpc_decision
import requests

r = requests.get(
    "https://indiamacro.ameeshkatariya.com/v1/next/rbi_mpc_decision",
    headers={"X-API-Key": "imk_..."}
)
event = r.json()
print(f"Next MPC: {event['event_date']} ({event['days_away']} days away)")
const r = await fetch(
  "https://indiamacro.ameeshkatariya.com/v1/next/rbi_mpc_decision",
  { headers: { "X-API-Key": "imk_..." } }
);
const event = await r.json();
console.log(`Next MPC: ${event.event_date} (${event.days_away} days away)`);

Response:

{ "event_type": "rbi_mpc_decision", "title": "RBI MPC Rate Decision – Meeting #61", "event_date": "2026-06-05", "days_away": 8, "impact": "high", "category": "monetary_policy", "id": "99ecdc37-5575-4aa6-b95c-effc2485b68b" }

Who's already shipping with this shape of data

Quant desk

Event-driven backtests

Pull historical CPI surprises (actual vs forecast) and align them to your INR/NIFTY series. The /v1/historical endpoint gives you the surprise field pre-computed.

Retail trader

"Don't miss MPC" alerts

Cron-poll /v1/next/rbi_mpc_decision every morning. Push to Telegram or your trading journal the night before high-impact events.

Fintech app

In-app economic calendar

One /v1/upcoming?days=30 call powers a clean calendar widget. No scraping, no maintenance, no 4 AM pages when a government site changes its HTML.

Research / desk

Surprise tables & commentary

Daily morning note? Pull actual, forecast, previous for any series and let your report template do the rest.

Eight endpoints. That's the whole API.

Full schema and live "try it" buttons at /docs.

Simple per-month tiers. No usage surprises.

Free

₹0 /mo
  • 5 calls/day
  • 60 calls/min
  • All endpoints
  • Community support
Get started

Pro

₹4,999 /mo
  • 100,000 calls/day
  • 1,000 calls/min
  • Priority support
  • Historical depth: 5+ years
Get started

Enterprise

Custom
  • Unlimited calls
  • SLA & uptime guarantee
  • Dedicated support
  • Custom data sources
Talk to us

Create your API key

Free tier is 5 calls/day so you'll burn it fast testing. Then upgrade or just wait until midnight UTC.

Already have an account? Sign in

Common questions

Where do you get the data from?

Official sources only — RBI press releases for MPC dates and forex reserves, MoSPI for CPI, IIP and GDP, PIB for GST collection figures, Office of the Economic Adviser for WPI, SEBI for board meetings. We don't make up dates or estimate values. If the official source pushes back a release, we update within hours.

How fresh is the data after a release?

Future dates are pre-computed from official calendars at ingestion time, so they're always there. Actual values (e.g. June CPI = 4.3%) are backfilled within 4 hours of the official release in the median case.

Do I need to handle scraper drift, source-site changes, holiday adjustments?

No. That's the whole product — we deal with the messy ingestion so you get one boring, consistent JSON shape forever.

What about uptime / SLA?

v1 is hosted on Digital Ocean + Supabase with HTTPS. We're not promising 99.9% uptime on the free tier yet — that comes with Pro and Enterprise. Status page launching soon.

Can I get historical data going back 10+ years?

v1 ships with the current fiscal year + the previous one. Deeper history (5y, 10y, since-base-year) is on the Pro roadmap and available now on Enterprise.

Do you support webhooks / push notifications for events?

Coming in Starter. Tell us via the form below or email if you want it sooner — we'll prioritise based on customer demand.