Quickstart

Every Data API request needs two headers: your publishable key with the data scope in X-API-Key, and a session token in X-Session-Token. Mint a token from your key pair by calling POST /v1/sessions with your secret key. Tokens are valid for 5 minutes, so mint one just before you query.

curl -X POST https://internal.mountaya.com/v1/sessions \
  -H "X-API-Key: sk_your_secret_key" \
  -H "Content-Type: application/json" \
  -d '{"publishable_key": "pk_your_publishable_key"}'

A successful call returns 201 Created with the token and its expiry:

{
  "data": {
    "token": "sess_…",
    "expires_at": "2026-06-03T12:05:00Z"
  }
}

directions computes a route between an ordered list of waypoints for a given activity. Pass the activity slug and at least two [longitude, latitude] waypoints, then select the response fields you want back. Here we route from Chamonix to Saint-Gervais on foot.

curl https://data.mountaya.com/graphql \
  -H "X-API-Key: pk_your_publishable_key" \
  -H "X-Session-Token: sess_your_session_token" \
  -H "Content-Type: application/json" \
  -d '{
    "query": "query Directions($input: DirectionsInput!) { directions(input: $input) { routes { distance duration summary geometry elevation { ascent descent } } } }",
    "variables": {
      "input": {
        "activity": "HIKING_AND_TRAIL",
        "waypoints": [[6.8652, 45.8326], [6.7124, 45.8920]]
      }
    }
  }'

directions returns a routes array. Each DirectionsRoute carries the total distance in meters, the duration in seconds, a one-line summary, the route geometry as a GeoJSON LineString (coordinates are [longitude, latitude, altitude]), an elevation summary, and a surface and way type analysis.

{
  "data": {
    "directions": {
      "routes": [
        {
          "distance": 15200.0,
          "duration": 12160.0,
          "summary": "15.2 km, ~3h23m, +720m / -430m elevation, 62% unpaved.",
          "geometry": {
            "type": "LineString",
            "coordinates": [
              [6.8652, 45.8326, 1035],
              [6.7124, 45.892, 850]
            ]
          },
          "elevation": { "ascent": 720.0, "descent": 430.0 }
        }
      ]
    }
  }
}

Because the Data API is GraphQL, a failed query still returns 200 OK and reports problems in an errors array. Inspect errors on every response, not just the HTTP status. See the error envelope for the full shape.

Prefer to explore interactively? Open this query in the playground and run it against the live schema.

directions is one of several queries. Reach for suggestions to generate routes that hit a target distance, isochrones for reachable area, matrix for travel-time grids, the places queries for geocoding and POIs, and analyzeGeometry to classify an existing line. Browse them all in the playground or read the routing, places, and analysis guides.