| Dataset | Consumer Price Index, All India |
|---|---|
| Dataset id | mospi.cpi |
| Series | 8,689 |
| Observations | 321,769 |
| Countries | 1 |
| Period range | 2011-01-01 to 2026-10-01 |
| Vintages | 7 |
| Last fetched | 2026-11-13 10:49 |
| Poll interval | 1 days |
| Archive | mospi/cpi/*.json.gz |
| Licence | Government Open Data License - India |
| Redistributable | with-attribution |
| Terms assessed | 2026-09-11 |
| Attribution | Source: Ministry of Statistics and Programme Implementation, India, Consumer Price Index, eSankhyiki (https://esankhyiki.mospi.gov.in/). Published under the Government Open Data License - India (https://www.data.gov.in/godl). This does not imply endorsement by the data provider. |
The connector's own docstring, verbatim. It lives beside the code so it cannot drift from it.
India MoSPI connector: national CPI with source-native sectors.
The eSankhyiki API is the Ministry's current, keyless publication route. The 2024-base release carries 668 national Combined categories and a source-made headline back series for 2013--2024. The retired 2012 and 2010 bases remain available and are kept as separate series sets.
Only All India is collected and exposed, under the owner-directed India exception. Combined, Rural and Urban sectors retain full native categories. Historical all-area raw responses remain immutable archive context. All India Combined is the national default. Bases are never spliced: MoSPI's own 2024-base Back and Current rows share an id because the source publishes them as non-overlapping segments of one base; 2010 and 2012 stay separate. The 2024 classification is COICOP 2018, not the COICOP 1999 vocabulary used by the IMF flow, so it remains source-namespaced below the headline.
MoSPI's published index and year-over-year fields are stored unchanged. Absent rate variants are derived by the shared driver from complete replay units. Recent windows and full audits retain exact source response bodies; a changed window boundary forces a full audit to preserve rate context.
The API server requires OpenSSL's legacy-server-connect compatibility bit. Unlike the Ministry's reference client, certificate and hostname verification remain enabled; only the legacy renegotiation option changes.