Skip to content

Place Details

Use /v1/place to expand one or more Pelias gid values into full feature documents. This is the best way to refresh stale metadata, enrich stored IDs, or join autocomplete selections with authoritative attributes.

Try it: GET /place
NameRequiredDescription
idsYesComma separated list of Pelias global identifiers. Each value must use the source:layer:id format (for example openstreetmap:venue:way/5013364).
categoriesNoSet to any value to include category metadata in the response.
  • Pass multiple gid values in a single request to batch lookups (for example ids=wof:locality:101750367,openaddresses:address:us/ny/city_of_new_york:123).
  • Persist the returned properties.source, properties.source_id, and geometry so you can reconcile records when datasets refresh.
  • Call /place after search or autocomplete to obtain category arrays, hierarchy data, and provider-specific metadata (properties.addendum).
Terminal window
curl -s -G 'https://api-na.geobridge.io/v1/place' \
-H 'Accept: application/json' \
-H "X-API-Key: ${GEOBRIDGE_API_KEY}" \
--data-urlencode 'ids=openstreetmap:venue:way/5013364'

The response is a GeoJSON FeatureCollection where each feature corresponds to one requested gid. Categories are omitted unless you set the categories parameter. Additional metadata appears inside properties.addendum using provider-specific keys.

  • Invalid identifier formats or missing ids parameters return HTTP 400.
  • Unknown gid values yield HTTP 404 with an empty feature list.
  • Treat HTTP 5xx responses as transient and retryable.