GET/v1/boundaries

API key required, sent as Authorization: Bearer snk_… or ?api_key=snk_….

Call it

bash

curl -fsS -X GET "https://api.mapmap.ai/v1/boundaries" \
  -H "Authorization: Bearer $MAPMAP_KEY"

Parameters

Name	In	Required	Description
q	query	no	A name, matched word by word from the start of each word, case and accents folded: `camden` finds "London Borough of Camden", `mosc` finds "Москва" by its English name. Searches `name`, `name:en`, the alternative names and the ISO code
near	query	no	`lat,lon`. With `q`, the nearest match first (distance to its box, 0 inside it). Without `q`, exactly the boundaries whose polygon contains the point, coarsest level first
level	query	no	OSM admin_level(s) to keep, 2 to 10, comma separated: 2 country, 4 region or federal subject, 5 to 8 county, district or borough, 9 and 10 parish or municipal district (the meaning of a level varies by country)
country	query	no	ISO 3166-1 alpha-2 country to keep
limit	query	no	Candidates, 1 to 50 (default 10)

Responses

200

{boundaries: [{boundary_id, name, name_en, admin_level, country, iso_code, area_km2, bbox, territory, contains_near?, distance_km?}], attribution, licence}

. area_km2 is the area of the stored, simplified polygon: the figure a custom region by this boundary is limited on. An empty list is a valid answer

400Neither q nor near, or a malformed parameter

401Missing or invalid API key

429Quota or rate limit exceeded

501Boundaries by name not enabled (SN_BOUNDARIES_DIR unset)

Error bodies follow the shared problem model documented on API conventions.

Also under boundaries

GET /boundary GET /v1/boundaries/{id}

Generated from https://api.mapmap.ai/openapi.json on 2026-10-31 · operationId get_boundaries