Developer API

Pincode API

The Pincode API controller catalogue describes the main endpoint as fetching Post Office details based on Country and Pin Code. It can be used to enrich address forms, validate postal context or look up service-area information from another application.

Capabilities

What this API is designed to do

Pincode API for fetching post-office details from country and postal-code input.

Look up post-office details by country and pincode
Use a single API-key-controlled endpoint
Apply subscription quotas and whitelist restrictions
Integrate lookup results into forms or address workflows
Use cases

Where it can fit

These are common integration scenarios; the exact implementation depends on your application, data-handling requirements and subscription tier.

Address-entry assistance
Postal and service-area validation
CRM or order workflows that need post-office context
Location-data enrichment during onboarding
Endpoint catalogue

Published routes and methods

The endpoint list below is read from the existing API controller catalogue. Website Management can explain the API, but it cannot invent or replace live endpoint routes.

MethodRoutePurpose
ANY/pincodeMain API to fetch Post Office details based on Country and Pin Code
Integration reference

Authentication, request shape and response handling

These examples are presentation content managed by Website Management. Always compare them with the live API documentation and endpoint catalogue before production integration.

Authentication & access

Use Authorization: Bearer YOUR_API_KEY or X-API-Key. country uses a supported two-letter country code; pin is the postal code or, for India, can also be a post-office search value.

Example request
curl -X GET "https://api.sinhcoms.com/pincode?country=IN&pin=110001" 
  -H "Authorization: Bearer YOUR_API_KEY"
Example response
The endpoint returns the postal-provider JSON response. For India it uses the configured India postal lookup; supported non-IN countries use the configured Zippopotam lookup.
Error handling

Documented error states

400pin is missing
401API key authentication or product authorization failed
429Daily request limit exceeded
Provider errorPostal provider did not return a usable result
Integration flow

From subscription to first request

Use the customer dashboard as the control point for keys, whitelist rules and plan limits.

01

Choose a Pincode API plan

02

Create or assign an API key

03

Call the published /pincode endpoint with the expected country and pin-code values

04

Validate response data before applying it to business logic

05

Monitor usage from the API dashboard

Plans

Choose the request capacity you need

Pricing and limits below are read from the active subscription tiers in the API system.

Star

INR 499.00/month

  • 100,000 requests/day
  • 3,000,000 requests/month
Integration notes

Before you go live

Postal data can change. Applications should handle missing or multiple records gracefully instead of assuming a single permanent result.