UTM Coordinate Converter API
Overview
To use UTM Coordinate Converter, you need an API key. You can get one by creating a free account and visiting your dashboard.
GET Endpoint
https://api.apiverve.com/v1/utmconverterExample
How to call the UTM Coordinate Converter API in different programming languages.
curl -X GET \
"https://api.apiverve.com/v1/utmconverter?direction=to_utm&latitude=40.7128&longitude=-74.006" \
-H "X-API-Key: your_api_key_here"const response = await fetch('https://api.apiverve.com/v1/utmconverter?direction=to_utm&latitude=40.7128&longitude=-74.006', {
method: 'GET',
headers: {
'X-API-Key': 'your_api_key_here',
'Content-Type': 'application/json'
}
});
const data = await response.json();
console.log(data);import requests
headers = {
'X-API-Key': 'your_api_key_here',
'Content-Type': 'application/json'
}
response = requests.get('https://api.apiverve.com/v1/utmconverter?direction=to_utm&latitude=40.7128&longitude=-74.006', headers=headers)
data = response.json()
print(data)package main
import (
"fmt"
"io"
"net/http"
)
func main() {
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/utmconverter?direction=to_utm&latitude=40.7128&longitude=-74.006", nil)
req.Header.Set("X-API-Key", "your_api_key_here")
req.Header.Set("Content-Type", "application/json")
client := &http.Client{}
resp, err := client.Do(req)
if err != nil {
panic(err)
}
defer resp.Body.Close()
body, _ := io.ReadAll(resp.Body)
fmt.Println(string(body))
}{
"status": "ok",
"error": null,
"data": {
"conversion": "lat/lon to UTM",
"input": {
"latitude": 40.7128,
"longitude": -74.006
},
"output": {
"zone": 18,
"hemisphere": "N",
"easting": 583959.37,
"northing": 4507351
},
"formatted": "18N 583959E 4507351N",
"datum": "WGS84"
}
}Authentication
The UTM Coordinate Converter API requires authentication via API key. Include your API key in the request header:
X-API-Key: your_api_key_hereInteractive API Playground
Test the UTM Coordinate Converter API directly in your browser with live requests and responses.
Parameters
The UTM Coordinate Converter API supports multiple query options. Use one of the following:
Option 1: Lat/Long to UTM
| Parameter | Type | Required | Description | Default | Example |
|---|---|---|---|---|---|
direction | string | optional | Conversion direction Supported values: to_utmfrom_utm | ||
latitude | number | required | Latitude (-90 to 90) Range: -90 - 90 | - | |
longitude | number | required | Longitude (-180 to 180) Range: -180 - 180 | - |
Option 2: UTM to Lat/Long
| Parameter | Type | Required | Description | Default | Example |
|---|---|---|---|---|---|
direction | string | optional | Conversion direction Supported values: to_utmfrom_utm | ||
zone | integer | required | UTM zone (1-60) | - | |
easting | number | required | UTM easting coordinate | - | |
northing | number | required | UTM northing coordinate | - | |
hemisphere | string | required | Hemisphere (N or S) | - |
Response
The UTM Coordinate Converter API returns responses in JSON, XML, YAML, and CSV formats. The JSON response is shown in the Example section above; alternative formats below.
Other Response Formats
<?xml version="1.0" encoding="UTF-8"?>
<response>
<status>ok</status>
<error xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<data>
<conversion>lat/lon to UTM</conversion>
<input>
<latitude>40.7128</latitude>
<longitude>-74.006</longitude>
</input>
<output>
<zone>18</zone>
<hemisphere>N</hemisphere>
<easting>583959.37</easting>
<northing>4507351</northing>
</output>
<formatted>18N 583959E 4507351N</formatted>
<datum>WGS84</datum>
</data>
</response>
status: ok
error: null
data:
conversion: lat/lon to UTM
input:
latitude: 40.7128
longitude: -74.006
output:
zone: 18
hemisphere: 'N'
easting: 583959.37
northing: 4507351
formatted: 18N 583959E 4507351N
datum: WGS84
| key | value |
|---|---|
| conversion | lat/lon to UTM |
| input | {latitude:40.7128,longitude:-74.006} |
| output | {zone:18,hemisphere:N,easting:583959.37,northing:4507351} |
| formatted | 18N 583959E 4507351N |
| datum | WGS84 |
Response Structure
All API responses follow a consistent structure with the following fields:
| Field | Type | Description | Example |
|---|---|---|---|
status | string | Indicates whether the request was successful ("ok") or failed ("error") | ok |
error | string | null | Contains error message if status is "error", otherwise null | null |
data | object | null | Contains the API response data if successful, otherwise null | {...} |
Learn more about response formats →
Response Data Fields
When the request is successful, the data object contains the following fields:
| Field | Type | Sample Value | Description |
|---|---|---|---|
conversion | string | Type of conversion performed (UTM to lat/lon) | |
input | object | - | |
â”” latitude | number | Input latitude coordinate value | |
â”” longitude | number | Input longitude coordinate value | |
output | object | - | |
â”” zone | number | UTM zone number (1-60) for converted coordinates | |
â”” hemisphere | string | Hemisphere designation (N for north, S for south) | |
â”” easting | number | UTM easting coordinate in meters | |
â”” northing | number | UTM northing coordinate in meters | |
formatted | string | Human-readable formatted lat/lon string | |
datum | string | Geodetic datum used (WGS84) |
Headers
Only X-API-Key is required. Optional headers include Accept for response format negotiation (JSON, XML, or YAML), User-Agent, and X-Request-ID for request tracing. See all request headers →
GraphQL AccessALPHA
Access UTM Coordinate Converter through GraphQL to combine it with other API calls in a single request. Query only the utm coordinate converter data you need with precise field selection, and orchestrate complex data fetching workflows.
Credit Cost: Each API called in your GraphQL query consumes its standard credit cost.
POST https://api.apiverve.com/v1/graphqlquery {
utmconverter(
input: {
direction: "to_utm"
latitude: 40.7128
longitude: -74.006
}
) {
conversion
input {
latitude
longitude
}
output {
zone
hemisphere
easting
northing
}
formatted
datum
}
}Note: Authentication is handled via the x-api-key header in your GraphQL request, not as a query parameter.
CORS Support
The UTM Coordinate Converter API accepts cross-origin requests from any origin, so it can be called directly from browser-based applications without a proxy. See CORS support →
Rate Limiting
UTM Coordinate Converter requests are throttled per minute on the Free plan and unthrottled on paid plans. Exceeding the limit returns 429 Too Many Requests; rate-limit usage is reported in the X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset response headers. See per-plan limits and best practices →
Error Codes
The UTM Coordinate Converter API uses standard HTTP status codes — 200 on success, 400 for invalid parameters, 401 for missing or invalid keys, 403 for insufficient credits, 429 for rate-limit exhaustion, and 500/503 for server-side issues. Each error response includes an X-Request-ID header you can quote when contacting support. See full error handling guide →
SDKs for UTM Coordinate Converter
Official UTM Coordinate Converter packages on npm, PyPI, NuGet, and JitPack — plus a Postman collection and an OpenAPI spec. See the SDK guide →
No-Code Integrations
UTM Coordinate Converter works with Zapier, Make, Pipedream, n8n, and Power Automate using the same API key. See setup guides →
Frequently Asked Questions
How do I get an API key for UTM Coordinate Converter?
How many credits does UTM Coordinate Converter cost?
Each successful UTM Coordinate Converter API call consumes credits based on plan tier. Check the pricing section above for the exact credit cost. Failed requests and errors don't consume credits, so you only pay for successful utm coordinate converter lookups.
Can I use UTM Coordinate Converter in production?
The free plan is for testing and development only. For production use of UTM Coordinate Converter, upgrade to a paid plan (Starter, Pro, or Mega) which includes commercial use rights, no attribution requirements, and guaranteed uptime SLAs. All paid plans are production-ready.
Can I use UTM Coordinate Converter from a browser?
What happens if I exceed my UTM Coordinate Converter credit limit?
When you reach your monthly credit limit, UTM Coordinate Converter API requests will return an error until you upgrade your plan or wait for the next billing cycle. You'll receive notifications at 80% and 95% usage to give you time to upgrade if needed.








