Docs/APIs/Cities Lookup

Cities Lookup

Lookup city data

OperationalCredits 2 per callp50 1412msGeographyStar

Overview

Pass any city name to query a monthly updated catalog of over 150,000 settlements. The response lists matching places with their country name, two-letter ISO code, census population count, and population category. Free requests return one matching record, while paid plans include custom result limits and longitude-latitude coordinates.

Live Test Cities Lookup API →

Endpoint

One host, one path per API. The block below shows this call in four languages; every one of them is the same HTTP request. Making requests covers the timeouts, retries and parameter rules that apply to all of them. The SDKs wrap the same call in a typed client.

GEThttps://api.apiverve.com/v1/citieslookup
curl "https://api.apiverve.com/v1/citieslookup?city=San%20Francisco&limit=5" \
  -H "x-api-key: your_api_key_here"

Replace your_api_key_here with the key from your dashboard. When the inputs arrive as a list rather than one at a time, batch requests run up to 200 of them through this same API in a single call.

Authentication

Send your key in the x-api-key header. That is the only auth step — there is no token exchange and no per-endpoint scope to configure. Authentication covers creating, rotating and revoking keys.

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.

Parameters

Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them.

ParameterTypeDescription
cityRequiredstringThe city name for which you want to get the data (e.g., New York)
limitOptionalPremiumintegerLimit number of cities that match your search criteria
default 1 · range 1–20

Response

Every API returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape. Response format covers the envelope, the other output formats and how premium fields are withheld.

Sample response
{
  "status": "ok",
  "error": null,
  "data": {
    "search": "San Francisco",
    "foundCities": [
      {
        "name": "San Francisco",
        "altName": "",
        "country": "US",
        "countryName": "United States",
        "featureCode": "PPLA2",
        "population": 874961,
        "populationCategory": "major",
        "loc": {
          "type": "Point",
          "coordinates": [
            -122.4194,
            37.7749
          ]
        }
      }
    ]
  }
}

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.

FieldTypeExampleDescription
searchstring"San Francisco"The search query used to find cities
foundCitiesarray[1]Array of city objects matching the search criteria
namestring"San Francisco"Official city name
altNamestring""Alternative city name or alias if available
countrystring"US"Two-letter ISO country code (e.g., US)
countryNamestring"United States"Full country name (e.g., United States)
featureCodestring"PPLA2"Geonames feature code for city classification type
populationnumber874961City population count derived from latest census
populationCategorystring"major"City size classification based on population ranges
locobject{...}
typestring"Point"GeoJSON geometry type (always Point)
coordinatesPremiumarray[-122.4194, ...]GeoJSON coordinates as [longitude, latitude] pair

Errors

Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change. Error handling covers the full status list and which of them are worth retrying.

StatusMeaningWhat to do
400Input was rejectedRead error; it names the parameter.
401Key missing or invalidCheck the header name and the key value.
403Key valid, but not permittedA key restriction or IP allow-list; see key scoping.
429Rate limited, or out of creditsRead error to tell them apart; see rate limits.

Use cases

Checkout Address Validation
When customers enter a city name during checkout, match official country codes and alternative names to standardize shipping records.
Retail Expansion Sizing
Retail analysts evaluate new store candidates by querying population figures and city size categories across international regions.
Fleet Dispatch Routing
For regional delivery scheduling, dispatchers convert destination city names into exact longitude and latitude coordinates on paid tiers.
Travel Destination Filtering
To help users discover vacation spots, travel search engines group destinations by population tier and resolve local alias spellings.

Other ways to use Cities Lookup

Set up Cities Lookup on APIVerve, or reach the same source a different way. Your APIVerve account and credits work on all of them — one key, one balance.

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

More in Geography:

Was this page helpful?