docs/api reference/Geocode + County Resolve
Home ↗
GET/api/geocode

Geocode + County Resolve

Converts a Texas address into coordinates and county using a Census Bureau Nominatim chain with a ZIP centroid fallback. Use this as a first step when you need lat/lon to pass into /api/property, /api/property/neighbors, or the FEMA flood endpoint.

Parameters

qstringrequired

Address or location query. Include city, state, or ZIP for best accuracy.

How to use

curl -G https://api.parcelkit.us/api/geocode \
  -H "x-api-key: sk_live_your_key" \
  --data-urlencode "q=10 Woodborough Way, Spring, TX 77389"
response.json
{
  "address": "10 Woodborough Way, Spring, TX 77389",
  "lat": 30.10744,
  "lon": -95.53443,
  "county": "Harris County",
  "city": "Spring",
  "state": "Texas",
  "zip": "77389",
  "method": "nominatim"
}
# 1. Geocode the address
curl -G https://api.parcelkit.us/api/geocode \
  -H "x-api-key: sk_live_your_key" \
  --data-urlencode "q=10 Woodborough Way, Spring, TX 77389"

# 2. Use lat/lon in the property call to skip re-geocoding
curl -G https://api.parcelkit.us/api/property \
  -H "x-api-key: sk_live_your_key" \
  --data-urlencode "address=10 Woodborough Way, Spring, TX 77389" \
  --data-urlencode "county=Harris" \
  --data-urlencode "lat=30.10744" \
  --data-urlencode "lon=-95.53443"

Most property endpoints run geocoding internally — you only need to call /api/geocode explicitly when building multi-step workflows where you want to reuse the same coordinates across several calls, or when you need the county name before deciding which endpoint to hit.