UTM Coordinate Converter API Reference

Overview

Perfect for GIS applications, mapping systems, and any application that needs to work with both coordinate systems interchangeably.

Endpoint

One host, one path per API. The block below shows this call in four languages; every one of them is the same HTTP request. Making requests covers the timeouts, retries and parameter rules that apply to all of them. The SDKs wrap the same call in a typed client.

GEThttps://api.apiverve.com/v1/utmconverter

curl "https://api.apiverve.com/v1/utmconverter?direction=to_utm&latitude=40.7128&longitude=-74.006" \
  -H "x-api-key: your_api_key_here"

const res = await fetch('https://api.apiverve.com/v1/utmconverter?direction=to_utm&latitude=40.7128&longitude=-74.006', {
  headers: { 'x-api-key': 'your_api_key_here' },
});

if (!res.ok) throw new Error(`${res.status} ${await res.text()}`);

const { data } = await res.json();
console.log(data);

import requests

res = requests.get(
    "https://api.apiverve.com/v1/utmconverter?direction=to_utm&latitude=40.7128&longitude=-74.006",
    headers={"x-api-key": "your_api_key_here"},
    timeout=15,
)
res.raise_for_status()

print(res.json()["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")

	res, err := http.DefaultClient.Do(req)
	if err != nil {
		panic(err)
	}
	defer res.Body.Close()

	out, _ := io.ReadAll(res.Body)
	fmt.Println(string(out))
}

Replace your_api_key_here with the key from your dashboard. When the inputs arrive as a list rather than one at a time, batch requests run up to 200 of them through this same API in a single call.

Authentication

Send your key in the x-api-key header. That is the only auth step — there is no token exchange and no per-endpoint scope to configure. Authentication covers creating, rotating and revoking keys.

401 is the only auth verdict

A 401 means the key is missing, invalid or expired. A 403 means the key is valid but not permitted here — blocked by a key restriction or an IP allow-list. Running out of credits is a 429.

Parameters

Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them.

Parameter	Type	Description
`direction`Optional	string	Conversion direction `to_utmfrom_utm` default to_utm
`latitude`Required	number	Latitude (-90 to 90) range -90–90
`longitude`Required	number	Longitude (-180 to 180) range -180–180

Response

Every API returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape. Response format covers the envelope, the other output formats and how premium fields are withheld.

Sample 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"
  }
}

Response fields

Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.

Field	Type	Example	Description
`conversion`	string	`"lat/lon to UTM"`	Type of conversion performed (UTM to lat/lon)
`input`	object	`{...}`
`latitude`	number	`40.7128`	Input latitude coordinate value
`longitude`	number	`-74.006`	Input longitude coordinate value
`output`	object	`{...}`
`zone`	number	`18`	UTM zone number (1-60) for converted coordinates
`hemisphere`	string	`"N"`	Hemisphere designation (N for north, S for south)
`easting`	number	`583959.37`	UTM easting coordinate in meters
`northing`	number	`4507351`	UTM northing coordinate in meters
`formatted`	string	`"18N 583959E 4507351N"`	Human-readable formatted lat/lon string
`datum`	string	`"WGS84"`	Geodetic datum used (WGS84)

Errors

Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change. Error handling covers the full status list and which of them are worth retrying.

Status	Meaning	What to do
`400`	Input was rejected	Read `error`; it names the parameter.
`401`	Key missing or invalid	Check the header name and the key value.
`403`	Key valid, but not permitted	A key restriction or IP allow-list; see key scoping.
`429`	Rate limited, or out of credits	Read `error` to tell them apart; see rate limits.

Use cases

GPS Mapping: Convert GPS coordinates to UTM format for accurate mapping, navigation, and location-based services
GIS Applications: Build GIS and surveying applications with precise coordinate transformations for land management and spatial analysis
Military Systems: Transform coordinates for military applications including tactical operations, navigation systems, and mission planning
Data Processing: Support geographic data processing workflows with bidirectional UTM and latitude/longitude coordinate conversion

Other ways to use UTM Coordinate Converter

Set up UTM Coordinate Converter on APIVerve, or reach the same source a different way. Your APIVerve account and credits work on all of them — one key, one balance.

Give it to an AI agentConnect over MCP and your agent calls it as a native tool — Claude, Cursor, ChatGPT.VerveKit →Reference →

Use it in Google Sheets or ExcelA =VERVE() formula fills a column — no script, no export, recalculates in place.VerveSheets →Reference →

Ground an agent on itA cited, machine-checkable fact your model can't produce on its own.VerveContext →Reference →

UTM Coordinate Converter