GET/tiles/{territory}/tiles.json

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

What it does

The zoom range, bounds and centre come from the PMTiles header; the tile template and attribution are filled in for the client.

data_updated reports how fresh the map behind those tiles is as an ISO-8601 date (YYYY-MM-DD), and data_updated_source names which of three sources answered, weakest last:

`data_updated_source`	meaning
`channel_index`	the OSM extract date of the territory's latest published package
`archive_osm_replication`	the archive's own `planetiler:osm:osmosisreplicationtime`
`archive_mtime`	when the `.pmtiles` file was last written: a proxy for the data date, not the data date

Both are null when even the file's mtime is unreadable, and null means unknown, never "current". See territory_data_updated for why the chain has three links.

Call it

bash

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

Parameters

Name	In	Required	Description
territory	path	yes	Territory id, e.g. `uk`

Responses

200TileJSON 3.0 document

404Tiles not configured or unknown territory

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

Also under tiles

GET /tiles/{territory}/{z}/{x}/{y}GET /tiles/{territory}/style.json

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