The India Post Pincode Directory: A Practical Guide for Developers
All Indian logistics runs on one dataset: the India Post pincode directory — 165,000+ post offices collapsing into 19,000+ delivery pincodes. Here is how the system works, where to get the data, and why it goes stale fast.
Every serviceability check, every zone lookup, every "deliver by Thursday" promise in Indian ecommerce ultimately rests on a single public dataset: the India Post pincode directory. If you build logistics software for India, you will end up knowing it intimately — here is a head start.
How a PIN code is structured
The six digits are hierarchical:
- Digit 1 — postal region (e.g. 1 = Delhi/NW India, 5 = South, 7 = East)
- Digit 2 — sub-region / postal circle
- Digit 3 — sorting district
- Digits 4–6 — the individual post office within that district
So 560034: region 5 (South), circle 56 (Karnataka), district 560 (Bengaluru), office 034 (Agara).
Offices vs pincodes
The raw directory lists 165,000+ post offices — head offices (HO), sub offices (SO) and branch offices (BO). Multiple offices share one pincode, so for delivery purposes the dataset collapses to roughly 19,000 unique pincodes. Any usable pincode master must do this deduplication, typically preferring HO > SO > BO records for the canonical name and coordinates.
Where the data lives
The authoritative source is the Department of Posts dataset on data.gov.in, which includes office names, districts, states and (in current versions) latitude/longitude. It is free, official — and served through a rate-limited API that requires a registered key for bulk access.
Why pincode data goes stale
This is the trap: teams import a CSV once and consider the problem solved. But the directory is a living dataset —
- new pincodes appear as areas urbanise,
- offices are merged and retired,
- district and state mappings get corrected,
- coordinates improve over time.
A master that was perfect in January quietly accumulates wrong answers all year. Stale data means false "not serviceable" rejections (lost sales) and false positives (failed deliveries) — both expensive, both invisible until customers complain.
What a production-grade pincode master needs
- Nightly sync against the official directory, not annual imports. Postpin's sync runs at 00:30 IST daily and diffs new, updated and retired pincodes automatically.
- Deduplication logic from offices to delivery pincodes.
- Derived flags — metro classification, remote-area status — because raw India Post data does not carry courier semantics.
- Sync logs and rollback so a bad upstream batch cannot silently poison your data.
- An API in front so every consumer reads one source of truth:
GET /v1/pincodes/302021
{ "pincode": "302021", "city": "Jaipur", "state": "Rajasthan",
"zone_tier": "roi", "is_remote": false }Build vs buy
Building the pipeline is a fun weekend; operating it — key management, rate limits, retries, diffing, monitoring, rollback — is a permanent chore. If pincode data is not your product, an API that ships the maintained master (Postpin keeps 19,000+ pincodes with coordinates in nightly sync) is almost always cheaper than the engineering time.
Either way: respect the dataset. It is the quiet foundation of every parcel in the country.
Frequently asked questions
How many pincodes are there in India?
Roughly 19,000 unique delivery pincodes, derived from 165,000+ post offices in the official directory (many offices share a pincode). The exact count moves as India Post adds and retires codes through the year.
Where can I download the official pincode database?
The Department of Posts publishes it on data.gov.in, including office names, districts, states and coordinates. Bulk API access needs a registered (free) API key; the sample key is heavily rate-limited.
How often do Indian pincodes change?
Continuously, in small increments — new codes for urbanising areas, retirements, merges and mapping corrections. Individually rare, collectively significant: a year-old snapshot typically disagrees with the live directory on hundreds of entries.