Tiles API
Serve uploaded vector or raster tilesets through TileJSON endpoints for web maps.
This section covers the delivery surface of our Tiles API and shows how uploaded tilesets are served through TileJSON, vector tiles, and raster tiles endpoints. If you already have an MBTiles or PMTiles file, start with Host MBTiles or Host PMTiles with Mappinest.
A single uploaded tileset can expose a TileJSON document plus vector and raster tile endpoints, all tied to the same tileset Identifier. That makes the same tileset usable across web maps, desktop GIS tools, and any integration that consumes tiles through plain URLs.
Use this section when you need concrete endpoint patterns, accepted response formats, and caching behavior. It also explains how uploaded data moves from Upload Data into production-ready delivery.
If your starting point is a map style rather than your own tileset, begin with the Map Styles API instead.
Next steps
Overview
Start here to understand TileJSON, vector tiles, raster tiles, and the shared XYZ endpoint pattern.
Host MBTiles
Use Mappinest to upload MBTiles and turn them into production tile delivery URLs.
Host PMTiles
Use Mappinest to upload PMTiles and expose them through standard tile delivery URLs.
TileJSON
Reference and integration guide for the Mappinest TileJSON endpoint.
Vector Tiles API
Endpoint reference for serving uploaded tilesets as vector PBF tiles.
Raster Tiles API
Endpoint reference for serving uploaded tilesets as raster XYZ tiles.