ip-biz-query
High-Precision Commercial IPv4 Lookup
Provides a high-precision commercial IPv4 lookup API service, enabling developers to quickly query accurate IPv4 information and integrate it into business systems.
Usage Cost
20 coins/call
Quick Start
Use a unified response envelope and call directly from your backend.
https://openapi.toolkk.com/v1/ip-biz-querycURL Example
curl --request GET \
--url 'https://openapi.toolkk.com/v1/ip-biz-query' \
--header 'Content-Type: application/json' \
--header 'X-API-Key: YOUR_API_KEY' \
--data '{\n "ip": "114.114.114.114",\n "area": "0",\n "coordsys": "wgs84"\n}'Python Example
import os
import requests
url = "https://openapi.toolkk.com/v1/ip-biz-query"
payload = {
"ip": "114.114.114.114",
"area": "0",
"coordsys": "wgs84"
}
headers = {
"Content-Type": "application/json",
"X-API-Key": os.getenv("TOOLKK_API_KEY", "YOUR_API_KEY"),
}
response = requests.get(url, headers=headers, params=payload, timeout=30)
response.raise_for_status()
print(response.json())Go Example
package main
import (
"bytes"
"fmt"
"io"
"net/http"
)
func main() {
endpoint := "https://openapi.toolkk.com/v1/ip-biz-query"
payload := []byte("{\n \"ip\": \"114.114.114.114\",\n \"area\": \"0\",\n \"coordsys\": \"wgs84\"\n}")
req, err := http.NewRequest("GET", endpoint, bytes.NewBuffer(payload))
if err != nil {
panic(err)
}
req.Header.Set("Content-Type", "application/json")
req.Header.Set("X-API-Key", "YOUR_API_KEY")
resp, err := http.DefaultClient.Do(req)
if err != nil {
panic(err)
}
defer resp.Body.Close()
body, err := io.ReadAll(resp.Body)
if err != nil {
panic(err)
}
fmt.Println(string(body))
}Java Example
import java.net.URI;
import java.net.http.HttpClient;
import java.net.http.HttpRequest;
import java.net.http.HttpResponse;
public class ToolkkExample {
public static void main(String[] args) throws Exception {
String payload = "{\n \"ip\": \"114.114.114.114\",\n \"area\": \"0\",\n \"coordsys\": \"wgs84\"\n}";
HttpRequest request = HttpRequest.newBuilder()
.uri(URI.create("https://openapi.toolkk.com/v1/ip-biz-query"))
.method("GET", HttpRequest.BodyPublishers.ofString(payload))
.header("Content-Type", "application/json")
.header("X-API-Key", "YOUR_API_KEY")
.build();
HttpResponse<String> response = HttpClient.newHttpClient()
.send(request, HttpResponse.BodyHandlers.ofString());
System.out.println(response.body());
}
}PHP Example
<?php
$endpoint = 'https://openapi.toolkk.com/v1/ip-biz-query';
$payload = "{\n \"ip\": \"114.114.114.114\",\n \"area\": \"0\",\n \"coordsys\": \"wgs84\"\n}";
$ch = curl_init($endpoint);
curl_setopt_array($ch, [
CURLOPT_RETURNTRANSFER => true,
CURLOPT_CUSTOMREQUEST => 'GET',
CURLOPT_HTTPHEADER => [
'Content-Type: application/json',
'X-API-Key: YOUR_API_KEY',
],
CURLOPT_POSTFIELDS => $payload,
]);
$response = curl_exec($ch);
if ($response === false) {
throw new RuntimeException(curl_error($ch));
}
curl_close($ch);
echo $response;Response Example
{
"code": "SUCCESS",
"message": "success",
"data": {
"country": "中国",
"province": "江苏省",
"city": "南京市",
"longitude": 118.7969,
"latitude": 32.0584
}
}Examples illustrate the response structure. Actual results depend on the API response.
- Authentication
- Send X-API-Key in request headers
- Rate limit
- 600 req/min
- Timeout
- 5000 ms
Send your API Key in the X-API-Key header from your backend.
Check both HTTP status and business fields before treating a call as successful.
Use retries and backoff together with rate limits in high-frequency scenarios.
Request Fields
Send requests from your server with the key in the X-API-Key header.
Request Fields
The fields below are derived from example JSON for integration reference only.
| Path | Type | Required | Description | Sample |
|---|---|---|---|---|
| ip | string | Unspecified | Unspecified | 114.114.114.114 |
| area | string | Unspecified | Unspecified | 0 |
| coordsys | string | Unspecified | Unspecified | wgs84 |
Request Example
{
"ip": "114.114.114.114",
"area": "0",
"coordsys": "wgs84"
}- Authentication
- Send X-API-Key in request headers
- Rate limit
- 600 req/min
- Timeout
- 5000 ms
Response Fields
Examples illustrate the response structure. Actual results depend on the API response.
Response Fields
The fields below are derived from example JSON for integration reference only.
| Path | Type | Required | Description | Sample |
|---|---|---|---|---|
| code | string | Unspecified | Unspecified | SUCCESS |
| message | string | Unspecified | Unspecified | success |
| data | object | Unspecified | Unspecified | {...} |
| data.country | string | Unspecified | Unspecified | 中国 |
| data.province | string | Unspecified | Unspecified | 江苏省 |
| data.city | string | Unspecified | Unspecified | 南京市 |
| data.longitude | number | Unspecified | Unspecified | 118.7969 |
| data.latitude | number | Unspecified | Unspecified | 32.0584 |
Response Example
{
"code": "SUCCESS",
"message": "success",
"data": {
"country": "中国",
"province": "江苏省",
"city": "南京市",
"longitude": 118.7969,
"latitude": 32.0584
}
}$.code == 200 API overview
Capabilities, use cases, limitations, and frequently asked questions.
High-Precision Commercial IPv4 Lookup API Overview
The High-Precision Commercial IPv4 Lookup API helps developers quickly process highly accurate IPv4 queries within their systems. It returns structured results and is ideal for scenarios such as cybersecurity analysis, access risk control, and data governance.
Use Cases
- Integrate high-precision IPv4 lookup capabilities into internal systems, SaaS platforms, automated workflows, or admin dashboards.
- Suitable for business scenarios requiring stable invocations, standardized responses, and orchestratable API capabilities.
- We recommend combining this with rate limiting, failure retries, and result caching strategies to improve overall integration stability.
Integration Advice
- Before integrating, confirm the request parameter formats, authentication methods, and error code handling logic.
- For high-frequency query scenarios, it is recommended to implement log tracking, timeout controls, and idempotency handling.
- If the results are used for risk control or automated decision-making, we advise combining them with business rules for secondary validation rather than relying solely on the API response as a single point of truth.