Reverse Geocode API
Overview
To use Reverse Geocode, you need an API key. You can get one by creating a free account and visiting your dashboard.
GET Endpoint
https://api.apiverve.com/v1/reversegeocodeExample
How to call the Reverse Geocode API in different programming languages.
curl -X GET \
"https://api.apiverve.com/v1/reversegeocode?lat=40.714224&lon=-73.961452" \
-H "X-API-Key: your_api_key_here"const response = await fetch('https://api.apiverve.com/v1/reversegeocode?lat=40.714224&lon=-73.961452', {
method: 'GET',
headers: {
'X-API-Key': 'your_api_key_here',
'Content-Type': 'application/json'
}
});
const data = await response.json();
console.log(data);import requests
headers = {
'X-API-Key': 'your_api_key_here',
'Content-Type': 'application/json'
}
response = requests.get('https://api.apiverve.com/v1/reversegeocode?lat=40.714224&lon=-73.961452', headers=headers)
data = response.json()
print(data)package main
import (
"fmt"
"io"
"net/http"
)
func main() {
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/reversegeocode?lat=40.714224&lon=-73.961452", nil)
req.Header.Set("X-API-Key", "your_api_key_here")
req.Header.Set("Content-Type", "application/json")
client := &http.Client{}
resp, err := client.Do(req)
if err != nil {
panic(err)
}
defer resp.Body.Close()
body, _ := io.ReadAll(resp.Body)
fmt.Println(string(body))
}{
"status": "ok",
"error": null,
"data": {
"zipcode": "11211",
"state_abbr": "NY",
"city": "Brooklyn",
"state": "New York",
"distance": 0.6501757300758664,
"latitudeClosest": "40.712090",
"longitudeClosest": "-73.95427",
"countryCode": "US",
"latitude": 40.714224,
"longitude": -73.961452,
"estimatedCity": true,
"nearestCities": [
"Brooklyn",
"Brooklyn Park",
"East Brooklyn",
"Brooklyn Center",
"Brooklyn Heights"
]
}
}Authentication
The Reverse Geocode API requires authentication via API key. Include your API key in the request header:
X-API-Key: your_api_key_hereInteractive API Playground
Test the Reverse Geocode API directly in your browser with live requests and responses.
Parameters
The following parameters are available for the Reverse Geocode API:
Get Coordinate Details
| Parameter | Type | Required | Description | Default | Example |
|---|---|---|---|---|---|
lat | number | required | The latitude of the coordinates Range: -90 - 90 | - | |
lon | number | required | The longitude of the coordinates Range: -180 - 180 | - |
Response
The Reverse Geocode API returns responses in JSON, XML, YAML, and CSV formats. The JSON response is shown in the Example section above; alternative formats below.
Other Response Formats
<?xml version="1.0" encoding="UTF-8"?>
<response>
<status>ok</status>
<error xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<data>
<zipcode>11211</zipcode>
<state_abbr>NY</state_abbr>
<city>Brooklyn</city>
<state>New York</state>
<distance>0.6501757300758664</distance>
<latitudeClosest>40.712090</latitudeClosest>
<longitudeClosest>-73.95427</longitudeClosest>
<countryCode>US</countryCode>
<latitude>40.714224</latitude>
<longitude>-73.961452</longitude>
<estimatedCity>true</estimatedCity>
<nearestCities>
<nearestCitie>Brooklyn</nearestCitie>
<nearestCitie>Brooklyn Park</nearestCitie>
<nearestCitie>East Brooklyn</nearestCitie>
<nearestCitie>Brooklyn Center</nearestCitie>
<nearestCitie>Brooklyn Heights</nearestCitie>
</nearestCities>
</data>
</response>
status: ok
error: null
data:
zipcode: '11211'
state_abbr: NY
city: Brooklyn
state: New York
distance: 0.6501757300758664
latitudeClosest: '40.712090'
longitudeClosest: '-73.95427'
countryCode: US
latitude: 40.714224
longitude: -73.961452
estimatedCity: true
nearestCities:
- Brooklyn
- Brooklyn Park
- East Brooklyn
- Brooklyn Center
- Brooklyn Heights
| key | value |
|---|---|
| zipcode | 11211 |
| state_abbr | NY |
| city | Brooklyn |
| state | New York |
| distance | 0.6501757300758664 |
| latitudeClosest | 40.712090 |
| longitudeClosest | -73.95427 |
| countryCode | US |
| latitude | 40.714224 |
| longitude | -73.961452 |
| estimatedCity | true |
| nearestCities | [Brooklyn,Brooklyn Park,East Brooklyn,Brooklyn Center,Brooklyn Heights] |
Response Structure
All API responses follow a consistent structure with the following fields:
| Field | Type | Description | Example |
|---|---|---|---|
status | string | Indicates whether the request was successful ("ok") or failed ("error") | ok |
error | string | null | Contains error message if status is "error", otherwise null | null |
data | object | null | Contains the API response data if successful, otherwise null | {...} |
Learn more about response formats →
Response Data Fields
When the request is successful, the data object contains the following fields:
| Field | Type | Sample Value | Description |
|---|---|---|---|
zipcode | string | ZIP code for the location | |
state_abbr | string | Two-letter state abbreviation code | |
city | string | Primary city name at coordinates | |
state | string | Full state name | |
distancePremium | number | Distance to closest coordinates in miles | |
latitudeClosestPremium | string | Latitude of closest mapped coordinate | |
longitudeClosestPremium | string | Longitude of closest mapped coordinate | |
countryCode | string | ISO country code for location | |
latitude | number | Input latitude coordinate | |
longitude | number | Input longitude coordinate | |
estimatedCityPremium | boolean | Whether city is estimated or exact match | |
nearestCitiesPremium | array | List of nearby cities ordered by proximity |
Headers
Only X-API-Key is required. Optional headers include Accept for response format negotiation (JSON, XML, or YAML), User-Agent, and X-Request-ID for request tracing. See all request headers →
GraphQL AccessALPHA
Access Reverse Geocode through GraphQL to combine it with other API calls in a single request. Query only the reverse geocode data you need with precise field selection, and orchestrate complex data fetching workflows.
Credit Cost: Each API called in your GraphQL query consumes its standard credit cost.
POST https://api.apiverve.com/v1/graphqlquery {
reversegeocode(
input: {
lat: 40.714224
lon: -73.961452
}
) {
zipcode
state_abbr
city
state
distance
latitudeClosest
longitudeClosest
countryCode
latitude
longitude
estimatedCity
nearestCities
}
}Note: Authentication is handled via the x-api-key header in your GraphQL request, not as a query parameter.
CORS Support
The Reverse Geocode API accepts cross-origin requests from any origin, so it can be called directly from browser-based applications without a proxy. See CORS support →
Rate Limiting
Reverse Geocode requests are throttled per minute on the Free plan and unthrottled on paid plans. Exceeding the limit returns 429 Too Many Requests; rate-limit usage is reported in the X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset response headers. See per-plan limits and best practices →
Error Codes
The Reverse Geocode API uses standard HTTP status codes — 200 on success, 400 for invalid parameters, 401 for missing or invalid keys, 403 for insufficient credits, 429 for rate-limit exhaustion, and 500/503 for server-side issues. Each error response includes an X-Request-ID header you can quote when contacting support. See full error handling guide →
SDKs for Reverse Geocode
Official Reverse Geocode packages on npm, PyPI, NuGet, and JitPack — plus a Postman collection and an OpenAPI spec. See the SDK guide →
No-Code Integrations
Reverse Geocode works with Zapier, Make, Pipedream, n8n, and Power Automate using the same API key. See setup guides →
Frequently Asked Questions
How do I get an API key for Reverse Geocode?
How many credits does Reverse Geocode cost?
Each successful Reverse Geocode API call consumes credits based on plan tier. Check the pricing section above for the exact credit cost. Failed requests and errors don't consume credits, so you only pay for successful reverse geocode lookups.
Can I use Reverse Geocode in production?
The free plan is for testing and development only. For production use of Reverse Geocode, upgrade to a paid plan (Starter, Pro, or Mega) which includes commercial use rights, no attribution requirements, and guaranteed uptime SLAs. All paid plans are production-ready.
Can I use Reverse Geocode from a browser?
What happens if I exceed my Reverse Geocode credit limit?
When you reach your monthly credit limit, Reverse Geocode API requests will return an error until you upgrade your plan or wait for the next billing cycle. You'll receive notifications at 80% and 95% usage to give you time to upgrade if needed.








