Home / LatLongAPI and Reverse Geocoding API

LatLongAPI and Reverse Geocoding API

Explore how the LatLongAPI turns coordinates into address context, with reverse geocoding features, use cases, a request example, and response guidance.

What does the LatLongAPI do?

LatLongAPI accepts a position expressed in latitude and longitude and returns address information. Reverse geocoding is the operation that connects those coordinates to a readable place. A GPS point can tell your application where an event happened; an address helps a person recognize that location.

Use the same reverse geocoding endpoint whether your coordinates come from a device, a selected map pin, or a stored location event. This is a coordinate-to-address workflow, rather than an address search or a route calculation.

Features you can use in your application

Two address formats. Choose a short address for a compact label and a longer address for a detail view.
Separate location fields. Read city and country code without splitting an address string. These fields can be null when information is unavailable.
Request metadata. Use the request identifier and latency value to connect a lookup with your application's logs.
JSON integration. Send named coordinate fields in a POST request and read structured results from your backend.

Where reverse geocoding helps

Delivery and field-service support

When a driver or technician records a location, show an address beside the original coordinates. A support agent can recognize the area without manually finding every point on a map. Keep the captured coordinates available when an address is incomplete.

Map pins and saved places

Give a selected point a readable label, then show the longer address when someone opens its details. Keeping compact and detailed views separate avoids crowding the map with long strings.

Location-event review

Attach address context to an operational event so a reviewer can compare a place name with its recorded position. Check for missing city or country values before using those fields to group events.

LatLongAPI example: from a coordinate to an address

The following request uses the v1-dev test environment. Replace YOUR_TEST_LICENSE with a license issued for that environment and send the request from your backend. Keep the license out of browser code and source control.

curl --fail-with-body --max-time 10 \
  'https://v1-dev.latlongapi.com/api/v1/reverse' \
  -H 'Content-Type: application/json' \
  --data '{
    "lat": 51.5007,
    "long": -0.1246,
    "api": "YOUR_TEST_LICENSE"
  }'

This response excerpt shows address fields for the same coordinates. Address values depend on available map data; the API also returns request metadata under meta.

{
  "result": {
    "short_address": "Big Ben, Bridge Street, City of Westminster, UK",
    "long_address": "Big Ben, Bridge Street, Westminster, Millbank, City of Westminster, SW1A 2JR, United Kingdom",
    "city": "City of Westminster",
    "country_code": "UK",
    "precision": 10
  }
}

For a map pin, display result.short_address. For a support detail panel, display result.long_address alongside the original coordinates. Keep a coordinate-only fallback when the lookup returns no usable address.

Benefits for your workflow

Readable labels reduce the need to interpret raw coordinate pairs during routine work. Separate response fields let your interface select the information it needs without parsing display text. Request metadata gives your team a way to investigate an individual lookup.

Evaluate coverage with representative locations before relying on an address in a production workflow. Discuss edge or BYOC deployment when location processing needs to run at your own cloud.

Choose your next step

Use the API documentation for field limits, authentication, and error handling. Compare capacity and deployment options on the pricing page, or try the homepage demo.