---
title: "`GET /geocode/reverse?lon=<f64>&lat=<f64>[&kinds=..&categories=..&name=..&radius_m=..&limit=..]`."
method: GET
path: "/geocode/reverse"
tags: ["geocoding"]
---

# \`GET /geocode/reverse?lon=<f64>&lat=<f64>\[&kinds=..&categories=..&name=..&radius_m=..&limit=..\]\`.

`GET /geocode/reverse`

## Request

- Base URL: `https://api.mapmap.ai`
- URL: `https://api.mapmap.ai/geocode/reverse`
- Auth: one of:
  - HTTP bearer
  - API key in query parameter `api_key`

## Query parameters

- `lon` number, double, required
- `lat` number, double, required
- `kinds` string
- `categories` string
- `name` string
- `radius_m` integer
- `limit` integer

## Response `200`

Photon-compatible GeoJSON FeatureCollection. First-party hits add `distance_m`, a stable `id`, and a `details` object on POI hits (whitelisted OSM display tags); the Photon proxy path passes the upstream body through verbatim

- object

## Other responses

- `400`: Missing or malformed `lon`/`lat`, or a malformed `kinds`/`categories`/`name`/`radius_m`/`limit`
- `401`: Missing or invalid API key
- `429`: Quota or rate limit exceeded
- `501`: Geocoding not enabled (neither SN_GEOCODE_DIR nor SN_PHOTON_URL set), or `categories`/`name`/`radius_m` on a Photon-proxy deployment (`urn:sn-gateway:problem:reverse-filtering-not-enabled`; clients feature-detect on this status)
- `502`: Photon upstream failed

---

[API](https://skmtc.dev/mapmap/apis/sn-gateway.md) · [All operations](https://skmtc.dev/mapmap/apis/sn-gateway/llms.txt) · [OpenAPI document](https://skmtc.dev/mapmap/apis/sn-gateway/revisions/2293be8b4c38?raw)