UTM Coordinate ConverterUTM Coordinate Converter API

OnlineCredit Usage:1 per callRefreshed 1 month ago
avg: 278ms|p50: 263ms|p75: 288ms|p90: 318ms|p99: 378ms

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

URL
https://api.apiverve.com/v1/utmconverter

Example

How to call the UTM Coordinate Converter API in different programming languages.

cURL Request
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"
JavaScript (Fetch API)
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);
Python (Requests)
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)
Go (net/http)
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))
}
Example 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"
  }
}

Authentication

The UTM Coordinate Converter API requires authentication via API key. Include your API key in the request header:

Required Header
X-API-Key: your_api_key_here

Learn more about authentication →

Interactive 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

ParameterTypeRequiredDescriptionDefaultExample
directionstringoptional
Conversion direction
Supported values: to_utmfrom_utm
to_utmto_utm
latitudenumberrequired
Latitude (-90 to 90)
Range: -90 - 90
-40.7128
longitudenumberrequired
Longitude (-180 to 180)
Range: -180 - 180
--74.006

Option 2: UTM to Lat/Long

ParameterTypeRequiredDescriptionDefaultExample
directionstringoptional
Conversion direction
Supported values: to_utmfrom_utm
to_utmfrom_utm
zoneintegerrequired
UTM zone (1-60)
-18
eastingnumberrequired
UTM easting coordinate
-585628
northingnumberrequired
UTM northing coordinate
-4511322
hemispherestringrequired
Hemisphere (N or S)
-N

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 Response
200 OK
<?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>
YAML Response
200 OK
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
CSV Response
200 OK
keyvalue
conversionlat/lon to UTM
input{latitude:40.7128,longitude:-74.006}
output{zone:18,hemisphere:N,easting:583959.37,northing:4507351}
formatted18N 583959E 4507351N
datumWGS84

Response Structure

All API responses follow a consistent structure with the following fields:

FieldTypeDescriptionExample
statusstringIndicates whether the request was successful ("ok") or failed ("error")ok
errorstring | nullContains error message if status is "error", otherwise nullnull
dataobject | nullContains 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:

FieldTypeSample ValueDescription
conversionstring"lat/lon to UTM"
Type of conversion performed (UTM to lat/lon)
inputobject{...}
-
â”” latitudenumber40.7128
Input latitude coordinate value
â”” longitudenumber-74.006
Input longitude coordinate value
outputobject{...}
-
â”” zonenumber18
UTM zone number (1-60) for converted coordinates
â”” hemispherestring"N"
Hemisphere designation (N for north, S for south)
â”” eastingnumber583959.37
UTM easting coordinate in meters
â”” northingnumber4507351
UTM northing coordinate in meters
formattedstring"18N 583959E 4507351N"
Human-readable formatted lat/lon string
datumstring"WGS84"
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.

Test UTM Coordinate Converter in the GraphQL Explorer to confirm availability and experiment with queries.

Credit Cost: Each API called in your GraphQL query consumes its standard credit cost.

GraphQL Endpoint
POST https://api.apiverve.com/v1/graphql
GraphQL Query Example
query {
  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?
Sign up for a free account at dashboard.apiverve.com. Your API key will be automatically generated and available in your dashboard. The same key works for UTM Coordinate Converter and all other APIVerve APIs. The free plan includes 1,000 credits plus a 500 credit bonus.
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?
Yes! The UTM Coordinate Converter API supports CORS with wildcard configuration, so you can call it directly from browser-based JavaScript without needing a proxy server. See the CORS section above for details.
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.

What's Next?

Continue your journey with these recommended resources

Was this page helpful?