Docs/APIs/IP Lookup

IP Lookup

Lookup IP address

OperationalCredits 10 per callp50 917msNetworkingStar

Overview

IP Lookup is an IP geolocation API, the GeoIP or IP info lookup behind localisation, fraud checks and compliance routing. It works by querying the IP address against a geolocation database and returning structured location data — country, region, city, coordinates, postal code, timezone and continent — plus the coordinate accuracy radius and whether the country is in the European Union.

Live Test IP 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/iplookup
curl "https://api.apiverve.com/v1/iplookup?ip=173.172.81.20" \
  -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
ipRequiredstringThe IP address for which you want to get the location data (e.g., 173.172.81.20)
ip

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": {
    "ip": "173.172.81.20",
    "country": "US",
    "countryName": "United States",
    "region": "MO",
    "regionName": "Missouri",
    "city": "Kansas City",
    "continent": "NA",
    "continentName": "North America",
    "timezone": "America/Chicago",
    "coordinates": [
      39.0831,
      -94.5853
    ],
    "postalCode": "64106",
    "accuracyRadius": 20,
    "isEU": false,
    "asn": "AS11427",
    "asnName": "TWC-11427-TEXAS"
  }
}

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
ipstring"173.172.81.20"The IP address that was looked up
countrystring"US"ISO 3166-1 alpha-2 country code
countryNamestring"United States"Full country name
regionstring"MO"State/region code
regionNamestring"Missouri"Full state/region name
cityPremiumstring"Kansas City"City name
continentstring"NA"Continent code (e.g. NA, EU, AS)
continentNamestring"North America"Full continent name
timezonestring"America/Chicago"IANA timezone of the IP location
coordinatesPremiumarray[39.0831, ...]Latitude and longitude
postalCodePremiumstring"64106"Postal/ZIP code of the IP location
accuracyRadiusPremiumnumber20Approximate accuracy radius of the coordinates, in kilometers (lower is more precise)
isEUPremiumbooleanfalseWhether the country is a member of the European Union — useful for GDPR/compliance routing
asnPremiumstring"AS11427"Autonomous System Number announcing the IP (e.g., AS15169); null if unrouted
asnNamePremiumstring"TWC-11427-TEXAS"Registered name of that AS (e.g., GOOGLE), not always the company name

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.

Start from a template

A working app built on this API, ready to deploy with your own key. Vercel asks for the key when you deploy; the code is on GitHub to change first.

Use cases

Localized Content Routing
E-commerce storefronts inspect incoming visitor IP addresses to set default languages and display regional offers matched to the country and timezone.
Account Takeover Detection
To flag suspicious logins, fraud engines compare the incoming IP's country and autonomous system number against the customer's known sign-in history.
Geo-Restricted Media Delivery
When a viewer requests video playback, streaming services read the country code to enforce territorial broadcasting rights and block unauthorized regions.
Ad Click Verification
Audit advertising traffic by matching visitor coordinates and autonomous system details against publisher placement records to filter bot farm activity.

Other ways to use IP Lookup

Set up IP 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 Networking:

Was this page helpful?