Get started
All releases
Map Studio
Map Studio API
Map Publishing

Collections belong to your organization

Collections become organization-owned and shareable by link, and the embed can target a collection directly.

Changed:

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. role on a collection is now your organization role.

Added:

GET /v1/organizations/{organization_id}/collections lists an organization's collections. GET /v1/users/{user_id}/collections now returns personal collections only. GET /v1/itineraries accepts an optional organization_id to group by that organization's collections instead of your personal ones.

Added:

Collections can be shared by link. POST /v1/collections/{collection_id}/share mints a read-only link, POST .../share/rotate replaces it, and DELETE .../share 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.

Added:

A publishable key discovers public collections. Sent without a session token, GET /v1/organizations/{organization_id}/collections returns the public collections of the organization that issued the key, and every row reports viewer because a key holds no membership. The key is pinned to its own organization, so asking for another answers 403. Private collections stay out of that listing; reaching one still takes a session token.

Fixed:

GET /v1/users/{user_id}/collections is reachable with a publishable key, returning a user's public personal collections with each row reporting viewer. 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 403 rather than an empty page, so a refusal is distinguishable from an empty library.

Changed:

Updating a collection, an itinerary or a zone is now PATCH rather than PUT, 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 PATCH and only the fields you mean to change.

Removed:

Per-collection collaborator invitations are removed, along with GET|POST|DELETE /v1/collections/{collection_id}/users, PUT .../users/{user_id} and PUT .../users/{user_id}/invitation. 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.

Changed:

collection_id is now a content selector in its own right: pass it alone to embed a whole collection, or with itinerary_id to open that collection focused on one itinerary. The with_collection_itineraries and with_collection_zones URL parameters are removed: a collection embed draws what the collection contains, and your organization's embed settings still cap which layers it may serve.