---
title: "`GET /tiles/{territory}/tiles.json`: a TileJSON 3.0 document."
method: GET
path: "/tiles/{territory}/tiles.json"
tags: ["tiles"]
---

# \`GET /tiles/{territory}/tiles.json\`: a TileJSON 3.0 document.

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

## Request

- Base URL: `https://api.mapmap.ai`
- URL: `https://api.mapmap.ai/tiles/{territory}/tiles.json`
- Auth: one of:
  - HTTP bearer
  - API key in query parameter `api_key`

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.

## Path parameters

- `territory` string, required

## Response `200`

TileJSON 3.0 document

## Other responses

- `404`: Tiles not configured or unknown territory

---

[API](https://skmtc.dev/mapmap/apis/sn-gateway.md) · [All operations](https://skmtc.dev/mapmap/apis/sn-gateway/llms.txt) · [OpenAPI document](https://skmtc.dev/mapmap/apis/sn-gateway/revisions/2293be8b4c38?raw)