Tile API reference
The Tile API serves base maps, overlays and your organization's content as tiles for the map you already run.
Send your publishable key in X-API-Key. A map library cannot set a header, so on the URLs it requests itself the key rides the publishable_key query parameter. Authentication covers both.
Base URL https://tiles.mountaya.com, contract v0.8.0: download the OpenAPI document.
- Layers: The layer catalog: the terrains, the elevation raster, the overlays and the itinerary and zone layers, each by its slug with the tile sources it resolves to.
- Terrains: The base maps, their sources, sprites and glyphs, and the elevation raster, served through this API so a map draws its base map under the credential it sends here.
- Overlays: Raster and vector overlays (slope, aspect, weather, points of interest) as tiles and as the specification a client needs to style and read them.
- Itineraries: Routes as vector tiles, drawn from the published snapshot or, when a session token naming a member accompanies the key, from the key's own organization's drafts, so a map draws a whole set of them without fetching each one's geometry.
- Collections: A collection's itineraries and zones as tiles, addressed by the collection rather than one resource at a time.
- Zones: Zones as vector tiles, carrying each zone's name, severity and validity window, which a client labels and styles them by.
New to the API? Start with the Tile API quickstart. Errors and rate limits work the same way everywhere: see the API conventions.