Resolve raw coordinates to US and Canadian cities and ZIP codes.
Reverse Geocode converts latitude and longitude coordinates into US, Canada and Australia location details. Pass geographic coordinates to retrieve the corresponding city, state, postal code, country code, time zone and US county. Paid plans can add the point's geohash, plus code and degrees-minutes-seconds notation.
Try it — live request, no key required
No key required to try it. Get a key to use it in your app.
{
"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"
],
"timezone": "America/New_York",
"county": "Kings County",
"countyFips": "36047",
"geocodes": {
"geohash": "dr5rsgyct",
"plusCode": "87G8P27Q+MC",
"dms": {
"latitude": "40°42'51.2\"N",
"longitude": "73°57'41.2\"W"
}
}
}
}
About the Reverse Geocode API
A reverse geocoding API for US, Canadian and Australian coordinates. Send a latitude and longitude and get back the nearest city, state or province, the ZIP or postal code and the country code, so you can get city from coordinates or convert coordinates to location details without a mapping SDK. It returns a place, not a street address: the answer is the closest known postal location to the point you sent.
Apps use it to label GPS coordinates in check-ins and delivery logs, find state from lat long for tax or compliance rules, fill in city and ZIP fields from a phone's location, and group sensor or fleet data by area. Each response also echoes the coordinates you sent.
The Free plan returns the city, state, state abbreviation, ZIP or postal code and country code. Paid plans add the coordinates of the matched location and its distance from your point, an estimated-city flag, and a list of the nearest city names ordered by distance.
How it works
Lookup runs in two steps, both against bundled offline data. First the point given by lat and lon is placed in a country using country boundary polygons. Then the nearest entry in a US, Canada and Australia postal location dataset is found for that country, and its city, state, state_abbr and zipcode are returned. Coordinates in any other country are outside the dataset and are not supported.
Results are only as fine-grained as the dataset: the answer is the closest postal-code location, not the containing boundary, so points near a town or ZIP line can resolve to the neighbouring one. latitudeClosest and longitudeClosest are the matched location's coordinates, returned as strings, and distance is how far it lies from your point. latitude and longitude echo the input and countryCode is the two-letter code from the first step.
nearestCities holds up to 20 unique city names from a worldwide city list, ordered by distance from your point, closest first, so it usually starts with the city you are in and continues with its neighbours. distance, the closest coordinates, estimatedCity and nearestCities are null on the Free plan.
What people use it for
- Fleet Telematics Tracking
- Logistics systems match vehicle GPS pings against city and state boundaries to generate human-readable trip summaries for dispatchers.
- Mobile Photo Geotagging
- Camera apps read coordinate metadata from uploaded photos to display the city and state where each picture was taken.
- Delivery Address Autofill
- When a customer shares device coordinates at checkout, ecommerce apps automatically populate the city, state, and ZIP code fields.
- Field Service Dispatch
- To assign incoming repair tickets, maintenance platforms convert technician coordinates into local municipality names and postal codes.
See it in action
The Reverse Geocode API in one live call, from the Playground to your own code.
Ways to call it
One endpoint, many ways in — REST with JSON, XML, YAML and CSV, plus GraphQL and an MCP interface for AI agents.
- JSON
- Default REST response
- XML
- Markup format
- YAML
- Human-readable
- CSV
- Tabular export
- GraphQL
- Query language
- MCP
- For AI agents
Other ways to use Reverse Geocode
Same data, same APIVerve account, same credit balance — one key works on all of them.
Does Reverse Geocode work for coordinates outside the US, Canada and Australia?
How far does the Starter plan go for reverse geocoding lookups?
Are nearest cities and distance metrics included on the Free plan?
How does the API handle coordinates that fall between towns or in rural areas?
Can I store and display the returned location data in a commercial application?
Request parameters — GET /v1/reversegeocode
Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them. Anything not listed here is dropped rather than passed through.
Required
| Parameter | Type | Example | Description |
|---|---|---|---|
latRequired | number | 40.714224 | The latitude of the coordinates range -90-90 |
lonRequired | number | -73.961452 | The longitude of the coordinates range -180-180 |
Optional
| Parameter | Type | Example | Description |
|---|---|---|---|
geocodesOptionalPremium | boolean | true | Add a geocodes object with the point's geohash, plus code (Open Location Code) and degrees-minutes-seconds notation |
curl "https://api.apiverve.com/v1/reversegeocode?lat=40.714224&lon=-73.961452&geocodes=true" \
-H "x-api-key: YOUR_API_KEY"Authentication
Send your key in the x-api-key header. That is the only auth step — no token exchange, and no per-endpoint scope to configure.
| Header | When | Value |
|---|---|---|
x-api-keyRequired | Every request | Your API key. Header names are case-insensitive, so X-API-Key is the same header. |
AuthorizationAlternate | Instead of the above | Bearer <key> — for clients that only expose bearer auth. Resolves to the same account and the same billing. |
A 401 means the key is missing, invalid or expired. A 403 means the key is valid but not permitted here — blocked by a key restriction or an IP allow-list. Running out of credits is a 429.
Response — GET /v1/reversegeocode
Every APIVerve endpoint returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape.
{
"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"
],
"timezone": "America/New_York",
"county": "Kings County",
"countyFips": "36047",
"geocodes": {
"geohash": "dr5rsgyct",
"plusCode": "87G8P27Q+MC",
"dms": {
"latitude": "40°42'51.2\"N",
"longitude": "73°57'41.2\"W"
}
}
}
}
Response fields
Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.
| Field | Type | Example | Description |
|---|---|---|---|
zipcode | string | "11211" | ZIP or postal code for the location. Australian postcodes are returned as numbers, so ones starting with 0 (Darwin, 0800) lose the leading zero |
state_abbr | string | "NY" | Two-letter state abbreviation code |
city | string | "Brooklyn" | Primary city name at coordinates |
state | string | "New York" | Full state name |
distancePremium | number | 0.6501757300758664 | Distance to closest coordinates in miles |
latitudeClosestPremium | string | "40.712090" | Latitude of closest mapped coordinate |
longitudeClosestPremium | string | "-73.95427" | Longitude of closest mapped coordinate |
countryCode | string | "US" | ISO country code for location |
latitude | number | 40.714224 | Input latitude coordinate |
longitude | number | -73.961452 | Input longitude coordinate |
estimatedCityPremium | boolean | true | Whether city is estimated or exact match |
nearestCitiesPremium | array | [Brooklyn, ...] | List of nearby cities ordered by proximity |
timezone | string | "America/New_York" | IANA time zone at the requested coordinates (e.g., America/New_York) |
county | string | "Kings County" | Primary county of the matched ZIP code (US only, null elsewhere) |
countyFipsPremium | string | "36047" | Five-digit FIPS code of that county (US only) |
geocodesPremium | object | {...} | Encodings of the requested point (only when geocodes=true) |
geohashPremium | string | "dr5rsgyct" | 9-character geohash (about 5 m precision) |
plusCodePremium | string | "87G8P27Q+MC" | 10-digit global plus code (Open Location Code, about 14 m precision), e.g., 87G8P27Q+MC |
dmsPremium | object | {...} | Latitude and longitude in degrees, minutes and seconds |
latitudePremium | string | "40°42'51.2"N" | Latitude in DMS notation, e.g., 40°42'51.2"N |
longitudePremium | string | "73°57'41.2"W" | Longitude in DMS notation, e.g., 73°57'41.2"W |
Response headers
Every response carries your balance, so your own code always knows where it stands without polling anything. All four are exposed to browsers through CORS.
| Header | What it carries |
|---|---|
x-api-remaining-credits | Credits left in the current cycle |
x-api-credits-used | Credits spent in the current cycle |
x-api-max-credits | The allowance for the cycle |
x-api-version | Version of the endpoint that answered |
Errors
Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.
| Status | Meaning | What to do |
|---|---|---|
400 | Input was rejected | Read error; it names the parameter that has to change. |
401 | Key missing or invalid | Check the header name and the key value. |
403 | Key valid, but not permitted here | A key restriction or an IP allow-list — never a bad key. |
429 | Rate limited, or out of credits | Read error to tell them apart, then back off or top up. |
What a call costs — 6 credits per call
Credits are shared across every APIVerve API — one balance, one key, one bill. Failed requests never count against it, so a rejected input costs nothing.
| Plan | Per month | Credits | Reverse Geocode calls | Per 1,000 calls |
|---|---|---|---|---|
| Free | Free | 200 | 33 | Free |
| Starter | $29.99 | 200,000 | 33,333 | $0.90 |
| Pro | $99.99 | 1,000,000 | 166,666 | $0.60 |
| Mega | $299.99 | 4,000,000 | 666,666 | $0.45 |
Calls are what the credits buy at this API's rate — spend them here, on any of the other APIs, or across both. Nothing is reserved per endpoint.
Call it from cURL — GET /v1/reversegeocode
No SDK to install — this is a plain HTTPS call to /v1/reversegeocode with your key in the x-api-key header. Swap in a real key and it runs as-is.
curl "https://api.apiverve.com/v1/reversegeocode" \
-H "x-api-key: YOUR_API_KEY"Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Node.js — GET /v1/reversegeocode
Install the Node.js SDK, then call the Reverse Geocode API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
npm install @apiverve/reversegeocodeconst res = await fetch("https://api.apiverve.com/v1/reversegeocode", {
headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Python — GET /v1/reversegeocode
Install the Python SDK, then call the Reverse Geocode API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
pip install apiverve-reversegeocodeimport requests
res = requests.get(
"https://api.apiverve.com/v1/reversegeocode",
headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from C# / .NET — GET /v1/reversegeocode
Install the C# / .NET SDK, then call the Reverse Geocode API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
dotnet add package APIVerve.API.ReverseGeocodeusing var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");
var json = await client.GetStringAsync("https://api.apiverve.com/v1/reversegeocode");
Console.WriteLine(json);Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Go — GET /v1/reversegeocode
No SDK to install — this is a plain HTTPS call to /v1/reversegeocode with your key in the x-api-key header. Swap in a real key and it runs as-is.
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/reversegeocode", nil)
req.Header.Set("x-api-key", "YOUR_API_KEY")
res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from PHP — GET /v1/reversegeocode
No SDK to install — this is a plain HTTPS call to /v1/reversegeocode with your key in the x-api-key header. Swap in a real key and it runs as-is.
$ch = curl_init("https://api.apiverve.com/v1/reversegeocode");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-api-key: YOUR_API_KEY"]);
$response = curl_exec($ch);
echo $response;Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Ruby — GET /v1/reversegeocode
No SDK to install — this is a plain HTTPS call to /v1/reversegeocode with your key in the x-api-key header. Swap in a real key and it runs as-is.
require "net/http"
uri = URI("https://api.apiverve.com/v1/reversegeocode")
req = Net::HTTP::Get.new(uri)
req["x-api-key"] = "YOUR_API_KEY"
res = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) { |h| h.request(req) }
puts res.bodyResources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Zero-code embed — one snippet, no backend
Drop an interactive Reverse Geocode form onto any page. The widget calls the API for you, so no key ever appears in your markup and there is nothing to deploy.
Changelog — Reverse Geocode API
Every change to this endpoint, newest first. Breaking changes ship as a new version and the previous one keeps serving — response fields are added, never removed or retyped in place, so an integration written against v1 keeps working.
Entries are picked up from dated catalog snapshots, so the first one appears after the next snapshot that moves something. A period where nothing changed produces no entry — silence is a valid changelog for the Reverse Geocode API.
Geography
- Cities Lookup
- Coordinates Are Sea
- Country Borders
- Country Boundaries
- Country Flags
- Country Languages
- Country Lookup
- County Data Lookup
- Distance Calculator
- India Pincode Lookup
- Reverse Geocode
- State Boundaries
- USDA Hardiness Zone
- Zip Codes Lookup
Related articles
All articles →
Location APIs: Distance, Geocoding, and TimezonesBuild location-aware features without Google Maps pricing. Distance calculations, address lookup, timezone handling—all from one API.Read
Multi-Currency E-commerce: Stop Losing SalesShowing prices in local currency increases conversions 20-40%. Here's how to implement multi-currency pricing that actually works.Read
Extract Clean Content from Any WebpageTurn messy web pages into clean Markdown. Perfect for content migration, archiving, AI training data, and building read-later tools.Read