GET/tiles/{territory}/{z}/{x}/{y}

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

What it does

Reads the (z, x, y) tile straight from the territory PMTiles and returns its bytes with the MVT content-type, the archive's tile compression as Content-Encoding (PMTiles stores MVT gzip-compressed by convention), a strong BLAKE3 ETag and immutable cache headers.

Unknown territory, tiles not configured, out-of-range coordinates, or a bad file extension: 404.
A tile absent from the archive (in range, no data): 204 No Content; the empty-tile convention MapLibre treats as a blank tile.

Call it

bash

curl -fsS -X GET "https://api.mapmap.ai/tiles/{territory}/{z}/{x}/{y}" \
  -H "Authorization: Bearer $MAPMAP_KEY"

Parameters

Name	In	Required	Description
territory	path	yes	Territory id, e.g. `uk`
z	path	yes	Zoom level
x	path	yes	Tile column
y	path	yes	Tile row plus extension, e.g. `21.mvt` (or `.pbf`)

Responses

200One Mapbox Vector Tile

204No data for this tile (empty tile)

304Not modified (If-None-Match matched the ETag)

404Tiles not configured, unknown territory, or out-of-range tile

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

Also under tiles

GET /tiles/{territory}/style.json GET /tiles/{territory}/tiles.json

Generated from https://api.mapmap.ai/openapi.json on 2026-09-17 · operationId get_tile