Reverse Geocode API

GET

Resolve raw coordinates to US and Canadian cities and ZIP codes.

Reverse Geocode converts latitude and longitude coordinates into US and Canada location details. Pass geographic coordinates to retrieve the corresponding city, state, postal code, and country code.

Try it — live request, no key required

Request

GETapi.apiverve.com/v1/reversegeocode?lat=40.714224&lon=-73.961452

Query parameters

latnumber

lonnumber

Verification

Format

No key required to try it. Get a key to use it in your app.

Example

{
  "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"
    ]
  }
}

About the Reverse Geocode API

Reverse Geocode works by converting the latitude and longitude coordinates into a human-readable address. Only supports USA and Canada Coordinates. It uses advanced algorithms and a large database of locations to provide accurate and up-to-date information.

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.

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

View all integrations →

Other ways to use Reverse Geocode

Same data, same APIVerve account, same credit balance — one key works on all of them.

Give it to an AI agentConnect over MCP and your agent calls it as a native tool — Claude, Cursor, ChatGPT.on VerveKit Google Sheets or ExcelA =VERVE() formula fills a column — no script, no export, recalculates in place.on VerveSheets Ground an agent on itA cited, machine-checkable fact your model can't produce on its own.on VerveContext

Questions.

Common questions about the Reverse Geocode API.

Read the docs →

Does Reverse Geocode work for coordinates outside the US and Canada?

No. The API only supports coordinates within the United States and Canada. Coordinates from other countries will not resolve to local address data.

How far does the Starter plan go for reverse geocoding lookups?

Each lookup consumes 6 credits. The Starter plan provides 200,000 monthly credits, which covers up to 33,333 reverse geocode calls. That works out to about $0.90 per 1,000 lookups, or $0.0009 per call. The Free plan includes 200 credits, allowing about 33 lookups each month.

Are nearest cities and distance metrics included on the Free plan?

No. Nearby cities, distance to closest coordinate, closest mapped coordinates, and the estimated city indicator are premium fields. Any paid plan unlocks these fields alongside the standard city, state, ZIP code, and country code returned on the Free plan.

How does the API handle coordinates that fall between towns or in rural areas?

The API maps the point to the closest known location in its database. On paid plans, you receive the estimated city indicator to confirm whether the city was an exact match or an estimate, along with the distance in miles to that closest coordinate.

Can I store and display the returned location data in a commercial application?

Yes, provided you are on a paid plan. Commercial use is allowed across all paid tiers for powering features within your own application. You may not resell or redistribute the raw geocoding data as a standalone dataset.

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
`lat`Required	number	`40.714224`	The latitude of the coordinates range -90-90
`lon`Required	number	`-73.961452`	The longitude of the coordinates range -180-180

Example request

1
2

curl "https://api.apiverve.com/v1/reversegeocode?lat=40.714224&lon=-73.961452" \
  -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-key`Required	Every request	Your API key. Header names are case-insensitive, so `X-API-Key` is the same header.
`Authorization`Alternate	Instead of the above	`Bearer <key>` — for clients that only expose bearer auth. Resolves to the same account and the same billing.

401 is the only auth verdict

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.

Sample 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"
    ]
  }
}

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 code for the location
`state_abbr`	string	`"NY"`	Two-letter state abbreviation code
`city`	string	`"Brooklyn"`	Primary city name at coordinates
`state`	string	`"New York"`	Full state name
`distance`Premium	number	`0.6501757300758664`	Distance to closest coordinates in miles
`latitudeClosest`Premium	string	`"40.712090"`	Latitude of closest mapped coordinate
`longitudeClosest`Premium	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
`estimatedCity`Premium	boolean	`true`	Whether city is estimated or exact match
`nearestCities`Premium	array	`[Brooklyn, ...]`	List of nearby cities ordered by proximity

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.

Compare all pricing tiers →

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

1
2

curl "https://api.apiverve.com/v1/reversegeocode" \
  -H "x-api-key: YOUR_API_KEY"

Resources

GitHubapiverve/reversegeocode-apiSource, issues and the examples this page is built from.ReferenceReverse Geocode API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/reversegeocodenpm apiverve-reversegeocodePyPI APIVerve.API.ReverseGeocodeNuGet

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.

Install — npm

npm install @apiverve/reversegeocode

Node.js

const 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

npm@apiverve/reversegeocodeThe published Node.js client, versioned and signed.GitHubapiverve/reversegeocode-apiSource, issues and the examples this page is built from.ReferenceReverse Geocode API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

apiverve-reversegeocodePyPI APIVerve.API.ReverseGeocodeNuGet

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.

Install — PyPI

pip install apiverve-reversegeocode

Python

import requests

res = requests.get(
    "https://api.apiverve.com/v1/reversegeocode",
    headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])

Resources

PyPIapiverve-reversegeocodeThe published Python client, versioned and signed.GitHubapiverve/reversegeocode-apiSource, issues and the examples this page is built from.ReferenceReverse Geocode API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/reversegeocodenpm APIVerve.API.ReverseGeocodeNuGet

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.

Install — NuGet

dotnet add package APIVerve.API.ReverseGeocode

C# / .NET

using 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

NuGetAPIVerve.API.ReverseGeocodeThe published C# / .NET client, versioned and signed.GitHubapiverve/reversegeocode-apiSource, issues and the examples this page is built from.ReferenceReverse Geocode API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/reversegeocodenpm apiverve-reversegeocodePyPI

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

@apiverve/reversegeocodenpm apiverve-reversegeocodePyPI APIVerve.API.ReverseGeocodeNuGet

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.

PHP

$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

@apiverve/reversegeocodenpm apiverve-reversegeocodePyPI APIVerve.API.ReverseGeocodeNuGet

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.

Ruby

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.body

Resources

Also published for

@apiverve/reversegeocodenpm apiverve-reversegeocodePyPI APIVerve.API.ReverseGeocodeNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

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

Reverse Geocode API

Try it — live request, no key required

About the Reverse Geocode API

What people use it for

Ways to call it

Other ways to use Reverse Geocode

Questions.

Request parameters — GET /v1/reversegeocode

Required

Authentication

Response — GET /v1/reversegeocode

Response fields

Response headers

Errors

What a call costs — 6 credits per call

Call it from cURL — GET /v1/reversegeocode

Resources

Also published for

Call it from Node.js — GET /v1/reversegeocode

Resources

Also published for

Call it from Python — GET /v1/reversegeocode

Resources

Also published for

Call it from C# / .NET — GET /v1/reversegeocode

Resources

Also published for

Call it from Go — GET /v1/reversegeocode

Resources

Also published for

Call it from PHP — GET /v1/reversegeocode

Resources

Also published for

Call it from Ruby — GET /v1/reversegeocode

Resources

Also published for

Zero-code embed — one snippet, no backend

Changelog — Reverse Geocode API

Geography

Related articles

Ready to build with Reverse Geocode? Start with 200 free credits — one key unlocks all 300+ APIs.

Explore the catalog