Quick answers about the IpQuery.Info API, quotas, and data. Still stuck? See the documentation or contact us.
Every request needs an apiKey query parameter. A default key is created automatically when you start your trial — copy it from the API Keys page. Keep secret keys on your server.
Pass ip= for a single address, ipList= for a query-string batch, send a POST body for larger bulk lookups, or omit all selectors to look up the address the request comes from. When you call from your back end, "the caller" is your server — pass the visitor's IP explicitly with ip=.
Yes. Both IPv4 and IPv6 addresses are accepted anywhere an IP is expected.
Each plan includes a monthly request allowance (Free trial 1,000 · Basic 100,000 · Advanced 1.5M · Enterprise 5M). One single-IP request counts as one; a batch ipList request counts as one per address. Your remaining allowance and reset cycle are on the Statistics dashboard.
The API returns HTTP 402 until the cycle resets or you upgrade on the Account & Billing page.
400 — invalid POST body. 401 — missing API key, or a tag longer than 20 characters. 402 — key is invalid or the monthly quota is exhausted. 403 — key restrictions rejected the request. 404 — key not found, or a specific IP could not be resolved. 413 — bulk request too large. 429 — per-client-IP rate limit exceeded.
A per-key option (on the API Keys page). A Record-Only key returns just an acknowledgement instead of the enrichment data, so it's safe to use from the browser to feed your Statistics while keeping the dataset private. You can also enable Rate Limit by IP to throttle a single caller to one request per five minutes.
Add a tag (max 20 chars) to single-address requests — it's recorded with the lookup so you can filter your charts by campaign, product, or source. See Segment usage with tags.
Enrichment combines several datasets — MaxMind GeoLite2 and DB-IP (geolocation), RIPE NCC (European network registration), plus VPN/proxy/Tor, cloud, crawler and spam lists. City-level geolocation is approximate by nature; country and network data are highly reliable.
Yes — the full field reference and a machine-readable OpenAPI spec are in the documentation.