Reverse Geocoding API
Look up the nearest address, neighborhood, and city for any lat/lng pair
How it works
Send coordinates
Pass a latitude and longitude pair.
Plaza resolves it
Finds the nearest addressable feature in OpenStreetMap.
Get an address
Street, city, postal code, country — structured and normalized.
See it in action
An example request and its response, drawn on the map.
Who uses this
Teams building with Reverse Geocoding API.
Mobile apps
Show the user's current location as a readable address.
Map interactions
Display address details when users click on a map.
Data enrichment
Add address context to coordinate-only datasets.
Start building
curl -X POST "https://plaza.fyi/api/v1/geocode/reverse" \
-H "X-API-Key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"geometry": {
"coordinates": [
-77.0365,
38.8977
],
"type": "Point"
}
}'
View endpoints
| Method | Path | Description |
|---|---|---|
| POST | /api/v1/geocode/reverse | Reverse geocode coordinates to a structured address |
| POST | /api/v1/geocode/reverse/batch | Reverse geocode up to 1,000 coordinates in one request |
How it compares
Common questions
What fields are in a reverse geocode response?
Street address, city, state/province, postal code, country, and the source OSM element ID. Responses are structured and normalized regardless of country.
Can I batch reverse geocode requests?
Yes. POST up to 1,000 points to /api/v1/geocode/reverse/batch (PlazaQL: reverse_geocode(points: [...])) and you get one result list per point, in the order you sent them. A point with nothing nearby gets an empty list. Each point counts as one request toward your plan, and the batch as one call against the per-minute rate limit.
How close does the coordinate need to be?
The API finds the nearest addressable feature to your coordinate. A point within a few hundred meters of a building will return a useful address in most cases.