IP Lookup resolves an IP address to its geographic location. It returns the country, region, city, coordinates, postal code, timezone and continent, along with an accuracy radius and an EU-membership flag for compliance routing.
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": {
// IP Lookup response payload
}
}
About the IP Lookup API
IP Lookup 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.
What people use it for
- Geolocation
- Use the IP Lookup API to look up the location of an IP address for geolocation. Use the data to track IP addresses, identify user locations, and analyze traffic patterns
- Security Analysis
- Look up IP addresses by using the IP Lookup API for security analysis. Use the data to detect suspicious activities, block malicious users, and prevent cyber attacks
- Network Monitoring
- Monitor networks by using the IP Lookup API to look up IP addresses. Use the data to track network traffic, analyze IP activity, and troubleshoot connectivity issues
- Fraud Detection
- Detect fraud by using the IP Lookup API to look up IP addresses. Use the data to identify fraudulent activities, block suspicious users, and protect against scams
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 IP Lookup
Same data, same APIVerve account, same credit balance — one key works on all of them.
What does the IP Lookup API do?
How do I authenticate IP Lookup API requests?
How much does the IP Lookup API cost?
How fast is the IP Lookup API?
What response formats does the IP Lookup API support?
What HTTP method does the IP Lookup API use?
Request parameters — GET /v1/iplookup
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 |
|---|---|---|---|
ipRequired | string | 173.172.81.20 | The IP address for which you want to get the location data (e.g., 173.172.81.20) ip |
curl "https://api.apiverve.com/v1/iplookup?ip=173.172.81.20" \
-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/iplookup
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": {
"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
}
}
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 |
|---|---|---|---|
ip | string | "173.172.81.20" | The IP address that was looked up |
country | string | "US" | ISO 3166-1 alpha-2 country code |
countryName | string | "United States" | Full country name |
region | string | "MO" | State/region code |
regionName | string | "Missouri" | Full state/region name |
cityPremium | string | "Kansas City" | City name |
continent | string | "NA" | Continent code (e.g. NA, EU, AS) |
continentName | string | "North America" | Full continent name |
timezone | string | "America/Chicago" | IANA timezone of the IP location |
coordinatesPremium | array | [39.0831, ...] | Latitude and longitude |
postalCodePremium | string | "64106" | Postal/ZIP code of the IP location |
accuracyRadiusPremium | number | 20 | Approximate accuracy radius of the coordinates, in kilometers (lower is more precise) |
isEUPremium | boolean | false | Whether the country is a member of the European Union — useful for GDPR/compliance routing |
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 — 10 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 | IP Lookup calls | Per 1,000 calls |
|---|---|---|---|---|
| Free | Free | 200 | 20 | Free |
| Starter | $29.99 | 200,000 | 20,000 | $1.50 |
| Pro | $99.99 | 1,000,000 | 100,000 | $1.00 |
| Mega | $299.99 | 4,000,000 | 400,000 | $0.75 |
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/iplookup
No SDK to install — this is a plain HTTPS call to /v1/iplookup 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/iplookup" \
-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/iplookup
Install the Node.js SDK, then call the IP Lookup API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
npm install @apiverve/iplookupconst res = await fetch("https://api.apiverve.com/v1/iplookup", {
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/iplookup
Install the Python SDK, then call the IP Lookup API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
pip install apiverve-iplookupimport requests
res = requests.get(
"https://api.apiverve.com/v1/iplookup",
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/iplookup
Install the C# / .NET SDK, then call the IP Lookup 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.IPLookupusing var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");
var json = await client.GetStringAsync("https://api.apiverve.com/v1/iplookup");
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/iplookup
No SDK to install — this is a plain HTTPS call to /v1/iplookup 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/iplookup", 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/iplookup
No SDK to install — this is a plain HTTPS call to /v1/iplookup 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/iplookup");
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/iplookup
No SDK to install — this is a plain HTTPS call to /v1/iplookup 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/iplookup")
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 IP Lookup 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 — IP Lookup 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 IP Lookup API.
Networking
- Bluetooth Company Lookup
- Bot Detector
- Content Filter
- Domain and IP Pinger
- IP Blacklist Lookup
- IP Lookup
- MAC Address Lookup
- Nameservers
- Phishing Domain Checker
- TLD Lookup
- TLS Checker
- Tor Node Detector
- USB Vendor Lookup
- VPN Proxy Detector
Related articles
All articles →
How to Detect VPN and Proxy UsersIdentify VPN, proxy, and datacenter IPs to prevent fraud and enforce geo-restrictions. Complete tutorial with code examples.Read
IP Geolocation: Accuracy, Limitations, and Best PracticesIP geolocation has limits. Learn when it works, when it fails, and how to handle edge cases in your applications.Read
The Developer's Guide to API Vendor Lock-InEvery API integration is a bet. Here's how to recognize lock-in traps before you're stuck, and how to build your way out.Read