May 22, 2026 · 6 min read · Data
Corrected 14 November 2026: the earlier version gave IN-TG as Telangana's ISO code. ISO changed it to IN-TS on 23 November 2023, with three other Indian codes; our data still uses the older four (see below).
ISO 3166-2:IN — state codes that work everywhere.
India has 36 states and union territories. There are at least six competing code systems for naming them, and most engineering teams discover this the hard way — when a join silently drops half the rows.
The six conventions you'll meet
Pull data about Indian states from any three sources and you'll see three different code systems. Off the top:
- Census of India abbreviations — MH for Maharashtra, KA for Karnataka, UP for Uttar Pradesh. Two letters, mostly.
- RTO (Regional Transport Office) codes — same MH/KA/UP for the most part, but they double as the licence-plate prefix and have additional districts beneath.
- Indian Postal abbreviations — broadly aligned with Census but inconsistent for UTs. "DL" for Delhi versus "DEL" depending on the dataset.
- Tourism-board names — long-form, frequently localized. "Kerala Tourism" labels, "Madhya Pradesh — The Heart of Incredible India," etc. Useful for prose, useless for joins.
- GST state codes — numeric. 27 = Maharashtra, 32 = Kerala, 07 = Delhi. Built into every GSTIN, used by tax software, ignored by everything else.
- ISO 3166-2:IN — IN-MH, IN-KL, IN-DL. Two-letter region code with the country prefix.
A few of these collide deceptively. AP is Andhra Pradesh in Census, but also Arunachal Pradesh — context-dependent. MP is Madhya Pradesh everywhere except in older British-era cartographic data where it sometimes meant something else. Ambiguity in two-letter codes without a country prefix is real, and it is the central reason ISO wins.
The table
A subset, to make the difference concrete:
- Maharashtra → Census
MH· GST27· ISOIN-MH - Kerala → Census
KL· GST32· ISOIN-KL - Delhi → Census
DL· GST07· ISOIN-DL - Tamil Nadu → Census
TN· GST33· ISOIN-TN - Uttar Pradesh → Census
UP· GST09· ISOIN-UP - Telangana → Census
TS· GST36· ISOIN-TS(until November 2023:IN-TG) - Andhra Pradesh → Census
AP· GST37· ISOIN-AP - Ladakh → Census
LA· GST38· ISOIN-LA - Jammu and Kashmir → Census
JK· GST01· ISOIN-JK
Note that ISO codes change. On 23 November 2023 ISO changed four
Indian codes: Telangana from IN-TG to IN-TS,
Odisha from IN-OR to IN-OD, Chhattisgarh from
IN-CT to IN-CG and Uttarakhand from
IN-UT to IN-UK. Data made before then uses the
old codes. If you mix the two without normalizing, those rows fall out
of the join.
The curly cases
State boundaries are not static. Two reorganizations in the last twelve years matter for any historical dataset.
Telangana split off from Andhra Pradesh in 2014. Hyderabad sits in Telangana now but served as joint capital for ten years. Pre-2014 records will assign Hyderabad to Andhra Pradesh; post that, Telangana. If your travel content predates the split, your state_code is wrong.
Ladakh became its own UT in 2019, separated from Jammu and
Kashmir. Leh and Kargil are now IN-LA, not
IN-JK. Most travel CMSes haven't been audited since.
Daman and Diu merged with Dadra and Nagar Haveli in 2020.
The combined UT has ISO code IN-DH; older data will still
list IN-DD or IN-DN separately.
Why our state_code column uses ISO
TravelMindsAI's state_code column on Indian cities holds
ISO 3166-2:IN codes. On 14 November 2026, 13,742 of the 13,762 Indian
city rows in our data carried one and 20 carried none; no numeric code
was left. Our data still
uses the ISO codes as they were before November 2023 for four states:
IN-TG for Telangana, IN-OR for Odisha,
IN-CT for Chhattisgarh and IN-UT for
Uttarakhand, in the city rows, in /v1/states/in and in the
state_code filter of /v1/heritage/in. If your
data uses the current codes (IN-TS, IN-OD,
IN-CG, IN-UK), map these four before you join.
Three reasons for ISO.
It joins cleanly across systems. Wikidata uses ISO
3166-2 as the canonical statement value for P300 (administrative
division). OpenStreetMap tags with ISO3166-2. Most
international travel datasets either use ISO or have an ISO column
available. Census codes work inside India and almost nowhere else.
It carries the country. IN-MH is
self-disambiguating. MH alone could be Maharashtra, the
Marshall Islands country code, or a US state in some legacy systems.
ISO maintains the boundary changes. When Ladakh
became IN-LA in 2019, the ISO Maintenance Agency
published the updated subdivision list within months. Census revisions
follow a slower, decade-aligned cadence.
GET /v1/cities does not return state_code;
the city context route (/v1/cities/{city_id}/context)
and the find_city tool do (for example, find_city
with Kovalam and IN answers "state_code": "IN-KL"). Where a city carries the ISO
form, joins to your tax data, your transit data and your GIS data work
without a translation table; for the rest, check the code before you
join.
If you're storing Indian states by Census abbreviation today, this is a decision worth revisiting before the next dataset import surprises you with three states quietly dropped on the floor.