GET /point?lat={lat}&lon={lon}

Point API

Pass a coordinate. Get the place and timezone it falls in.

Try it

Example response/point?lat=39.77&lon=-104.9
{
  "latitude": 39.77,
  "longitude": -104.9,
  "country": "US",
  "country_name": "United States",
  "state": "CO",
  "state_name": "Colorado",
  "district": "08031",
  "district_name": "Denver",
  "timezone": "America/Denver",
  ?deep=true
}

1M requests · $20/mo. Get started

What comes back.

country

ISO2 country code (null over open ocean)

state

State / ADM1 code

district

District code (US county FIPS, FR INSEE department, GB GSS, null elsewhere)

deep.elevation

Elevation in meters (null if unavailable)

deep.city

Compact nearest-city identity and location, including distance and distance_mi; null when no city is within 200 km

timezone

IANA timezone containing the coordinate; a nautical zone over open ocean, or null when unresolved

1

Pass lat and lon

A GPS reading, a photo, a pin on a map.

2

Get the admin

Country, state, district, and the IANA timezone. Add deep=true for terrain and a nearby city.

3

Resolve the district

FIPS, INSEE, or GSS on the district path.

Make your first request.

One key works across the APIs. Copy a request in your language and get JSON back.

curl "https://api.parseapi.com/point?lat=39.77&lon=-104.9" \
  -H "X-API-Key: YOUR_API_KEY" \
  -H "Parse-Version: 2.0.0"
// Example response · 200
{
  "latitude": 39.77,
  "longitude": -104.9,
  "country": "US",
  "country_name": "United States",
  "state": "CO",
  "state_name": "Colorado",
  "district": "08031",
  "district_name": "Denver",
  "timezone": "America/Denver"
}

API referenceSDKsKeys and authentication

Every response field

Response fields

latitudenumber
Input latitude
longitudenumber
Input longitude
countrystring or null
ISO2 country code (null over open ocean)
country_namestring or null
Country name
statestring or null
State / ADM1 code
state_namestring or null
State / ADM1 name
districtstring or null
District code (US county FIPS, FR INSEE department, GB GSS, null elsewhere)
district_namestring or null
District / ADM2 name
timezonestring or null
IANA timezone containing the coordinate; a nautical zone over open ocean, or null when unresolved

Deep fields

deep.cityobject or null
Compact nearest-city identity and location, including distance and distance_mi; null when no city is within 200 km
deep.elevationnumber or null
Elevation in meters (null if unavailable)
deep.elevation_ftnumber or null
Elevation in feet (null if unavailable)
deep.resolutionnumber or null
Approx elevation grid spacing in meters

Build with Point

All tutorials →

QUESTIONS

What do I pass?
Latitude and longitude. A GPS reading, a geotagged photo, a pin on a map.
What comes back?
Country, state, district, and the IANA timezone for the coordinate. Missing facts stay null.
Does elevation come back?
Add deep=true for elevation in meters and feet, with grid spacing in deep.resolution. Included on every plan. Ocean depth is negative.
How is this different from /elevation?
Point identifies the place and timezone, with optional terrain and nearest-city detail. Elevation answers the terrain question directly.
How do I resolve the district?
FIPS, INSEE, or GSS on the district path.
What does deep add?
Terrain elevation, resolution, and a compact nearest-city summary, included on every plan. The IANA timezone stays in the ordinary response. Use /time for local clock time.

See what time zone you are in, or what county you are in.