TypeScript SDK
Typed packages for the Mountaya platform. Read itineraries, render them on a map, and edit them, in a browser or on a server.
The SDK ships on npm under the @mountaya scope, from one repository released together.
One family talks to the platform. It builds every request, holds your credential, and hands back typed data. The other family draws that data on a map and fetches nothing for you. Feed it from your cache, your store, or a payload you rendered on a server.
Install sets up the packages, the stylesheet, and the provider the React components read. Every page after it assumes you did that once.
What you can build
Fetch data
Call the three APIs through one typed client, with hooks for React.
Show a map
A map view, its controls, its panels, and the primitives underneath them.
Edit an itinerary
Draw a route, move a waypoint, and split a segment on the canvas.
Show itinerary data
An elevation profile and route tables, with no map anywhere.
Build a studio
The assembled editor, its chrome, its hooks, collaboration, and video export.
Browse examples
Running code for each of the above, ready to copy.
One credential, three hosts
The client resolves each surface to its own host, so one instance serves all three.
Point any of them at a local stack or at your own gateway with the baseUrls option.
A publishable key (pk_…) is safe to ship to a browser. A secret key (sk_…) mints session tokens and belongs on a server you control. @mountaya/client/browser does not export the secret-key credential, and its constructor throws in a page or a React Native application. Read authentication for the key, scope, and session model these packages implement.