Find boundaries containing a place

Find boundaries that contain one place. Use exactly one lookup method: a Place id (recommended), a lat and lon pair, or an osm_id and osm_type pair; combining methods or giving none returns 400. Use boundaries to restrict the returned boundary types and geometry to choose representative points or simplified boundary polygons.

Data layers: administrative (OpenStreetMap admin_level 2 to 11, Nominatim placex); postal_code (Census ZCTA5 for the US, StatCan FSA for Canada); timezone (timezone-boundary-builder, place_id gp:tz:<tzid>); and OpenStreetMap polygons for neighborhood, place, region, political, historic, protected_area (includes leisure=nature_reserve), national_park (boundary=national_park, or a nature reserve named "... National Park"), aboriginal_lands, census, school_district, forest, hazard, regional_park, religious_administration, low_emission_zone, public_transport and traditional. Coverage is the US and Canada.

Deviation (empty): the types religious, municipality, barony, town, health and historic:administrative are accepted and validated but have no data layer, so they never contribute features. The response lists every requested type in layers (layer: false for these), and when any such type is requested it carries an X-Boundaries-Note header. A layer with data can still contribute nothing at a given point (layer: true, within: 0).

Deviation (extra): boundaries accepts the extra types protected_area, national_park, aboriginal_lands, census, school_district, forest, hazard and regional_park, and the special value all; there is no cap on the number of types (Geoapify allows 10). The response adds a top-level layers summary and a boundary_type property on each feature.

Deviation (extra): datasource and place_id follow our own formats (see the property docs); datasource.attribution carries the licence attribution that must be shown to end users.

Deviation (empty): Geoapify's optional descriptive fields (formatted, address_line1, address_line2, categories, name_international, name_other, website, population, and the descriptive timezone property object, ...) are never returned. (A timezone boundary feature is different: it is returned when you request boundaries=timezone.) Address fields are limited to name, continent, country, country_code, state, state_code, iso3166_2, county, county_district, city, city_district, suburb, neighbourhood, postcode, postal_code, lon, lat, place_id, datasource.

Deviation (unsupported): id accepts only Place IDs of kind gp:osm: and gp:pc:. IDs of kind gp:addr:, gp:iso: and gp:tz: (and Geoapify's hex place IDs) are not resolved and return an empty FeatureCollection with layers within 0 (malformed gp: IDs return 400). gp:tz:<tzid> appears as the place_id of timezone features but does not resolve as an id.

Not supported: none of Geoapify's parameters for this endpoint are removed; all are read.

Example: GET /boundaries/part-of?lat=39.7684&lon=-86.1581&apiKey=YOUR_API_KEY returns the administrative boundaries containing downtown Indianapolis (city, township, county, state, country).