My App

Migration

Move MapLibre/Mapbox-style clients to implemented Planisfy routes.

Migration

Planisfy intentionally uses familiar style, tile, and coordinate shapes, but it is not a complete Mapbox API clone.

URL Changes

NeedPlanisfy route
Style JSON/styles/v1/{owner}/{style}
Versioned style JSON/styles/v1/{owner}/{style}@{version}
TileJSON/tiles/v1/{owner}.{tileset}.json or /tiles/v1/{owner}/{tileset}.json
Vector tile/tiles/v1/{owner}.{tileset}/{z}/{x}/{y}
Tilequery/v4/{owner}.{tileset}/tilequery/{lon},{lat}.json
Style sprite/styles/v1/{owner}/{style}/sprite(.json|.png|@2x.json|@2x.png)
Glyph PBF/fonts/v1/{fontstack}/{range}.pbf
Directions/directions/v1/{profile}/{lon,lat;lon,lat}

Auth Changes

Use X-API-Key: pk_... for service APIs. Do not pass Mapbox-style access_token as the primary auth mechanism; the implemented middleware validates the X-API-Key header and session cookies.

Compatibility Limits

Tilequery is implemented for PMTiles-backed vector tilesets. Raster tilequery is not supported. Sprite routes are published only when the style references sprite assets; styles without sprite assets return 404 Sprite not configured.

On this page