---
title: US Reverse Location Lookup API
slug: reverse-location-lookup
url: https://apyhub.com/dosvak/service/reverse-location-lookup
provider: Dosvak LLC
categories: [Geolocation, Travel]
tags: [reverse-geocoding, geolocation, coordinates, maps, place-lookup]
auth: api_key
version: 0.1.0
service_type: sync
endpoints: 1
atoms: 100
mcp: true
---

# US Reverse Location Lookup API

Reverse geocode latitude and longitude with an optional search radius. Returns a flexible JSON result for map, delivery, and GPS workflows.

## Endpoints

| Method | URL | Description | Atoms |
| --- | --- | --- | --- |
| GET | `https://api.eu.apyhub.com/dosvak/reverse-location-lookup` | What it does Performs a reverse location lookup using latitude and longitude passed as query parame… | 100 |

## Endpoint reference

### Reverse location lookup

`GET https://api.eu.apyhub.com/dosvak/reverse-location-lookup` · 100 atoms · accepts `application/json` · returns `application/json`

| Parameter | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `lat` | query | number | yes | Lat Example: `34.0522`. |
| `lon` | query | number | yes | Lon Example: `-118.2437`. |
| `radius_m` | query | integer | no | Radius M Default: `1000`. Example: `1500`. |

#### Quickstart

Look up the nearest location for a latitude/longitude pair.

```bash
curl -X GET "https://api.eu.apyhub.com/dosvak/reverse-location-lookup?lat=34.0522&lon=-118.2437&radius_m=2000" \
  -H "apy-token: $APY_TOKEN"
```

#### What you'll get back

Returns a JSON object. The schema allows additional top-level fields, so the exact response shape may vary.

```json
{
  "input": {
    "lat": 34.0522,
    "lon": -118.2437,
    "radius_m": 1000
  },
  "feature": {
    "osm_id": 4253186548,
    "name": "Ronald F. Deaton Civic Auditorium",
    "category": "events_venue",
    "lat": 34.05206589960343,
    "lon": -118.2438373,
    "distance_m": 23.62699806699978,
    "source": "point"
  },
  "attribution": [
    {
      "source": "OpenStreetMap contributors",
      "dataset": "OpenStreetMap feature and geometry data",
      "license": "ODbL 1.0",
      "url": "https://www.openstreetmap.org/copyright",
      "notice": "Contains information from OpenStreetMap and its contributors, available under the Open Database License."
    }
  ]
}
```

## About

## What it does
Reverse Location Lookup turns latitude and longitude into a location-aware lookup result. Send `lat` and `lon`, and optionally a `radius_m` up to 50,000, to query nearby place or address data around a point on the map.

Use Reverse Location Lookup when you need to attach context to coordinates, such as identifying where a mobile event occurred, enriching a delivery pin, or resolving a GPS reading in a support or logistics workflow. The request is simple: two required query parameters for the coordinate pair, plus an optional search radius in meters with a default of 1,000.

The response is returned as a JSON object with flexible structure, so you can integrate it into your own location-processing pipeline without assuming a fixed field set. That makes it a good fit for applications that need reverse-geocoding-style results while keeping the output adaptable to the source data returned by the service.

## Usage

Base URL: `https://api.eu.apyhub.com` (default region — see
`GET https://apyhub.com/api/public/regions` for the rest).

Authenticate with an ApyHub API key in the `apy-token` header.
Full docs and a live playground: https://apyhub.com/dosvak/service/reverse-location-lookup