Validate Indian Postcodes API

Hosted on ApyHub

What it does

Validate India Postcode Validator checks whether a postcode exists in its lookup table. Send a postcode string in the request body; spaces are ignored for matching.

The response is intentionally simple: you get back a boolean data value. true means the postcode was found, and false means it was not. That makes it easy to gate checkout forms, address entry flows, or import pipelines without having to parse a larger location payload.

Use it when you need a fast existence check for Indian PIN codes and want to avoid accepting obviously invalid entries. It fits well in signup forms, shipping validation, CRM data cleanup, and any workflow where postcode correctness matters before you move on to deeper address handling.

POST

Validate India pin code

http://localhost:8080/apyhub/validate-indian-postcode

QUICKSTARTGUIDE

Quickstart

Check whether a postcode or PIN code exists in the lookup table.

curl -X POST "http://localhost:8080/apyhub/validate-indian-postcode" \
  -H "apy-token: $APY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"postcode":"YO17 6DU"}'

What you'll get back

Returns a JSON object with a data boolean field — true when the postcode exists in the lookup table, false otherwise.

{
  "data": true
}

TRY ITLIVE · 10 ATOMS

API key

Loading your default key…

The full key is used to call the gateway and stays in this tab — never sent to orbit or saved.

About this endpoint

What it does

Validates an Indian PIN code by sending a postcode string in the request body and returning a boolean result. The response indicates whether the postcode exists in the lookup table.

Request Body

Parameter	Type	Mandatory	Description
postcode	String	Yes	Postcode or PIN code; spaces are ignored for matching.

Response

Returns a JSON object with a data boolean field. true when the postcode exists in the lookup table, false otherwise.

Parameter	Type	Mandatory	Description
data	Boolean	Yes	`true` when the postcode exists in the lookup table.

Body

Name

Type

Description

bodyREQUIRED

object

—

▣ COMMON ERRORS

Errors any endpoint can return

400bad_request

Required parameter missing or malformed body.

401unauthorized

API key missing, revoked, or not authorized for this service.

429rate_limited

Your plan's per-second rate exceeded. Retry with exponential backoff.

503upstream_busy

Backend temporarily unavailable. Try again in a few seconds.