Look up any Indian PIN code and every post office under it.
India Pincode Lookup is an Indian PIN code API covering all ~19,300 PIN codes and ~157,000 post offices. Look up a PIN code to get its district, state, ISO state code, India Post circle, region, division and post office count, or search by post office, district or state, while paid plans add coordinates, every post office with its type and delivery status, and nearby PIN codes by distance.
Try it — live request, no key required
No key required to try it. Get a key to use it in your app.
{
"status": "ok",
"error": null,
"data": {
"count": 1,
"totalMatches": 1,
"results": [
{
"pincode": "560001",
"district": "Bengaluru Urban",
"state": "Karnataka",
"stateCode": "KA",
"circle": "Karnataka Circle",
"region": "Bengaluru HQ Region",
"division": "BANGALORE GPO DIVISION",
"latitude": 12.98247,
"longitude": 77.59456,
"timezone": "Asia/Kolkata",
"postOfficeCount": 10,
"deliveryOfficeCount": 1,
"postOffices": [
{
"name": "Bengaluru G.P.O.",
"officeType": "head_office",
"delivery": true,
"latitude": 12.9716,
"longitude": 77.59456
},
{
"name": "Bengaluru Foreign Post S.O",
"officeType": "sub_office",
"delivery": false,
"latitude": 13.03,
"longitude": 77.6007
},
{
"name": "CMM Court Complex S.O",
"officeType": "sub_office",
"delivery": false,
"latitude": 12.97949,
"longitude": 77.59418
},
{
"name": "Dr. Ambedkar Veedhi S.O",
"officeType": "sub_office",
"delivery": false,
"latitude": 12.98114,
"longitude": 77.59536
},
{
"name": "HighCourt S.O",
"officeType": "sub_office",
"delivery": false,
"latitude": 12.96842,
"longitude": 77.56919
},
{
"name": "Legislators Home S.O",
"officeType": "sub_office",
"delivery": false,
"latitude": 12.98386,
"longitude": 77.58961
},
{
"name": "Mahatma Gandhi Road S.O",
"officeType": "sub_office",
"delivery": false,
"latitude": 12.16103,
"longitude": 78.00022
},
{
"name": "Rajbhavan S.O",
"officeType": "sub_office",
"delivery": false,
"latitude": 12.98247,
"longitude": 77.5913
},
{
"name": "Vasanthanagar S.O",
"officeType": "sub_office",
"delivery": false,
"latitude": 12.99351,
"longitude": 77.5921
},
{
"name": "Vidhana Soudha S.O",
"officeType": "sub_office",
"delivery": false,
"latitude": 12.98747,
"longitude": 77.60475
}
],
"nearby": [
{
"pincode": "560009",
"district": "Bengaluru Urban",
"state": "Karnataka",
"distanceKm": 1.57
},
{
"pincode": "560042",
"district": "Bengaluru Urban",
"state": "Karnataka",
"distanceKm": 1.93
}
]
}
]
}
}
About the India Pincode Lookup API
A pincode lookup API built from the All India Pincode Directory published by the Department of Posts, Government of India. One call returns the full picture for a PIN code: district and state with its ISO 3166-2:IN code, the India Post circle, region and division, a coordinate taken as the median of its offices, and every post office under the PIN marked as head, sub or branch office with its delivery status and own coordinates. Reverse lookups find PIN codes by post office name, district or state. The coordinates and the post office list are on paid plans, as is nearby=true, which lists the PIN codes within a radius of up to 50 km, nearest first.
What people use it for
- Checkout Address Autofill
- Fill district and state as soon as a shopper types a 6-digit PIN code, and reject PIN codes that do not exist.
- Delivery Serviceability
- Check whether a PIN code has a delivery post office and list nearby PIN codes for courier zone planning.
- Address Cleaning
- Standardise district and state names and attach ISO state codes to customer records.
- Store and Agent Locators
- Find the PIN codes around a branch to define its catchment area.
Ways to call it
One endpoint, many ways in — REST with JSON, XML, YAML and CSV, plus GraphQL and an MCP interface for AI agents.
- JSON
- Default REST response
- XML
- Markup format
- YAML
- Human-readable
- CSV
- Tabular export
- GraphQL
- Query language
- MCP
- For AI agents
Other ways to use India Pincode Lookup
Same data, same APIVerve account, same credit balance — one key works on all of them.
How complete is the directory?
What does the Free plan include?
How accurate are the coordinates?
Why does a PIN code return several post offices?
How many credits does a lookup use?
Request parameters — GET /v1/indiapincode
Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them. Anything not listed here is dropped rather than passed through.
Optional
| Parameter | Type | Example | Description |
|---|---|---|---|
pincodeOptional | string | 110001 | Six-digit PIN code |
officeOptional | string | Connaught Place | Post office name or part of it length 0-100 |
districtOptional | string | Pune | District name length 0-80 |
stateOptional | string | Maharashtra | State or union territory name length 0-80 |
nearbyOptionalPremium | boolean | true | With pincode, include the PIN codes within radius km default false |
radiusOptional | number | 10 | Radius in km for nearby (1-50) default 10 · range 1-50 |
limitOptional | integer | 10 | Maximum PIN codes to return for searches (1-50) default 10 · range 1-50 |
curl "https://api.apiverve.com/v1/indiapincode?pincode=110001&office=Connaught%20Place&district=Pune&state=Maharashtra&nearby=true&radius=10&limit=10" \
-H "x-api-key: YOUR_API_KEY"Authentication
Send your key in the x-api-key header. That is the only auth step — no token exchange, and no per-endpoint scope to configure.
| Header | When | Value |
|---|---|---|
x-api-keyRequired | Every request | Your API key. Header names are case-insensitive, so X-API-Key is the same header. |
AuthorizationAlternate | Instead of the above | Bearer <key> — for clients that only expose bearer auth. Resolves to the same account and the same billing. |
A 401 means the key is missing, invalid or expired. A 403 means the key is valid but not permitted here — blocked by a key restriction or an IP allow-list. Running out of credits is a 429.
Response — GET /v1/indiapincode
Every APIVerve endpoint returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape.
{
"status": "ok",
"error": null,
"data": {
"count": 1,
"totalMatches": 1,
"results": [
{
"pincode": "560001",
"district": "Bengaluru Urban",
"state": "Karnataka",
"stateCode": "KA",
"circle": "Karnataka Circle",
"region": "Bengaluru HQ Region",
"division": "BANGALORE GPO DIVISION",
"latitude": 12.98247,
"longitude": 77.59456,
"timezone": "Asia/Kolkata",
"postOfficeCount": 10,
"deliveryOfficeCount": 1,
"postOffices": [
{
"name": "Bengaluru G.P.O.",
"officeType": "head_office",
"delivery": true,
"latitude": 12.9716,
"longitude": 77.59456
},
{
"name": "Bengaluru Foreign Post S.O",
"officeType": "sub_office",
"delivery": false,
"latitude": 13.03,
"longitude": 77.6007
},
{
"name": "CMM Court Complex S.O",
"officeType": "sub_office",
"delivery": false,
"latitude": 12.97949,
"longitude": 77.59418
},
{
"name": "Dr. Ambedkar Veedhi S.O",
"officeType": "sub_office",
"delivery": false,
"latitude": 12.98114,
"longitude": 77.59536
},
{
"name": "HighCourt S.O",
"officeType": "sub_office",
"delivery": false,
"latitude": 12.96842,
"longitude": 77.56919
},
{
"name": "Legislators Home S.O",
"officeType": "sub_office",
"delivery": false,
"latitude": 12.98386,
"longitude": 77.58961
},
{
"name": "Mahatma Gandhi Road S.O",
"officeType": "sub_office",
"delivery": false,
"latitude": 12.16103,
"longitude": 78.00022
},
{
"name": "Rajbhavan S.O",
"officeType": "sub_office",
"delivery": false,
"latitude": 12.98247,
"longitude": 77.5913
},
{
"name": "Vasanthanagar S.O",
"officeType": "sub_office",
"delivery": false,
"latitude": 12.99351,
"longitude": 77.5921
},
{
"name": "Vidhana Soudha S.O",
"officeType": "sub_office",
"delivery": false,
"latitude": 12.98747,
"longitude": 77.60475
}
],
"nearby": [
{
"pincode": "560009",
"district": "Bengaluru Urban",
"state": "Karnataka",
"distanceKm": 1.57
},
{
"pincode": "560042",
"district": "Bengaluru Urban",
"state": "Karnataka",
"distanceKm": 1.93
}
]
}
]
}
}
Response fields
Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.
| Field | Type | Example | Description |
|---|---|---|---|
count | number | 1 | Number of PIN codes returned |
totalMatches | number | 1 | Number of PIN codes that matched before the limit |
results | array[1] | ||
pincode | string | "560001" | Six-digit Indian postal index number |
district | string | "Bengaluru Urban" | District |
state | string | "Karnataka" | State or union territory |
stateCode | string | "KA" | ISO 3166-2:IN subdivision code, e.g. KA |
circle | string | "Karnataka Circle" | India Post circle |
region | string | "Bengaluru HQ Region" | India Post region; null where the division reports straight to the circle |
division | string | "BANGALORE GPO DIVISION" | India Post division |
latitudePremium | number | 12.98247 | Latitude of the PIN: the median of its post offices' coordinates |
longitudePremium | number | 77.59456 | Longitude of the PIN |
timezone | string | "Asia/Kolkata" | IANA time zone (Asia/Kolkata) |
postOfficeCount | number | 10 | Number of post offices under the PIN |
deliveryOfficeCount | number | 1 | Number of those offices that deliver mail |
postOfficesPremium | array[10] | Every post office under the PIN, head office first | |
namePremium | string | "Bengaluru G.P.O." | Post office name |
officeTypePremium | string | "head_office" | head_office, sub_office or branch_office |
deliveryPremium | boolean | true | The office delivers mail |
latitudePremium | number | 12.9716 | Latitude of the office; null when the directory gives none or an implausible one |
longitudePremium | number | 77.59456 | Longitude of the office |
nearbyPremium | array[2] | PINs within radius km (nearby=true): pincode, district, state, distanceKm | |
pincodePremium | string | "560009" | |
districtPremium | string | "Bengaluru Urban" | |
statePremium | string | "Karnataka" | |
distanceKmPremium | number | 1.57 |
Response headers
Every response carries your balance, so your own code always knows where it stands without polling anything. All four are exposed to browsers through CORS.
| Header | What it carries |
|---|---|
x-api-remaining-credits | Credits left in the current cycle |
x-api-credits-used | Credits spent in the current cycle |
x-api-max-credits | The allowance for the cycle |
x-api-version | Version of the endpoint that answered |
Errors
Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.
| Status | Meaning | What to do |
|---|---|---|
400 | Input was rejected | Read error; it names the parameter that has to change. |
401 | Key missing or invalid | Check the header name and the key value. |
403 | Key valid, but not permitted here | A key restriction or an IP allow-list — never a bad key. |
429 | Rate limited, or out of credits | Read error to tell them apart, then back off or top up. |
What a call costs — 2 credits per call
Credits are shared across every APIVerve API — one balance, one key, one bill. Failed requests never count against it, so a rejected input costs nothing.
| Plan | Per month | Credits | India Pincode Lookup calls | Per 1,000 calls |
|---|---|---|---|---|
| Free | Free | 200 | 100 | Free |
| Starter | $29.99 | 200,000 | 100,000 | $0.30 |
| Pro | $99.99 | 1,000,000 | 500,000 | $0.20 |
| Mega | $299.99 | 4,000,000 | 2,000,000 | $0.15 |
Calls are what the credits buy at this API's rate — spend them here, on any of the other APIs, or across both. Nothing is reserved per endpoint.
Call it from cURL — GET /v1/indiapincode
No SDK to install — this is a plain HTTPS call to /v1/indiapincode with your key in the x-api-key header. Swap in a real key and it runs as-is.
curl "https://api.apiverve.com/v1/indiapincode" \
-H "x-api-key: YOUR_API_KEY"Resources
Call it from Node.js — GET /v1/indiapincode
No SDK to install — this is a plain HTTPS call to /v1/indiapincode with your key in the x-api-key header. Swap in a real key and it runs as-is.
const res = await fetch("https://api.apiverve.com/v1/indiapincode", {
headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);Resources
Call it from Python — GET /v1/indiapincode
No SDK to install — this is a plain HTTPS call to /v1/indiapincode with your key in the x-api-key header. Swap in a real key and it runs as-is.
import requests
res = requests.get(
"https://api.apiverve.com/v1/indiapincode",
headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])Resources
Call it from C# / .NET — GET /v1/indiapincode
No SDK to install — this is a plain HTTPS call to /v1/indiapincode with your key in the x-api-key header. Swap in a real key and it runs as-is.
using var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");
var json = await client.GetStringAsync("https://api.apiverve.com/v1/indiapincode");
Console.WriteLine(json);Resources
Call it from Go — GET /v1/indiapincode
No SDK to install — this is a plain HTTPS call to /v1/indiapincode with your key in the x-api-key header. Swap in a real key and it runs as-is.
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/indiapincode", nil)
req.Header.Set("x-api-key", "YOUR_API_KEY")
res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))Resources
Call it from PHP — GET /v1/indiapincode
No SDK to install — this is a plain HTTPS call to /v1/indiapincode with your key in the x-api-key header. Swap in a real key and it runs as-is.
$ch = curl_init("https://api.apiverve.com/v1/indiapincode");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-api-key: YOUR_API_KEY"]);
$response = curl_exec($ch);
echo $response;Resources
Call it from Ruby — GET /v1/indiapincode
No SDK to install — this is a plain HTTPS call to /v1/indiapincode with your key in the x-api-key header. Swap in a real key and it runs as-is.
require "net/http"
uri = URI("https://api.apiverve.com/v1/indiapincode")
req = Net::HTTP::Get.new(uri)
req["x-api-key"] = "YOUR_API_KEY"
res = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) { |h| h.request(req) }
puts res.bodyResources
Zero-code embed — one snippet, no backend
Drop an interactive India Pincode Lookup form onto any page. The widget calls the API for you, so no key ever appears in your markup and there is nothing to deploy.
Changelog — India Pincode Lookup API
Every change to this endpoint, newest first. Breaking changes ship as a new version and the previous one keeps serving — response fields are added, never removed or retyped in place, so an integration written against v1 keeps working.
Entries are picked up from dated catalog snapshots, so the first one appears after the next snapshot that moves something. A period where nothing changed produces no entry — silence is a valid changelog for the India Pincode Lookup API.
Geography
- Cities Lookup
- Coordinates Are Sea
- Country Borders
- Country Boundaries
- Country Flags
- Country Languages
- Country Lookup
- County Data Lookup
- Distance Calculator
- India Pincode Lookup
- Reverse Geocode
- State Boundaries
- USDA Hardiness Zone
- Zip Codes Lookup