<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <id>https://docs.mountaya.com/en/changelog/</id>
  <title>Mountaya changelog</title>
  <subtitle>What changed across the Mountaya platform APIs, Map Publishing, Map Studio and the tools built on them.</subtitle>
  <link rel="self" type="application/atom+xml" href="https://docs.mountaya.com/changelog.xml" />
  <link rel="alternate" type="text/html" href="https://docs.mountaya.com/en/changelog/" />
  <updated>2026-09-25T00:00:00Z</updated>
  <author>
    <name>Mountaya</name>
  </author>
  <entry>
    <id>https://docs.mountaya.com/en/changelog/2026-09-25/</id>
    <title>One contract for every credential</title>
    <link rel="alternate" type="text/html" href="https://docs.mountaya.com/en/changelog/2026-09-25/" />
    <published>2026-09-25T00:00:00Z</published>
    <updated>2026-09-25T00:00:00Z</updated>
    <category term="map-studio-api" label="Map Studio API" />
    <category term="tile-api" label="Tile API" />
    <category term="data-api" label="Data API" />
    <category term="map-publishing" label="Map Publishing" />
    <category term="map-studio" label="Map Studio" />
    <category term="mcp-server" label="MCP server" />
    <summary>Keys are pinned to their organization, zones get names and open to every account, and every API answers the same way about what a credential can see.</summary>
    <content type="html">&lt;p&gt;Keys are pinned to their organization, zones get names and open to every account, and every API answers the same way about what a credential can see.&lt;/p&gt;&lt;ul&gt;&lt;li&gt;&lt;strong&gt;Changed&lt;/strong&gt; (Map Studio API): The five merge operations are &lt;code&gt;PATCH&lt;/code&gt;: &lt;code&gt;patchItinerarySegment&lt;/code&gt;, &lt;code&gt;patchItinerarySegmentGroup&lt;/code&gt;, &lt;code&gt;patchItineraryWaypoint&lt;/code&gt;, &lt;code&gt;patchOrganizationPublishableKey&lt;/code&gt; and &lt;code&gt;patchOrganizationBillingInfo&lt;/code&gt; replace the &lt;code&gt;put*&lt;/code&gt; operations on the same paths, and an omitted field keeps its value. &lt;code&gt;PUT&lt;/code&gt; is no longer routed there. Adding a payment method is &lt;code&gt;POST /v1/organizations/{organization_id}/billing/payment-methods&lt;/code&gt;, beside the listing, rather than &lt;code&gt;.../billing/payment-method&lt;/code&gt;.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Changed&lt;/strong&gt; (Map Studio API, Tile API, Data API, Map Publishing): Every REST enum member is kebab-case: lowercase words joined by hyphens, such as &lt;code&gt;past-due&lt;/code&gt;, &lt;code&gt;per-time&lt;/code&gt; or &lt;code&gt;hiking-and-trail&lt;/code&gt;. The only enums spelled otherwise are the few whose spelling belongs to someone else: the dotted collaboration event names, the Data API&apos;s own field names in a usage report, media types, unit symbols and the GeoJSON object types. An enum the GraphQL API declares too maps to its REST member by one transform, with no exception: lowercase the SDL member and turn each underscore into a hyphen, so &lt;code&gt;HIKING_AND_TRAIL&lt;/code&gt; is &lt;code&gt;hiking-and-trail&lt;/code&gt;. The embed URL&apos;s &lt;code&gt;activity&lt;/code&gt; parameter takes the same members.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Changed&lt;/strong&gt; (Map Studio API, Tile API, Data API): A publishable key is pinned to its own organization. Every create, every write and every &lt;code&gt;/v1/organizations/{organization_id}/...&lt;/code&gt; operation must target the key&apos;s organization: any other organization id is a &lt;code&gt;403&lt;/code&gt;, whether or not it exists, decided before anything is looked up. An omitted &lt;code&gt;organization_id&lt;/code&gt; means the key&apos;s organization, including on &lt;code&gt;postItineraryDuplicate&lt;/code&gt;, where it used to mean the source&apos;s. &lt;code&gt;getItineraries&lt;/code&gt; without &lt;code&gt;organization_id&lt;/code&gt; lists the key&apos;s organization&apos;s itineraries rather than an empty page. A key never creates, lists or edits a personal resource.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Changed&lt;/strong&gt; (Map Studio API): Five reads act as a member and require &lt;code&gt;X-User-Id&lt;/code&gt;: &lt;code&gt;getAgentRunEvents&lt;/code&gt;, &lt;code&gt;getItineraryEvents&lt;/code&gt;, &lt;code&gt;getZoneEvents&lt;/code&gt;, &lt;code&gt;getOrganizationItinerariesEvents&lt;/code&gt; and &lt;code&gt;getUserOrganizations&lt;/code&gt;. A missing or malformed header is a &lt;code&gt;400&lt;/code&gt;, and a user who is not an active member is a &lt;code&gt;403&lt;/code&gt;; any role passes. The three collaboration streams used to refuse every key, and &lt;code&gt;getUserOrganizations&lt;/code&gt; now returns the acting member&apos;s own membership in the key&apos;s organization. A user whose invitation is still pending may be the &lt;code&gt;X-User-Id&lt;/code&gt; of those two operations only: &lt;code&gt;getUserOrganizations&lt;/code&gt; shows them the invitation, and &lt;code&gt;putOrganizationMemberInvitation&lt;/code&gt; accepts or declines it with a key.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Fixed&lt;/strong&gt; (Map Studio API, Tile API, Data API): A resource the credential cannot view answers &lt;code&gt;404&lt;/code&gt; exactly like one that does not exist, where it used to answer &lt;code&gt;403&lt;/code&gt;; one it can view but not edit still answers &lt;code&gt;403&lt;/code&gt;. That covers itineraries, zones, collections, another organization&apos;s publishable key, a share token used outside what it grants, and the Data API &lt;code&gt;itinerary&lt;/code&gt; query. An agent run started by somebody else or in another organization is a &lt;code&gt;404&lt;/code&gt; like an unknown one, and &lt;code&gt;postAgentRunFeedback&lt;/code&gt; on an unknown run is a &lt;code&gt;404&lt;/code&gt; rather than a &lt;code&gt;202&lt;/code&gt;.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Changed&lt;/strong&gt; (Map Studio API, Tile API, Data API, Map Publishing): Another organization&apos;s public itinerary is served as it was last published, whatever the credential, a session token included; one never published answers &lt;code&gt;404&lt;/code&gt;. Drafts are served only to the organization that owns them. &lt;code&gt;Cache-Control: public&lt;/code&gt; is sent only on the published snapshot of a public itinerary read with a key; drafts, private itineraries, zones, collections and share-token reads are &lt;code&gt;private&lt;/code&gt;, error responses carry no caching label, and every labelled response names &lt;code&gt;X-API-Key&lt;/code&gt;, &lt;code&gt;X-Session-Token&lt;/code&gt; and &lt;code&gt;X-Share-Token&lt;/code&gt; in &lt;code&gt;Vary&lt;/code&gt; beside &lt;code&gt;Origin&lt;/code&gt;.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Changed&lt;/strong&gt; (Map Studio API, Tile API, Map Studio): A share link belongs to an organization. A link to a personal itinerary or collection no longer resolves and answers &lt;code&gt;401&lt;/code&gt; like a disabled link, and none can be minted or rotated. A collection link of an organization whose Map Studio subscription is missing, paused or ended answers &lt;code&gt;401&lt;/code&gt; like an itinerary link, rather than serving the collection without its itineraries.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Added&lt;/strong&gt; (Map Studio API, Map Studio, Tile API, Data API): Zones have a name: required on create, 2 to 30 characters once trimmed, and unique within the organization, where a taken name is a &lt;code&gt;409&lt;/code&gt; naming the zone that holds it. A zone&apos;s area is a single Polygon, and any other geometry is a &lt;code&gt;400&lt;/code&gt; at &lt;code&gt;geojson.geometry&lt;/code&gt;. The feature &lt;code&gt;id&lt;/code&gt; is optional on create, and a read returns the zone&apos;s id with empty &lt;code&gt;properties&lt;/code&gt;. The Data API &lt;code&gt;search&lt;/code&gt; matches zones by name, and the zone tile specifications no longer carry a &lt;code&gt;points&lt;/code&gt; layer.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Changed&lt;/strong&gt; (Map Studio, Map Studio API): Zones are open to every account. A personal account creates and edits zones whether or not it belongs to an organization, and no plan capability gates them. Publishing, share links, embedding, export and video remain what an organization&apos;s subscription pays for.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Changed&lt;/strong&gt; (Map Studio API, Data API, Tile API): A personal resource carries &lt;code&gt;organization_id: null&lt;/code&gt; on every read, collaboration event and tile feature. A &lt;code&gt;description&lt;/code&gt; reads &lt;code&gt;null&lt;/code&gt; when there is none, is omitted on create for none, and is cleared on update by &lt;code&gt;null&lt;/code&gt; or a value that trims to nothing. &lt;code&gt;updated_at&lt;/code&gt; is always set on itineraries, collections, zones and organizations.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Changed&lt;/strong&gt; (Map Studio API, Map Studio): A waypoint in &lt;code&gt;poi&lt;/code&gt; mode needs a name, 2 to 30 characters, and clearing one is a &lt;code&gt;400&lt;/code&gt;; a &lt;code&gt;point&lt;/code&gt; may stay unnamed and keeps the icon it is given. Every icon of the published list is accepted. Import previews report &lt;code&gt;recommendation_reason&lt;/code&gt; and &lt;code&gt;warnings&lt;/code&gt; as closed codes (&lt;code&gt;route-failed&lt;/code&gt;, &lt;code&gt;directions-unsupported&lt;/code&gt;, &lt;code&gt;route-deviates&lt;/code&gt;, &lt;code&gt;off-trail&lt;/code&gt;; &lt;code&gt;track-empty&lt;/code&gt;, and &lt;code&gt;waypoints-truncated&lt;/code&gt; when a preview proposes the first 5,000 waypoints of a file holding more) rather than message keys, and name every proposal within 2 to 30 characters, so a proposal confirms as it stands. An organization drafts, imports and previews without a ceiling on the number of its itineraries.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Removed&lt;/strong&gt; (Map Studio API, MCP server): &lt;code&gt;postSession&lt;/code&gt; no longer takes a &lt;code&gt;surface&lt;/code&gt;: a caller mints sessions for the APIs, and only Mountaya&apos;s MCP server mints the sessions it uses. A session bound to the MCP server is refused with &lt;code&gt;401&lt;/code&gt; on the Map Studio and Tile APIs.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Fixed&lt;/strong&gt; (Map Studio API): &lt;code&gt;postSession&lt;/code&gt; answers &lt;code&gt;401&lt;/code&gt; for an unknown, revoked or malformed secret key, where it used to answer &lt;code&gt;404&lt;/code&gt;. A failure while checking any credential is an opaque &lt;code&gt;500&lt;/code&gt; (&lt;code&gt;504&lt;/code&gt; when the request&apos;s time budget ran out), never a &lt;code&gt;401&lt;/code&gt;. Revoked publishable keys stay listed with &lt;code&gt;revoked_at&lt;/code&gt; set. A key whose scopes are all false is a &lt;code&gt;400&lt;/code&gt; on update as it already was on create, and &lt;code&gt;embedding&lt;/code&gt; turns on &lt;code&gt;tiles&lt;/code&gt; and &lt;code&gt;resources&lt;/code&gt;.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Changed&lt;/strong&gt; (Data API, MCP server): &lt;code&gt;offset&lt;/code&gt; and &lt;code&gt;total&lt;/code&gt; are removed from &lt;code&gt;geocode&lt;/code&gt;, &lt;code&gt;reverseGeocode&lt;/code&gt;, &lt;code&gt;pois&lt;/code&gt; and &lt;code&gt;search&lt;/code&gt;: nothing ever implemented them. &lt;code&gt;reverseGeocode&lt;/code&gt; reports &lt;code&gt;count&lt;/code&gt; as the number of places it returns, where it always reported 0, and &lt;code&gt;matchedField&lt;/code&gt; is always set. An operation is held to a complexity ceiling of at most four root fields, aliases included, refused as a whole with &lt;code&gt;COMPLEXITY_LIMIT_EXCEEDED&lt;/code&gt;. A missing session token is a &lt;code&gt;401&lt;/code&gt; before any &lt;code&gt;402&lt;/code&gt; or &lt;code&gt;403&lt;/code&gt;, and is never charged.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Fixed&lt;/strong&gt; (Data API, MCP server): Data API errors: an entry&apos;s &lt;code&gt;path&lt;/code&gt; is the response path and the input path is under &lt;code&gt;extensions.path&lt;/code&gt;, a multi-field refusal carries one coded entry per field and nothing else, and a failure inside a resolver answers &lt;code&gt;INTERNAL_ERROR&lt;/code&gt;. &lt;code&gt;speed&lt;/code&gt; must be positive, &lt;code&gt;analyzeGeometry&lt;/code&gt; and &lt;code&gt;terrainProfile&lt;/code&gt; take at most 10,000 positions, a &lt;code&gt;terrainGrid&lt;/code&gt; covers at most 100 km², isochrones report the values requested, matrix indices are checked, POI distances are measured to the buffered geometry, and an unreadable routing or geocoding refusal reads as a neutral sentence. An &lt;code&gt;Accept-Language&lt;/code&gt; region tag falls back to its language, on every API.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Fixed&lt;/strong&gt; (Tile API, Map Publishing): A share token draws any overlay its itinerary or collection uses, whatever the organization&apos;s overlay allowlist. The overlay timestamp window compares with the current time rather than the current hour, and &lt;code&gt;getOverlaySpecification&lt;/code&gt; applies the allowlist the tile route applies. &lt;code&gt;with_zones&lt;/code&gt; and &lt;code&gt;with_itineraries&lt;/code&gt; apply to every credential. Vector tiles are sent as &lt;code&gt;application/x-protobuf&lt;/code&gt;, a zone that fails to render in a collection tile is a &lt;code&gt;502&lt;/code&gt;, and a &lt;code&gt;405&lt;/code&gt; names the allowed methods in &lt;code&gt;Allow&lt;/code&gt;.&lt;/li&gt;&lt;/ul&gt;</content>
  </entry>
  <entry>
    <id>https://docs.mountaya.com/en/changelog/2026-08-16/</id>
    <title>Collections belong to your organization</title>
    <link rel="alternate" type="text/html" href="https://docs.mountaya.com/en/changelog/2026-08-16/" />
    <published>2026-08-16T00:00:00Z</published>
    <updated>2026-08-16T00:00:00Z</updated>
    <category term="map-studio" label="Map Studio" />
    <category term="map-studio-api" label="Map Studio API" />
    <category term="map-publishing" label="Map Publishing" />
    <summary>Collections become organization-owned and shareable by link, and the embed can target a collection directly.</summary>
    <content type="html">&lt;p&gt;Collections become organization-owned and shareable by link, and the embed can target a collection directly.&lt;/p&gt;&lt;ul&gt;&lt;li&gt;&lt;strong&gt;Changed&lt;/strong&gt; (Map Studio, Map Studio API): A collection now belongs to the organization that owns it, and every active member of that organization sees it. Previously a collection was listed only to the people individually invited to it, so two colleagues could organize the same itineraries into folders neither could see. A collection created in your personal scope stays yours alone. &lt;code&gt;role&lt;/code&gt; on a collection is now your organization role.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Added&lt;/strong&gt; (Map Studio API): &lt;code&gt;GET /v1/organizations/{organization_id}/collections&lt;/code&gt; lists an organization&apos;s collections. &lt;code&gt;GET /v1/users/{user_id}/collections&lt;/code&gt; now returns personal collections only. &lt;code&gt;GET /v1/itineraries&lt;/code&gt; accepts an optional &lt;code&gt;organization_id&lt;/code&gt; to group by that organization&apos;s collections instead of your personal ones.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Added&lt;/strong&gt; (Map Studio API, Map Studio): Collections can be shared by link. &lt;code&gt;POST /v1/collections/{collection_id}/share&lt;/code&gt; mints a read-only link, &lt;code&gt;POST .../share/rotate&lt;/code&gt; replaces it, and &lt;code&gt;DELETE .../share&lt;/code&gt; disables it: the same lifecycle itineraries already had. Unlike an itinerary link, which exposes exactly one itinerary, a collection link exposes the itineraries and zones the collection contains.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Added&lt;/strong&gt; (Map Studio API, Map Publishing): A publishable key discovers public collections. Sent without a session token, &lt;code&gt;GET /v1/organizations/{organization_id}/collections&lt;/code&gt; returns the public collections of the organization that issued the key, and every row reports &lt;code&gt;viewer&lt;/code&gt; because a key holds no membership. The key is pinned to its own organization, so asking for another answers &lt;code&gt;403&lt;/code&gt;. Private collections stay out of that listing; reaching one still takes a session token.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Fixed&lt;/strong&gt; (Map Studio API, Map Publishing): &lt;code&gt;GET /v1/users/{user_id}/collections&lt;/code&gt; is reachable with a publishable key, returning a user&apos;s public personal collections with each row reporting &lt;code&gt;viewer&lt;/code&gt;. A private collection is never listed to a publishable key; reaching one still needs a session token. A cross-user read with a session token answers &lt;code&gt;403&lt;/code&gt; rather than an empty page, so a refusal is distinguishable from an empty library.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Changed&lt;/strong&gt; (Map Studio API): Updating a collection, an itinerary or a zone is now &lt;code&gt;PATCH&lt;/code&gt; rather than &lt;code&gt;PUT&lt;/code&gt;, and every field in the body is optional: whatever you leave out keeps its current value. Previously the three disagreed: a collection update required all three fields and cleared anything omitted, an itinerary update required only the name, and a zone update required nothing, so renaming a collection meant restating its description and privacy or losing them. The paths and the field names are unchanged; send &lt;code&gt;PATCH&lt;/code&gt; and only the fields you mean to change.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Removed&lt;/strong&gt; (Map Studio API): Per-collection collaborator invitations are removed, along with &lt;code&gt;GET|POST|DELETE /v1/collections/{collection_id}/users&lt;/code&gt;, &lt;code&gt;PUT .../users/{user_id}&lt;/code&gt; and &lt;code&gt;PUT .../users/{user_id}/invitation&lt;/code&gt;. Collaboration inside an organization is organization membership; collaboration outside one is a share link. A collection role no longer grants any access to the itineraries or zones inside it.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Changed&lt;/strong&gt; (Map Publishing): &lt;code&gt;collection_id&lt;/code&gt; is now a content selector in its own right: pass it alone to embed a whole collection, or with &lt;code&gt;itinerary_id&lt;/code&gt; to open that collection focused on one itinerary. The &lt;code&gt;with_collection_itineraries&lt;/code&gt; and &lt;code&gt;with_collection_zones&lt;/code&gt; URL parameters are removed: a collection embed draws what the collection contains, and your organization&apos;s embed settings still cap which layers it may serve.&lt;/li&gt;&lt;/ul&gt;</content>
  </entry>
  <entry>
    <id>https://docs.mountaya.com/en/changelog/2026-08-12/</id>
    <title>One read path for pagination, real error codes on the Data API</title>
    <link rel="alternate" type="text/html" href="https://docs.mountaya.com/en/changelog/2026-08-12/" />
    <published>2026-08-12T00:00:00Z</published>
    <updated>2026-08-12T00:00:00Z</updated>
    <category term="map-studio-api" label="Map Studio API" />
    <category term="data-api" label="Data API" />
    <category term="mcp-server" label="MCP server" />
    <category term="docs" label="Documentation" />
    <summary>Eleven wire changes break an existing consumer: pagination metadata nests under `pagination`, Data API errors carry a real `extensions.code`, the unlimited sentinel is `null` rather than `-1`, six Data API fields are renamed, removed, or retyped, thirteen public Map Studio API operations are renamed with the `/groups` route becoming `/segment-groups`, and a filtered `search` narrows `Way.activityCompatible` to the activity it was asked about. The Map Studio API also gains a public 50-operation surface, a documented 504, and a rate limit on session exchange.</summary>
    <content type="html">&lt;p&gt;Eleven wire changes break an existing consumer: pagination metadata nests under `pagination`, Data API errors carry a real `extensions.code`, the unlimited sentinel is `null` rather than `-1`, six Data API fields are renamed, removed, or retyped, thirteen public Map Studio API operations are renamed with the `/groups` route becoming `/segment-groups`, and a filtered `search` narrows `Way.activityCompatible` to the activity it was asked about. The Map Studio API also gains a public 50-operation surface, a documented 504, and a rate limit on session exchange.&lt;/p&gt;&lt;ul&gt;&lt;li&gt;&lt;strong&gt;Changed&lt;/strong&gt; (Map Studio API): Pagination metadata moved from the flat &lt;code&gt;extensions.metadata.{limit, offset, total}&lt;/code&gt; to a nested &lt;code&gt;extensions.metadata.pagination&lt;/code&gt; object carrying the same three fields. A client still reading the flat path now reads &lt;code&gt;undefined&lt;/code&gt;. It affects the four plain list endpoints: &lt;code&gt;GET /v1/itineraries/{itinerary_id}/collections&lt;/code&gt;, &lt;code&gt;GET /v1/zones/{zone_id}/collections&lt;/code&gt;, &lt;code&gt;GET /v1/users/{user_id}/collections&lt;/code&gt;, and &lt;code&gt;GET /v1/collections/{collection_id}/users&lt;/code&gt;. &lt;code&gt;GET /v1/itineraries&lt;/code&gt; reports the same nested object beside its own &lt;code&gt;count&lt;/code&gt; and &lt;code&gt;limit&lt;/code&gt;, so one read path now serves every list endpoint whether or not it also carries domain data.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Fixed&lt;/strong&gt; (Data API, MCP server): Data API errors populate &lt;code&gt;extensions.code&lt;/code&gt;, and the message is the localized sentence alone. Both were broken together: the wrong error presenter was rendering an error&apos;s whole string form, so the message arrived as &lt;code&gt;&amp;quot;FORBIDDEN: &amp;lt;message&amp;gt; (input)&amp;quot;&lt;/code&gt; and &lt;code&gt;extensions&lt;/code&gt; arrived empty. Anything parsing that prefix to recover a code must read &lt;code&gt;extensions.code&lt;/code&gt; instead: a client that branched on the prefix will not find it, and one that branched on an absent code was treating every 402, 403, 404, 429, and 500 as a bad argument.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Changed&lt;/strong&gt; (Map Studio API): The entitlement sentinel for an unlimited dimension is &lt;code&gt;null&lt;/code&gt;, replacing &lt;code&gt;-1&lt;/code&gt;. It reads the same everywhere the value appears: an organization&apos;s &lt;code&gt;limits&lt;/code&gt; map, and the &lt;code&gt;limit&lt;/code&gt; beside the itineraries listing. A client comparing against &lt;code&gt;-1&lt;/code&gt; now never matches and treats an unlimited dimension as capped at whatever it defaults to; compare against &lt;code&gt;null&lt;/code&gt; instead. A dimension absent from the map still means no limit was granted at all, which is not the same as unlimited.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Changed&lt;/strong&gt; (Data API, MCP server): Six fields changed shape on the Data API. &lt;code&gt;Place.housenumber&lt;/code&gt; and &lt;code&gt;Isochrone.reachfactor&lt;/code&gt; are now &lt;code&gt;houseNumber&lt;/code&gt; and &lt;code&gt;reachFactor&lt;/code&gt;, spelled the way every other field in the schema is. &lt;code&gt;Place.score&lt;/code&gt; and &lt;code&gt;Way.score&lt;/code&gt; are gone: both carried the upstream geocoder&apos;s own relevance figure, which is not comparable between two responses, so rank on the order results arrive in instead. &lt;code&gt;Isochrone.center&lt;/code&gt; is nullable, because the value is forwarded verbatim from the routing provider rather than reconstructed from the origin you sent: a provider that reports no centre now reports &lt;code&gt;null&lt;/code&gt; where it used to report an empty array. &lt;code&gt;ZoneSearchResult.level&lt;/code&gt; and &lt;code&gt;mode&lt;/code&gt; are the &lt;code&gt;ZoneLevel&lt;/code&gt; and &lt;code&gt;ZoneMode&lt;/code&gt; enums rather than free-form strings, so their values arrive upper-snake-cased: &lt;code&gt;WARNING&lt;/code&gt;, &lt;code&gt;POLYGON&lt;/code&gt;, and the rest. Selecting a renamed or removed field is not a &lt;code&gt;null&lt;/code&gt; in the response: it is a validation error, &lt;code&gt;Cannot query field&lt;/code&gt;, raised before a resolver runs, so a selection set that still names one of them comes back with no data at all.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Changed&lt;/strong&gt; (Map Studio API): Every Map Studio API operation name is now derived from its path rather than chosen, so a method&apos;s name says where it goes. Thirteen public names change: the itinerary sub-resources regain the parent the path already carries, so &lt;code&gt;postSegment&lt;/code&gt; is &lt;code&gt;postItinerarySegment&lt;/code&gt;, &lt;code&gt;putWaypoint&lt;/code&gt; is &lt;code&gt;putItineraryWaypoint&lt;/code&gt;, and the segment-group trio follows the same shape. The route &lt;code&gt;/v1/itineraries/{itinerary_id}/groups&lt;/code&gt; is now &lt;code&gt;/v1/itineraries/{itinerary_id}/segment-groups&lt;/code&gt;, which is what the payloads have always called it (&lt;code&gt;SegmentGroupCreateParams&lt;/code&gt;, &lt;code&gt;ItinerarySegmentGroup&lt;/code&gt;), and the old path is gone rather than aliased. Twenty-seven console-only names changed the same way and reach no API key.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Changed&lt;/strong&gt; (Data API, MCP server): A &lt;code&gt;search&lt;/code&gt; filtered to one activity now reports &lt;code&gt;Way.activityCompatible&lt;/code&gt; as that activity alone, where it used to list every activity the way accepts. The field reports what was established rather than a catalogue: a filtered search verifies only the activity it was asked about, so naming the others would claim a routing check that never ran. Read an absent activity as unreported, not as refused. An unfiltered search is unchanged.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Added&lt;/strong&gt; (Map Studio API, Documentation): The Map Studio API has a public surface of its own: 50 operations covering itineraries, segments, waypoints, segment groups, zones, collections, and sessions, published as their own OpenAPI document and rendered as a reference in the developer portal. The console-only operations are filtered out of it, so what the reference shows is what an API key can reach.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Added&lt;/strong&gt; (Map Studio API): &lt;code&gt;POST /v1/sessions&lt;/code&gt; declares &lt;code&gt;429 Too Many Requests&lt;/code&gt;. It is now rate limited, per calling address and, on failed exchanges, per secret key: a session exchange that presents an unknown key is the one cheap way to probe for a valid one, and it was previously unbounded. A working integration mints roughly one token per four minutes per key thanks to the existing get-or-mint cache, so legitimate traffic sits far below the ceiling.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Added&lt;/strong&gt; (Map Studio API): Every public Map Studio API operation declares &lt;code&gt;504 Gateway Timeout&lt;/code&gt; with the &lt;code&gt;GATEWAY_TIMEOUT&lt;/code&gt; code. Routes run under a request time budget, and a spent budget used to surface as whichever internal error the interruption happened to produce. The restatement only ever replaces a 5xx, so an expiring deadline never turns a 404 into a 504.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Added&lt;/strong&gt; (Documentation): A page documenting the error contract both APIs share: the envelope, all sixteen codes with their statuses, where each surface puts the offending field path, and what separates a &lt;code&gt;PAYMENT_REQUIRED&lt;/code&gt; from a &lt;code&gt;CARD_REQUIRED&lt;/code&gt;.&lt;/li&gt;&lt;/ul&gt;</content>
  </entry>
  <entry>
    <id>https://docs.mountaya.com/en/changelog/2026-08-05/</id>
    <title>Know what a route crosses</title>
    <link rel="alternate" type="text/html" href="https://docs.mountaya.com/en/changelog/2026-08-05/" />
    <published>2026-08-05T00:00:00Z</published>
    <updated>2026-08-05T00:00:00Z</updated>
    <category term="data-api" label="Data API" />
    <category term="mcp-server" label="MCP server" />
    <category term="map-studio" label="Map Studio" />
    <summary>Routed results report the tollways and access-restricted ways they cross, `directions` can route around them on request, and suggestions never propose one at all.</summary>
    <content type="html">&lt;p&gt;Routed results report the tollways and access-restricted ways they cross, `directions` can route around them on request, and suggestions never propose one at all.&lt;/p&gt;&lt;ul&gt;&lt;li&gt;&lt;strong&gt;Added&lt;/strong&gt; (Data API, MCP server): Routed results now report the tollways and access-restricted ways they cross. Every &lt;code&gt;GeometryAnalysis&lt;/code&gt; carries &lt;code&gt;advisories&lt;/code&gt;, naming whether the line crosses a way that charges a toll or one restricted to owners, customers, deliveries, permit holders, or destination traffic, and where, as coordinate ranges. Permissive ways, where the owner tolerates passage, are reported but are not treated as a restriction.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Added&lt;/strong&gt; (Data API, MCP server): &lt;code&gt;directions&lt;/code&gt; accepts &lt;code&gt;avoid: [TOLLWAY, RESTRICTED_ACCESS]&lt;/code&gt; to route around those ways. It costs a second routing pass only when the first route actually crosses one. Avoidance is best-effort, so each route reports an &lt;code&gt;avoidance&lt;/code&gt; outcome: &lt;code&gt;NOT_NEEDED&lt;/code&gt;, &lt;code&gt;APPLIED&lt;/code&gt;, or &lt;code&gt;NO_ROUTE&lt;/code&gt; when the hazard could not be routed around, which usually means a waypoint sits on the way itself.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Changed&lt;/strong&gt; (Data API, MCP server): &lt;code&gt;suggestions&lt;/code&gt; never proposes a route through a tollway or an access-restricted way. There is no opt-out: when no hazard-free candidate can be generated from the given points the query fails rather than returning one that crosses something. Use &lt;code&gt;directions&lt;/code&gt; when a route should go through such a way deliberately.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Changed&lt;/strong&gt; (Map Studio): Placing a point that routes a segment through a tollway or an access-restricted way now asks first. Confirm and the point is placed; decline and the route returns to its last accepted shape. Opening a saved segment that already crosses one does not prompt; only a change you make does.&lt;/li&gt;&lt;/ul&gt;</content>
  </entry>
  <entry>
    <id>https://docs.mountaya.com/en/changelog/2026-08-02/</id>
    <title>Reshape a route after you have drawn it</title>
    <link rel="alternate" type="text/html" href="https://docs.mountaya.com/en/changelog/2026-08-02/" />
    <published>2026-08-02T00:00:00Z</published>
    <updated>2026-08-02T00:00:00Z</updated>
    <category term="map-studio" label="Map Studio" />
    <category term="map-publishing" label="Map Publishing" />
    <category term="tile-api" label="Tile API" />
    <category term="data-api" label="Data API" />
    <category term="mcp-server" label="MCP server" />
    <summary>Itineraries gain a draft and a published version, segments can be merged, split, inserted, grouped, and switched between routing engines, and itineraries can be duplicated.</summary>
    <content type="html">&lt;p&gt;Itineraries gain a draft and a published version, segments can be merged, split, inserted, grouped, and switched between routing engines, and itineraries can be duplicated.&lt;/p&gt;&lt;ul&gt;&lt;li&gt;&lt;strong&gt;Added&lt;/strong&gt; (Map Studio, Map Publishing, Tile API): Itineraries now have a draft and a published version. Editing changes only the draft, so a course can be reworked in the open; share links, embeds, and the tiles they render keep serving the last published snapshot until you publish again. An itinerary that has never been published is not reachable from a share link or an embed. Publishing is refused while a collaborator is still editing any part of the itinerary.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Added&lt;/strong&gt; (Map Studio): Segments can be reshaped after they are drawn. Merge two neighbours that share a routing engine, split one in two at a point you click on the route, or insert a new segment between two neighbours or before the first. The chain renumbers itself and stays continuous.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Added&lt;/strong&gt; (Map Studio): A segment&apos;s routing engine can be switched between smart routing and freehand. Going from freehand to smart routing snaps the drawn line to the trail network while keeping the original start and end points, and reports a clear error when the line cannot be routed.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Added&lt;/strong&gt; (Map Studio): Neighbouring segments can be collected into a group that shows a single name, color, and speed on the elevation profile. The segments themselves are untouched and stay individually editable, which suits a course that dips into a freehand line for a few hundred meters where no trail is mapped.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Added&lt;/strong&gt; (Data API, MCP server): The &lt;code&gt;itinerary&lt;/code&gt; query returns an itinerary&apos;s segment groups as &lt;code&gt;groups&lt;/code&gt;, and each segment names the group it belongs to through &lt;code&gt;groupId&lt;/code&gt;. Groups are flat rather than nested, so the ordered segment chain stays the primary structure and a run is resolved by matching the ids. An itinerary with no groups returns an empty list.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Fixed&lt;/strong&gt; (Data API, MCP server): &lt;code&gt;analyzeGeometry&lt;/code&gt; and &lt;code&gt;directions&lt;/code&gt; now return the &lt;code&gt;trailDifficultyInfo&lt;/code&gt; stretches they compute. The field was on the schema but missing from the queries the MCP server and AI agents issue, so the analysis was calculated and then dropped before it reached a caller.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Added&lt;/strong&gt; (Map Studio): Itineraries can be duplicated, optionally into another organization, choosing which segments and waypoints to carry over. The kept segments must stay a continuous run, so only the ends of the remaining route can be dropped.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Changed&lt;/strong&gt; (Map Studio): Clicking a segment on the map opens it for editing, the same as clicking its row in the list. A segment a collaborator is already editing stays inert.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Fixed&lt;/strong&gt; (Map Studio): The &lt;code&gt;mode&lt;/code&gt; field on the segment update request has been removed. It was accepted and silently ignored, so a request that set it never changed the segment&apos;s routing engine. Changing the engine is now its own operation.&lt;/li&gt;&lt;/ul&gt;</content>
  </entry>
  <entry>
    <id>https://docs.mountaya.com/en/changelog/2026-07-27/</id>
    <title>Professional trail routing</title>
    <link rel="alternate" type="text/html" href="https://docs.mountaya.com/en/changelog/2026-07-27/" />
    <published>2026-07-27T00:00:00Z</published>
    <updated>2026-07-27T00:00:00Z</updated>
    <category term="data-api" label="Data API" />
    <category term="tile-api" label="Tile API" />
    <category term="map-studio" label="Map Studio" />
    <summary>A new `PROFESSIONAL_TRAIL` activity routes off the mapped trail network, ski touring and snowshoe walking accept waypoints further from a path, and Map Studio gains a table comparing every activity.</summary>
    <content type="html">&lt;p&gt;A new `PROFESSIONAL_TRAIL` activity routes off the mapped trail network, ski touring and snowshoe walking accept waypoints further from a path, and Map Studio gains a table comparing every activity.&lt;/p&gt;&lt;ul&gt;&lt;li&gt;&lt;strong&gt;Added&lt;/strong&gt; (Data API, Tile API): &lt;code&gt;PROFESSIONAL_TRAIL&lt;/code&gt; is a new value in the &lt;code&gt;ActivitySlug&lt;/code&gt; enum, written &lt;code&gt;professionaltrail&lt;/code&gt; on the Tile and Map Studio APIs. Pass it wherever you pass an activity today: &lt;code&gt;directions&lt;/code&gt;, &lt;code&gt;suggestions&lt;/code&gt;, &lt;code&gt;isochrones&lt;/code&gt;, &lt;code&gt;matrix&lt;/code&gt;, and the activity tile endpoints.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Added&lt;/strong&gt; (Data API): Professional trail routes on the same trails as &lt;code&gt;HIKING_AND_TRAIL&lt;/code&gt; but takes the most direct line and accepts waypoints at any distance from a path, so points that sit off the mapped network return a route instead of failing as unroutable. &lt;code&gt;HIKING_AND_TRAIL&lt;/code&gt; is unchanged.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Changed&lt;/strong&gt; (Data API): &lt;code&gt;SKI_TOURING&lt;/code&gt; now accepts waypoints at any distance from a mapped path, and &lt;code&gt;SNOWSHOE_WALKING&lt;/code&gt; accepts them up to 3 km out. Both previously failed when a point sat more than roughly 400 m from a path, which rejected cols, snowfields, and other off-trail starts. Every other activity keeps the 400 m limit.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Added&lt;/strong&gt; (Map Studio): The activity picker carries a How it works link. It opens a table of every activity showing the terrain it suits, whether it routes automatically, and whether it can be drawn freehand.&lt;/li&gt;&lt;/ul&gt;</content>
  </entry>
  <entry>
    <id>https://docs.mountaya.com/en/changelog/2026-07-03/</id>
    <title>The Mountaya developer platform launches</title>
    <link rel="alternate" type="text/html" href="https://docs.mountaya.com/en/changelog/2026-07-03/" />
    <published>2026-07-03T00:00:00Z</published>
    <updated>2026-07-03T00:00:00Z</updated>
    <category term="docs" label="Documentation" />
    <category term="mcp-server" label="MCP server" />
    <category term="map-studio" label="Map Studio" />
    <category term="map-publishing" label="Map Publishing" />
    <category term="data-api" label="Data API" />
    <summary>A new developer portal, an MCP server for AI agents, a visual embedding builder in Map Studio, and self-serve onboarding bring the whole platform together.</summary>
    <content type="html">&lt;p&gt;A new developer portal, an MCP server for AI agents, a visual embedding builder in Map Studio, and self-serve onboarding bring the whole platform together.&lt;/p&gt;&lt;ul&gt;&lt;li&gt;&lt;strong&gt;Added&lt;/strong&gt; (Documentation): A new developer portal with guides, the Data API playground, the Map Studio API reference, the Tile API reference, and a Markdown copy of every page for AI tools.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Added&lt;/strong&gt; (MCP server): An MCP server that gives AI assistants the read-only Data API as tools, over an OAuth connector or an API key pair.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Added&lt;/strong&gt; (Map Studio, Map Publishing): A visual embedding builder in Map Studio that configures the map and hands back a ready-to-paste snippet.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Added&lt;/strong&gt; (Data API): Search now spans your own itineraries, collections, and zones alongside places, POIs, and ways, with activity-aware filtering.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Added&lt;/strong&gt; (Map Studio): Self-serve onboarding to create an organization, mint API keys, and build a first map without leaving the app.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Added&lt;/strong&gt; (Map Publishing, Map Studio): Manage embed display props and safety rules yourself, controlling what each embedded map shows and where it may load.&lt;/li&gt;&lt;/ul&gt;</content>
  </entry>
</feed>
