Documentation menu
boundaries
GET/v1/boundaries/{id}
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/{id}" \
-H "Authorization: Bearer $MAPMAP_KEY"Parameters
| Name | In | Required | Description |
|---|---|---|---|
| id | path | yes | A boundary_id from GET /v1/boundaries, e.g. osm-r51827 |
Responses
200A GeoJSON
Feature: the stored MultiPolygon (Douglas-Peucker simplified, coordinates to 1e-6°) with the search fields plus simplification: {method, tolerance_deg, tolerance_m, vertices, source_vertices}, data_updated, licence and attribution in properties. The Feature is accepted as is as a custom region's polygon, and a cut by it equals a cut by the boundary_id400Not a boundary id
401Missing or invalid API key
404No such boundary in this deployment's data
501Boundaries by name not enabled (SN_BOUNDARIES_DIR unset)
Error bodies follow the shared problem model documented on API conventions.
Also under boundaries
Generated from https://api.mapmap.ai/openapi.json on 2026-10-31 · operationId get_boundary_by_id