UTM Coordinate Converter API

GET

Translate coordinates between UTM zones and latitude/longitude.

UTM Coordinate Converter provides bidirectional conversion between UTM (Universal Transverse Mercator) coordinates and latitude/longitude using WGS84 datum.

Try it — live request, no key required

Request

GETapi.apiverve.com/v1/utmconverter?latitude=40.7128&longitude=-74.0060

Query parameters

latitudenumber

longitudenumber

Verification

Format

No key required to try it. Get a key to use it in your app.

Example

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

About the UTM Coordinate Converter API

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

What people use it for

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

Ways to call it

One endpoint, many ways in — REST with JSON, XML, YAML and CSV, plus GraphQL and an MCP interface for AI agents.

JSON: Default REST response
XML: Markup format
YAML: Human-readable
CSV: Tabular export
GraphQL: Query language
MCP: For AI agents

View all integrations →

Other ways to use UTM Coordinate Converter

Same data, same APIVerve account, same credit balance — one key works on all of them.

Give it to an AI agentConnect over MCP and your agent calls it as a native tool — Claude, Cursor, ChatGPT.on VerveKit Google Sheets or ExcelA =VERVE() formula fills a column — no script, no export, recalculates in place.on VerveSheets Ground an agent on itA cited, machine-checkable fact your model can't produce on its own.on VerveContext

Questions.

Common questions about the UTM Coordinate Converter API.

Read the docs →

How many coordinate conversions does the Free plan cover?

The Free plan includes 100 conversions each month at 2 credits per request. If you need higher volume, the Starter plan provides 200,000 credits to cover 100,000 monthly conversions, which works out to about $0.30 per 1,000 calls.

Which geodetic datum does the converter use?

All conversions use the standard WGS84 geodetic datum. Both conversion directions return the datum explicitly in the response to confirm the coordinate reference system used.

Does the converter support both Northern and Southern hemispheres?

Yes. All 60 UTM zones are supported across both the Northern and Southern hemispheres. When converting from UTM back to latitude and longitude, provide the hemisphere designation as N or S along with the zone number, easting, and northing.

What coordinate ranges are accepted as input?

When converting to UTM, latitude must be between -90 and 90 degrees, and longitude must be between -180 and 180 degrees. When converting from UTM to latitude and longitude, the zone parameter must be an integer between 1 and 60.

Can I convert coordinates in both directions?

Yes. The UTM Coordinate Converter supports bidirectional conversion between geographic points and UTM coordinates. You can pass latitude and longitude to get UTM zone, hemisphere, easting, northing, and formatted strings, or supply UTM values to obtain latitude and longitude.

Request parameters — GET /v1/utmconverter

Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them. Anything not listed here is dropped rather than passed through.

Required

Parameter	Type	Example	Description
`latitude`Required	number	`40.7128`	Latitude (-90 to 90) range -90-90
`longitude`Required	number	`-74.006`	Longitude (-180 to 180) range -180-180

Optional

Parameter	Type	Example	Description
`direction`Optional	string	`to_utm`	Conversion direction `to_utmfrom_utm` default to_utm

Example request

1
2

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

Authentication

Send your key in the x-api-key header. That is the only auth step — no token exchange, and no per-endpoint scope to configure.

Header	When	Value
`x-api-key`Required	Every request	Your API key. Header names are case-insensitive, so `X-API-Key` is the same header.
`Authorization`Alternate	Instead of the above	`Bearer <key>` — for clients that only expose bearer auth. Resolves to the same account and the same billing.

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.

Response — GET /v1/utmconverter

Every APIVerve endpoint returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape.

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 (lat/lon to UTM)
`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 UTM string representation
`datum`	string	`"WGS84"`	Geodetic datum used (WGS84)

Response headers

Every response carries your balance, so your own code always knows where it stands without polling anything. All four are exposed to browsers through CORS.

Header	What it carries
`x-api-remaining-credits`	Credits left in the current cycle
`x-api-credits-used`	Credits spent in the current cycle
`x-api-max-credits`	The allowance for the cycle
`x-api-version`	Version of the endpoint that answered

Errors

Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.

Status	Meaning	What to do
`400`	Input was rejected	Read `error`; it names the parameter that has to change.
`401`	Key missing or invalid	Check the header name and the key value.
`403`	Key valid, but not permitted here	A key restriction or an IP allow-list — never a bad key.
`429`	Rate limited, or out of credits	Read `error` to tell them apart, then back off or top up.

What a call costs — 2 credits per call

Credits are shared across every APIVerve API — one balance, one key, one bill. Failed requests never count against it, so a rejected input costs nothing.

Plan	Per month	Credits	UTM Coordinate Converter calls	Per 1,000 calls
Free	Free	200	100	Free
Starter	$29.99	200,000	100,000	$0.30
Pro	$99.99	1,000,000	500,000	$0.20
Mega	$299.99	4,000,000	2,000,000	$0.15

Calls are what the credits buy at this API's rate — spend them here, on any of the other APIs, or across both. Nothing is reserved per endpoint.

Compare all pricing tiers →

Call it from cURL — GET /v1/utmconverter

No SDK to install — this is a plain HTTPS call to /v1/utmconverter with your key in the x-api-key header. Swap in a real key and it runs as-is.

cURL

1
2

curl "https://api.apiverve.com/v1/utmconverter" \
  -H "x-api-key: YOUR_API_KEY"

Resources

GitHubapiverve/utmconverter-apiSource, issues and the examples this page is built from.ReferenceUTM Coordinate Converter API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/utmconverternpm APIVerve.API.UTMCoordinateConverterNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Node.js — GET /v1/utmconverter

Install the Node.js SDK, then call the UTM Coordinate Converter API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — npm

npm install @apiverve/utmconverter

Node.js

const res = await fetch("https://api.apiverve.com/v1/utmconverter", {
  headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);

Resources

npm@apiverve/utmconverterThe published Node.js client, versioned and signed.GitHubapiverve/utmconverter-apiSource, issues and the examples this page is built from.ReferenceUTM Coordinate Converter API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

APIVerve.API.UTMCoordinateConverterNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Python — GET /v1/utmconverter

No SDK to install — this is a plain HTTPS call to /v1/utmconverter with your key in the x-api-key header. Swap in a real key and it runs as-is.

Python

import requests

res = requests.get(
    "https://api.apiverve.com/v1/utmconverter",
    headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])

Resources

Also published for

@apiverve/utmconverternpm APIVerve.API.UTMCoordinateConverterNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from C# / .NET — GET /v1/utmconverter

Install the C# / .NET SDK, then call the UTM Coordinate Converter API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — NuGet

dotnet add package APIVerve.API.UTMCoordinateConverter

C# / .NET

using var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");

var json = await client.GetStringAsync("https://api.apiverve.com/v1/utmconverter");
Console.WriteLine(json);

Resources

NuGetAPIVerve.API.UTMCoordinateConverterThe published C# / .NET client, versioned and signed.GitHubapiverve/utmconverter-apiSource, issues and the examples this page is built from.ReferenceUTM Coordinate Converter API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/utmconverternpm

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Go — GET /v1/utmconverter

No SDK to install — this is a plain HTTPS call to /v1/utmconverter with your key in the x-api-key header. Swap in a real key and it runs as-is.

req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/utmconverter", nil)
req.Header.Set("x-api-key", "YOUR_API_KEY")

res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))

Resources

Also published for

@apiverve/utmconverternpm APIVerve.API.UTMCoordinateConverterNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from PHP — GET /v1/utmconverter

No SDK to install — this is a plain HTTPS call to /v1/utmconverter with your key in the x-api-key header. Swap in a real key and it runs as-is.

PHP

$ch = curl_init("https://api.apiverve.com/v1/utmconverter");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-api-key: YOUR_API_KEY"]);

$response = curl_exec($ch);
echo $response;

Resources

Also published for

@apiverve/utmconverternpm APIVerve.API.UTMCoordinateConverterNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Ruby — GET /v1/utmconverter

No SDK to install — this is a plain HTTPS call to /v1/utmconverter with your key in the x-api-key header. Swap in a real key and it runs as-is.

Ruby

require "net/http"

uri = URI("https://api.apiverve.com/v1/utmconverter")
req = Net::HTTP::Get.new(uri)
req["x-api-key"] = "YOUR_API_KEY"

res = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) { |h| h.request(req) }
puts res.body

Resources

Also published for

@apiverve/utmconverternpm APIVerve.API.UTMCoordinateConverterNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

All articles →

Extract Clean Content from Any WebpageTurn messy web pages into clean Markdown. Perfect for content migration, archiving, AI training data, and building read-later tools.Read

Take Your App Multilingual (No Rewrite)Add language support to an existing app without rearchitecting. Practical strategies for translation, detection, and localization.Read

Business Day Math Is Harder Than You ThinkWeekends, holidays, and country-specific rules make working day calculations surprisingly tricky. Here's what to watch for.Read

UTM Coordinate Converter API

Try it — live request, no key required

About the UTM Coordinate Converter API

What people use it for

Ways to call it

Other ways to use UTM Coordinate Converter

Questions.

Request parameters — GET /v1/utmconverter

Required

Optional

Authentication

Response — GET /v1/utmconverter

Response fields

Response headers

Errors

What a call costs — 2 credits per call

Call it from cURL — GET /v1/utmconverter

Resources

Also published for

Call it from Node.js — GET /v1/utmconverter

Resources

Also published for

Call it from Python — GET /v1/utmconverter

Resources

Also published for

Call it from C# / .NET — GET /v1/utmconverter

Resources

Also published for

Call it from Go — GET /v1/utmconverter

Resources

Also published for

Call it from PHP — GET /v1/utmconverter

Resources

Also published for

Call it from Ruby — GET /v1/utmconverter

Resources

Also published for

Zero-code embed — one snippet, no backend

Changelog — UTM Coordinate Converter API

Math/Calculations

Related articles

Ready to build with UTM Coordinate Converter? Start with 200 free credits — one key unlocks all 300+ APIs.

Explore the catalog