Overview
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.
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.
curl "https://api.apiverve.com/v1/iplookup?ip=173.172.81.20" \
-H "x-api-key: your_api_key_here"const res = await fetch('https://api.apiverve.com/v1/iplookup?ip=173.172.81.20', {
headers: { 'x-api-key': 'your_api_key_here' },
});
if (!res.ok) throw new Error(`${res.status} ${await res.text()}`);
const { data } = await res.json();
console.log(data);import requests
res = requests.get(
"https://api.apiverve.com/v1/iplookup?ip=173.172.81.20",
headers={"x-api-key": "your_api_key_here"},
timeout=15,
)
res.raise_for_status()
print(res.json()["data"])package main
import (
"fmt"
"io"
"net/http"
)
func main() {
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/iplookup?ip=173.172.81.20", nil)
req.Header.Set("x-api-key", "your_api_key_here")
res, err := http.DefaultClient.Do(req)
if err != nil {
panic(err)
}
defer res.Body.Close()
out, _ := io.ReadAll(res.Body)
fmt.Println(string(out))
}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.
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.
| Parameter | Type | Description |
|---|---|---|
ipRequired | string | The 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.
{
"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 |
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.
| Status | Meaning | What to do |
|---|---|---|
400 | Input was rejected | Read error; it names the parameter. |
401 | Key missing or invalid | Check the header name and the key value. |
403 | Key valid, but not permitted | A key restriction or IP allow-list; see key scoping. |
429 | Rate limited, or out of credits | Read error to tell them apart; see rate limits. |
Use cases
- 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
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.
Related
More in Networking: