Reverse geocoding API

Reverse geocoding API
for GPS records.

Turn GPS records into readable locations for fleet logs, delivery events and field-service apps. Send a latitude and longitude to get the nearest house, street or locality, with its distance from your point.

50,000 free credits a month. One credit per successful lookup.

cURL
curl 'https://api.opengeocoding.com/v1/reverse' \
  -H 'x-api-key: YOUR_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{"lat":55.676,"lon":12.568,"radiusM":500,"size":1}'
Response
{
  "results": [
    {
      "address": {
        "displayName": "Example nearby address",
        "geoCoordinates": {
          "lat": 55.6761,
          "lon": 12.5683
        }
      },
      "distanceM": 22,
      "layer": "address"
    }
  ]
}

Built for GPS points, not just map clicks.

Nearest first, with a distance

Ask for one result or several within a radius. Each carries its distance in metres from your point.

Graceful fallback

No house in range? You get the street. No street either? The nearest locality within about 50 km. The layer field says which.

ISO 3166-2 regions

Results carry ISO 3166-2 region codes, and a separate region lookup maps any point to its administrative regions.

Keep the answers

Store reverse-geocoded addresses next to your GPS data with no deletion deadline, subject to the data licences.

Label fleet and delivery records

Turn device locations, delivery scans or photo coordinates into a street address people can read.

Add context to field-service reports

Attach a readable location to technician check-ins and job reports while keeping the original GPS point.

Group by region

Need only the state or province? Resolve regions returns the ISO 3166-2 regions for a point.

Reverse geocoding in a production workflow.

  1. 1. Keep the original GPS record

    Store the source coordinates and your event or record ID. A nearby address adds context; it does not correct the GPS measurement or prove that an event happened at that address.

  2. 2. Check distance and result layer

    Inspect distanceM and layer before treating a result as a house-level address. A street or locality fallback is useful context, not an exact address. See the reverse response fields.

  3. 3. Save completed records

    Save each label with your record ID so a restarted worker can skip completed records. Pace calls to your account rate limit and follow Retry-After on rate-limit 429 responses. An exhausted credit balance also returns 429; retries do not restore credits. Use the error and retry reference to handle temporary failures.

Reverse geocode your first point.

Need coordinates for an address instead? Use the same key for forward geocoding API or geocode an address CSV.