Glossary
Short definitions of the terms these docs use, grouped by topic.
A key starting with pk_ that identifies your organization on every request. It is safe in a browser. See authentication.
A key starting with sk_ that mints session tokens. Keep it on your server. See authentication.
A short-lived credential starting with sess_, minted by your server and sent beside the publishable key. It lasts five minutes. See mint a session token.
A product a publishable key may open, such as data or tiles. See scopes.
Who a session token is for, set by the surface field when you mint it: your own clients by default, or an Embedded Studio. See token audience.
A request that acts as one of your members, through a session token minted with their user_id. Every write to your content does. See act as a member.
A read-only link to one itinerary or one collection, carrying a token starting with share_. See share links.
The sites that may use your publishable key from a browser and frame the hosted embed. Set them under Organization → Security. See allowed domains.
A contract with Mountaya that opens Map Publishing, Map Studio, Embedded Studio, and the Tile API. Talk to us to start one.
A product you switch on yourself by adding a card: the Data API and the MCP server. See create an account.
A trip made of segments, with waypoints between them, built for one activity. See the Map Studio API.
One leg of an itinerary between two waypoints, routed or drawn freehand.
A named point on an itinerary, such as a start, a hut, or a pass.
A named, colored run of an itinerary's segments, such as one day or one stage.
An area on the map, a single polygon with a severity level, such as an avalanche area.
Itineraries and zones grouped and shown together. A share link to a collection opens everything inside it.
You edit an itinerary or a zone as a draft. The public sees its published snapshot until you publish again. See draft and published.
The sport a route is built for, such as hiking or ski touring. It picks the routing profile and the default speed. See activities.
The map under your content: a terrain style such as summer topo, winter topo, or satellite. See the Tile API.
A layer drawn over the base map: weather, terrain shading, slopes, or points of interest. See overlays.
The area you can reach from a point within a given time. See isochrones.
Travel times and distances between many origins and destinations, in one request. See matrix.
Your published maps on your own site in an iframe, behind a share link, as a route file, or as a video. See Map Publishing.
The Mountaya map editor, mounted inside your own product with the TypeScript SDK. See Embedded Studio.
The Embedded Studio's state and actions without its interface, so you build the screens with your own design system. See headless.
The one path every change in an Embedded Studio takes. A person, an AI agent, and your own code all dispatch the same tools on it. See handlers.