The APIs

Eight endpoints under https://api.mygeocode.com/v1/. Each takes query parameters on a GET request and returns JSON. They share one quota, one set of error codes and one price.

Forward Geocoding API

GET /v1/forward

Send an address, a place name or a rough description and get coordinates, a cleaned up address and each of its parts.

Details and examples

Reverse Geocoding API

GET /v1/reverse

Send a latitude and longitude and get the nearest address, with the city, region, postcode and country broken out.

Details and examples

Address Autocomplete API

GET /v1/autocomplete

Suggest addresses while someone types. Every suggestion comes with coordinates, so you rarely need a second call.

Details and examples

IPv4 Lookup API

GET /v1/ipv4

Country, region, city, coordinates, timezone and network owner for any IPv4 address, or for the caller if you leave it out.

Details and examples

IPv6 Lookup API

GET /v1/ipv6

The same details for IPv6 addresses, plus the announced prefix the address belongs to.

Details and examples

Timezone Lookup API

GET /v1/timezone

IANA timezone name, UTC offset, DST status and local time for any coordinate, now or at a timestamp you choose.

Details and examples

Elevation Lookup API

GET /v1/elevation

Height above sea level in metres for one point, or up to 100 points in a single call.

Details and examples

Postal Code Lookup API

GET /v1/postcode

Turn a postal code into a place name, region and coordinates. Works for ZIP codes, postcodes and their equivalents in most countries.

Details and examples

What they have in common

Same envelope

Every response has a top-level status of ok or error. Errors carry a machine-readable code and a sentence you can log. Coordinates are always decimal degrees in lat and lon.

Same access rules

No key needed for 2,500 requests a day per IP. Whitelist your servers or use a key to go past that. Keys are capped at two IPs per 24 hours. See authentication.

Same price

A reverse geocode costs the same as an IP lookup: nothing for the first 2,500 a day, with no account, then $0.001 each from prepaid credits, or €50 a month for unlimited. See pricing.

What counts as one request

Almost everything is one call, one request. The exceptions are batch calls, where each item in the batch counts on its own.

Endpoint	Counts as
Forward geocoding, reverse geocoding, postal code lookup	1 request per call, regardless of how many results come back
Address autocomplete	1 request per call. Debounce keystrokes in your client; the SDKs will do this for you
IPv4 and IPv6 lookup	1 request per call, or 1 per address in a batch
Timezone lookup	1 request per call
Elevation lookup	1 request per point. A call with 20 points counts as 20
Drop-in hosts (Google, Bing, HERE and others)	Same rules as the endpoint they are backed by
JavaScript drop-ins: map loads and tiles	0. Only geocoder, autocomplete and elevation calls count

Not here yet

Routing, distance matrices and isochrones are not part of the service and are not planned for this year. Points of interest search by category is under consideration. If you need one of these to switch, say so; it helps us decide what to build next.