API reference

Place lookup

Fetch one or more results again by id.

GET/v1/place

Fetch results again by their id, for example when you stored only the id after a user picked an autocomplete suggestion. Any primary result id from geocode, search, reverse geocode, or autocomplete works.

Headers

Header	Required	Value
apikey	Yes	Your primary API key, or a public browser token

Query parameters

idstringrequired

One or more result ids, separated by commas. Up to 20 ids, e.g. openaddresses:address:us/ny:1.

Request example

cURL

curl --get "$GEOCODING_BASE_URL/v1/place" \
  --header "apikey: $GEOCODING_API_KEY" \
  --data-urlencode "id=openaddresses:address:us/ny:1"

Success response

Place lookup returns the same GeoJSON format as every endpoint, with one feature per id found.

{
  "type": "FeatureCollection",
  "features": [
    {
      "type": "Feature",
      "geometry": {"type": "Point", "coordinates": [-74.0113, 40.7074]},
      "properties": {"id": "openaddresses:address:us/ny:1", "label": "11 Wall Street, New York, NY, USA", "type": "address", "...": "..."}
    }
  ]
}

Successful responses include X-Geocoding-Outcome: matched or no_match. Authentication, account rate limits, usage metering, and standard errors apply. Each successful lookup is metered separately from autocomplete. See usage and billing.

Lookup behavior

• Ids not found in the current dataset are omitted, so an unknown id returns HTTP 200 with "features": []. SDK resolution methods instead raise provider_error for an empty lookup, because they promise one address.
• Ids depend on the dataset and can change when it is updated. Store the address fields and coordinates you need, not only the id.
• The API looks up primary ids only. Use an SDK to resolve Google or HERE suggestions.