API features
WGS84, GCJ-02, and BD-09
Work with the three coordinate systems commonly encountered across global and China-focused map products.
All source and target combinations
Convert between any supported pair, including same-system normalization when required.
Consistent coordinate order
Receive every result in a predictable [longitude, latitude] array for safer integration.
Map provider normalization
Align coordinates collected from international maps, China map providers, and location datasets.
Geocoding and mobility workflows
Prepare location values for map display, navigation, delivery, fleet, and geospatial analysis.
Safe out-of-region behavior
Preserve coordinates outside the applicable GCJ-02 region instead of applying an unsuitable offset.
API Document
HTTP Protocol:HTTPS
HTTP Method:GET
HTTP Endpoint:https://api.gugudata.io/v1/location/coordinateconverter
Response Type:application/json; charset=utf-8
DEMO Endpoint:https://api.gugudata.io/v1/location/coordinateconverter/demo
Live Demo:Try Interactive Demo
Postman Collection:Run in Postman
API Request Parameters
| Name | Type | Is Required | Default Value | Remark |
|---|---|---|---|---|
| appkey | string | true | YOUR_APPKEY | API key used to authenticate the request. |
| from | string | true | WGS84 | Source coordinate system. Canonical values are `WGS84`, `GCJ02`, and `BD09`; matching is case-insensitive for compatibility. |
| to | string | true | GCJ02 | Target coordinate system. Canonical values are `WGS84`, `GCJ02`, and `BD09`; matching is case-insensitive for compatibility. |
| value | string | true | [120.54,32.74] | Coordinate pair in `[longitude,latitude]` format. Longitude must be between -180 and 180; latitude must be between -90 and 90. |
API Response Parameters
| Name | Type | Remark |
|---|---|---|
| dataStatus | object | Response metadata for the request. |
| dataStatus.requestParameter | string | Privacy-safe summary of the normalized request. |
| dataStatus.statusCode | integer | Application-level status code. |
| dataStatus.statusDescription | string | Human-readable application status message. |
| dataStatus.responseDateTime | string | Time at which the response was generated. |
| dataStatus.dataTotalCount | integer | Number of matching or returned records for this request. |
| data | object | Converted coordinate result. |
| data.coordinateFrom | string | Normalized source coordinate system. |
| data.coordinateTo | string | Normalized target coordinate system. |
| data.coordinateSourceValue | string | Validated source coordinate in `[longitude,latitude]` format. |
| data.coordinateDestinationValue | string | Converted coordinate in `[longitude,latitude]` format. |
API Response Status Codes
| Status Code | Explanation of Status Code | Remarks |
|---|---|---|
| 200 | Request processed successfully. | Some endpoints expose a separate application-level status field in the response body, such as `dataStatus.statusCode`. |
| 400 | Invalid request parameters or request format. | Check required fields, data types, and request body format. |
| 401 | Missing or unknown application key. | Provide a valid `appkey` with the request. |
| 403 | The application key is recognized but access is not allowed. | The key may be expired, inactive, or not permitted for the requested API. |
| 429 | Request rate or trial usage limit exceeded. | Reduce request frequency and retry with backoff. If a trial allowance is exhausted, check Trial Keys for remaining requests and subscribe to continue. |
| 500 | Internal service error. | Retry later or contact support if the error persists. |
| 503 | Upstream service unavailable. | Retry later; the requested upstream dependency is temporarily unavailable. |
Remote MCP
Use this API through GuGuData Remote MCP
Connect your AI client once, authorize in the browser, and the client can use the GuGuData API tools available to your account. You do not need to paste an appkey into the MCP client.
https://mcp.gugudata.io/mcp{
"mcpServers": {
"gugudata": {
"url": "https://mcp.gugudata.io/mcp",
"transportType": "streamable-http"
}
}
}Code Snippets
Frequently asked questions
Common questions about request limits, trials, renewal, and cancellation.
What does the 5 requests per second limit mean?
It is a request-rate limit, not a concurrency allowance. Keep your request rate at or below 5 per second. If the service returns a rate-limit response, reduce the frequency and retry with backoff.
Is total paid usage limited?
There is no total request cap during an active paid subscription and no usage-based overage charge.
How does the free trial work?
Each account can receive a limited trial key. Requests are shared across APIs in the same category. Check Trial Keys for the exact allowance and remaining requests.
How do renewal and cancellation work?
The plan renews annually until canceled. Manage or cancel the renewal from Dashboard → Orders & Billing. Access continues through the paid period after cancellation. See the Terms of Service for the current refund policy. If the billing portal is unavailable, contact support.
Service terms
Read our service terms and privacy policy before subscribing.




