POSTReverse Geocoding

Convert latitude and longitude coordinates into structured Indian address data including locality, city, state, PIN code, and country.

POST/tools/kyc/reverse-geocoding

The Reverse Geocoding API translates GPS coordinates into a human-readable, structured address. It is designed for address validation during onboarding, geo-compliance checks, field-agent location verification, and location-based fraud detection workflows. Pass a latitude/longitude pair and receive a normalised address broken down by locality, city, district, state, PIN code, and country — along with a confidence score.

Body parameters

Field	Type	Required	Description
`initiator_id`	string	required	Registered mobile number of the API user (see Platform Credentials).e.g. 9962981729
`user_code`	string	required	User code of the retailer/agent the service is run for.e.g. 20810200
`client_ref_id`	string	optional	Unique reference id per API call, generated by your system.e.g. REQ-20260101-001
`latitude`	string	required	Geolocation latitude of the point to resolve (decimal degrees).e.g. 19.0760
`longitude`	string	required	Geolocation longitude of the point to resolve (decimal degrees).e.g. 72.8777

initiator_idstringRequired

Registered mobile number of the API user (see Platform Credentials).

example: 9962981729

user_codestringRequired

User code of the retailer/agent the service is run for.

example: 20810200

client_ref_idstringoptional

Unique reference id per API call, generated by your system.

example: REQ-20260101-001

latitudestringRequired

Geolocation latitude of the point to resolve (decimal degrees).

example: 19.0760

longitudestringRequired

Geolocation longitude of the point to resolve (decimal degrees).

example: 72.8777

Headers

Field	Type	Required	Description
`developer_key`	string	required	Static API key issued to your account after KYC.
`secret-key`	string	required	Dynamic per-request signature: base64(HMAC-SHA256(timestamp, base64(access_key))).
`secret-key-timestamp`	string	required	Current time in milliseconds since UNIX epoch, used to compute secret-key. Must match server time.
`content-type`	string	required	application/jsone.g. application/json

developer_keystringRequired

Static API key issued to your account after KYC.

secret-keystringRequired

Dynamic per-request signature: base64(HMAC-SHA256(timestamp, base64(access_key))).

secret-key-timestampstringRequired

Current time in milliseconds since UNIX epoch, used to compute secret-key. Must match server time.

content-typestringRequired

application/json

example: application/json

Responses

statusnumber
Primary success indicator (0 = success).
messagestring
Human-readable response / error message.
response_status_idnumber
Granular status id; see the shared error-codes table.
response_type_idnumber
A unique id for every possible response shape (success or error) — useful for client logic branching and analytics.
dataobject
API-specific response payload.
- latitudestring
  Echo of the latitude coordinate supplied in the request.
- longitudestring
  Echo of the longitude coordinate supplied in the request.
- addressstring
  Full formatted street address resolved from the coordinates.
- citystring
  City name derived from the coordinates.
- statestring
  Full state name derived from the coordinates.
- statecodestring
  Two-letter ISO / RTO state code.
- countrycodestring
  Two-letter ISO 3166-1 alpha-2 country code.
- pincodestring
  Indian 6-digit PIN code for the resolved location.
- scorenumber
  Geocoding confidence score between 0 and 1; higher values indicate a more precise address match.
- statusstring
  Status of the coordinate resolution (e.g. 'OK').