Reverse Geocode API

Translate raw geographic coordinates into structured, human-readable street addresses, administrative zones, and postal codes in real time.

Where it's used

Use cases, value and how it works

Overview & Solution

Connected devices, mobile apps, and IoT hardware report numeric coordinates (latitude, longitude) that are meaningless to human operators and end customers. The Reverse Geocode API bridges this gap by looking up the nearest road segments, building structures, and regional boundaries to deliver a clear, formatted address.

Industry Use Cases

1. Ride-Hailing & On-Demand Services

• Automated Pickup Location: Instantly display the user's current street and building name when opening the app, eliminating the need to type addresses manually.
• Drop-off Point Identification: Clarify destination landmarks for drivers.

2. Fleet & Asset Tracking

• Live Location Reporting: Translate vehicle telematics into human-readable locations on operations control room dashboards (e.g., "Vehicle #42 parked at Andheri MIDC, Mumbai").
• Incident & Emergency Response: Rapidly communicate accident or breakdown locations to nearest recovery and police units.

3. Field Force Management

• Automated Attendance Check-In: Verify where a sales executive or service technician checked in by converting GPS pings to verifiable client offices or dealer stores.

Key Benefits

• Hierarchical Address Breakdown: Returns street, building, sub-locality, city, district, state, and postal code.

API reference

Location and Address Intelligence APIs · API key only

Quick try

curl

curl -X POST 'https://api-gw.sovereignsolutions.com/gateway/geocode/reverse?api-key=$API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{"longitude": 77.06615, "latitude": 28.462238}'

Convert coordinates into a structured address

POST https://api-gw.sovereignsolutions.com/gateway/geocode/reverse

Auth: api-key query parameter only - no bearer token, no tenant in the URL

Request parameters

Parameter	In	Type	Required	Description
longitude	body	number	-	Longitude of the point, decimal degrees.
latitude	body	number	-	Latitude of the point, decimal degrees.

Request body

{
  "longitude": 77.06615,
  "latitude": 28.462238
}

Response

200 OK

[
  {
    "Country": "India",
    "District": "Gurugram",
    "PinCode": {
      "OfficeName": "Industrial Estate (Gurgaon)",
      "OfficeType": "S.O",
      "Value": "122007"
    },
    "Road": "",
    "State": "HARYANA",
    "Status": true,
    "Tehsil": "Gurgaon",
    "Village": ""
  }
]

Response fields (12)

Field	Type	Description
[]	object	One address per input point.
[].Country	string	Country.
[].District	string	District.
[].PinCode	object
[].PinCode.OfficeName	string	Post office name.
[].PinCode.OfficeType	string	Post office type, e.g. S.O (sub office).
[].PinCode.Value	string	Postal code (PIN).
[].Road	string	Nearest road name. Empty when none is known.
[].State	string	State.
[].Status	boolean	true when an address was found.
[].Tehsil	string	Tehsil (sub-district).
[].Village	string	Village. Empty when the point is not in a village.

The response is an array even for a single point. To look up several points in one call, see Batch Reverse Geocoding.

Errors: non-2xx responses use the standard status codes listed on Errors.