geocode-regeo-query
Latitude/Longitude Parsing & Reverse Geocoding
Provides a Latitude/Longitude Parsing and Reverse Geocoding API service, enabling developers to quickly parse coordinate data and integrate it into business systems.
Usage Cost
5 coins/call
Quick Start
Use a unified response envelope and call directly from your backend.
https://openapi.toolkk.com/v1/geocode-regeo-querycURL Example
curl --request POST \
--url 'https://openapi.toolkk.com/v1/geocode-regeo-query' \
--header 'Content-Type: application/json' \
--header 'X-API-Key: YOUR_API_KEY' \
--data '{\n "lng": 116.397428,\n "lat": 39.90923\n}'Python Example
import os
import requests
url = "https://openapi.toolkk.com/v1/geocode-regeo-query"
payload = {
"lng": 116.397428,
"lat": 39.90923
}
headers = {
"Content-Type": "application/json",
"X-API-Key": os.getenv("TOOLKK_API_KEY", "YOUR_API_KEY"),
}
response = requests.request("POST", url, headers=headers, json=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/geocode-regeo-query"
payload := []byte("{\n \"lng\": 116.397428,\n \"lat\": 39.90923\n}")
req, err := http.NewRequest("POST", 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 \"lng\": 116.397428,\n \"lat\": 39.90923\n}";
HttpRequest request = HttpRequest.newBuilder()
.uri(URI.create("https://openapi.toolkk.com/v1/geocode-regeo-query"))
.method("POST", 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/geocode-regeo-query';
$payload = "{\n \"lng\": 116.397428,\n \"lat\": 39.90923\n}";
$ch = curl_init($endpoint);
curl_setopt_array($ch, [
CURLOPT_RETURNTRANSFER => true,
CURLOPT_CUSTOMREQUEST => 'POST',
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": {
"address": "北京市东城区天安门广场",
"province": "北京市",
"city": "北京市",
"district": "东城区"
}
}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
- 10000 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 |
|---|---|---|---|---|
| lng | number | Unspecified | Unspecified | 116.397428 |
| lat | number | Unspecified | Unspecified | 39.90923 |
Request Example
{
"lng": 116.397428,
"lat": 39.90923
}- Authentication
- Send X-API-Key in request headers
- Rate limit
- 600 req/min
- Timeout
- 10000 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.address | string | Unspecified | Unspecified | 北京市东城区天安门广场 |
| data.province | string | Unspecified | Unspecified | 北京市 |
| data.city | string | Unspecified | Unspecified | 北京市 |
| data.district | string | Unspecified | Unspecified | 东城区 |
Response Example
{
"code": "SUCCESS",
"message": "success",
"data": {
"address": "北京市东城区天安门广场",
"province": "北京市",
"city": "北京市",
"district": "东城区"
}
}Documentation
Capabilities, use cases, and considerations.
Latitude/Longitude Parsing & Reverse Geocoding API Overview
The Latitude/Longitude Parsing & Reverse Geocoding API helps developers quickly process coordinate conversions and reverse geocoding within their systems. It returns structured results, making it ideal for business integration, automated API calls, and system docking.
Use Cases
- Integrate latitude/longitude parsing and reverse geocoding capabilities into internal systems, SaaS platforms, automated workflows, or admin dashboards.
- Suitable for business scenarios requiring stable API calls, standardized responses, and orchestratable interfaces.
- We recommend implementing rate limiting, failure retries, and result caching strategies to improve overall integration stability.
Integration Advice
- Before integrating, verify the request parameter formats, authentication methods, and error code handling logic.
- For high-frequency parsing scenarios, ensure proper log tracking, timeout controls, and idempotency handling.
- If the results are used for risk control or automated decision-making, we recommend applying secondary validation based on your business rules rather than relying solely on the API response.