Get started
All releases
Map Studio API
Tile API
Data API
Map Publishing
Map Studio
MCP server

One contract for every credential

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.

Changed:

The five merge operations are PATCH: patchItinerarySegment, patchItinerarySegmentGroup, patchItineraryWaypoint, patchOrganizationPublishableKey and patchOrganizationBillingInfo replace the put* operations on the same paths, and an omitted field keeps its value. PUT is no longer routed there. Adding a payment method is POST /v1/organizations/{organization_id}/billing/payment-methods, beside the listing, rather than .../billing/payment-method.

Changed:

Every REST enum member is kebab-case: lowercase words joined by hyphens, such as past-due, per-time or hiking-and-trail. The only enums spelled otherwise are the few whose spelling belongs to someone else: the dotted collaboration event names, the Data API'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 HIKING_AND_TRAIL is hiking-and-trail. The embed URL's activity parameter takes the same members.

Changed:

A publishable key is pinned to its own organization. Every create, every write and every /v1/organizations/{organization_id}/... operation must target the key's organization: any other organization id is a 403, whether or not it exists, decided before anything is looked up. An omitted organization_id means the key's organization, including on postItineraryDuplicate, where it used to mean the source's. getItineraries without organization_id lists the key's organization's itineraries rather than an empty page. A key never creates, lists or edits a personal resource.

Changed:

Five reads act as a member and require X-User-Id: getAgentRunEvents, getItineraryEvents, getZoneEvents, getOrganizationItinerariesEvents and getUserOrganizations. A missing or malformed header is a 400, and a user who is not an active member is a 403; any role passes. The three collaboration streams used to refuse every key, and getUserOrganizations now returns the acting member's own membership in the key's organization. A user whose invitation is still pending may be the X-User-Id of those two operations only: getUserOrganizations shows them the invitation, and putOrganizationMemberInvitation accepts or declines it with a key.

Fixed:

A resource the credential cannot view answers 404 exactly like one that does not exist, where it used to answer 403; one it can view but not edit still answers 403. That covers itineraries, zones, collections, another organization's publishable key, a share token used outside what it grants, and the Data API itinerary query. An agent run started by somebody else or in another organization is a 404 like an unknown one, and postAgentRunFeedback on an unknown run is a 404 rather than a 202.

Changed:

Another organization's public itinerary is served as it was last published, whatever the credential, a session token included; one never published answers 404. Drafts are served only to the organization that owns them. Cache-Control: public 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 private, error responses carry no caching label, and every labelled response names X-API-Key, X-Session-Token and X-Share-Token in Vary beside Origin.

Changed:

A share link belongs to an organization. A link to a personal itinerary or collection no longer resolves and answers 401 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 401 like an itinerary link, rather than serving the collection without its itineraries.

Added:

Zones have a name: required on create, 2 to 30 characters once trimmed, and unique within the organization, where a taken name is a 409 naming the zone that holds it. A zone's area is a single Polygon, and any other geometry is a 400 at geojson.geometry. The feature id is optional on create, and a read returns the zone's id with empty properties. The Data API search matches zones by name, and the zone tile specifications no longer carry a points layer.

Changed:

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's subscription pays for.

Changed:

A personal resource carries organization_id: null on every read, collaboration event and tile feature. A description reads null when there is none, is omitted on create for none, and is cleared on update by null or a value that trims to nothing. updated_at is always set on itineraries, collections, zones and organizations.

Changed:

A waypoint in poi mode needs a name, 2 to 30 characters, and clearing one is a 400; a point may stay unnamed and keeps the icon it is given. Every icon of the published list is accepted. Import previews report recommendation_reason and warnings as closed codes (route-failed, directions-unsupported, route-deviates, off-trail; track-empty, and waypoints-truncated 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.

Removed:

postSession no longer takes a surface: a caller mints sessions for the APIs, and only Mountaya's MCP server mints the sessions it uses. A session bound to the MCP server is refused with 401 on the Map Studio and Tile APIs.

Fixed:

postSession answers 401 for an unknown, revoked or malformed secret key, where it used to answer 404. A failure while checking any credential is an opaque 500 (504 when the request's time budget ran out), never a 401. Revoked publishable keys stay listed with revoked_at set. A key whose scopes are all false is a 400 on update as it already was on create, and embedding turns on tiles and resources.

Changed:

offset and total are removed from geocode, reverseGeocode, pois and search: nothing ever implemented them. reverseGeocode reports count as the number of places it returns, where it always reported 0, and matchedField is always set. An operation is held to a complexity ceiling of at most four root fields, aliases included, refused as a whole with COMPLEXITY_LIMIT_EXCEEDED. A missing session token is a 401 before any 402 or 403, and is never charged.

Fixed:

Data API errors: an entry's path is the response path and the input path is under extensions.path, a multi-field refusal carries one coded entry per field and nothing else, and a failure inside a resolver answers INTERNAL_ERROR. speed must be positive, analyzeGeometry and terrainProfile take at most 10,000 positions, a terrainGrid 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 Accept-Language region tag falls back to its language, on every API.

Fixed:

A share token draws any overlay its itinerary or collection uses, whatever the organization's overlay allowlist. The overlay timestamp window compares with the current time rather than the current hour, and getOverlaySpecification applies the allowlist the tile route applies. with_zones and with_itineraries apply to every credential. Vector tiles are sent as application/x-protobuf, a zone that fails to render in a collection tile is a 502, and a 405 names the allowed methods in Allow.