Skip to content

50,000 free calls a month, card-free. Get an API key →

Documentation menu
docs / api / post-elevation-along
elevation

POST/elevation/along

API key required, sent as Authorization: Bearer snk_… or ?api_key=snk_….

Call it

bash
curl -fsS -X POST "https://api.mapmap.ai/elevation/along" \
  -H "Authorization: Bearer $MAPMAP_KEY" \
  -H "Content-Type: application/json" \
  -d @request.json

Request body

application/json

Along-route elevation profile: a route (geometry_polyline6, or the full route response POST /route returns), and at most one of interval_m (default 100 m) or sample_count

The OpenAPI document declares this body as a free-form JSON object with no field list, so there is nothing here to generate a table from. The prose above is what the gateway states about it; the raw document is the authority.

Responses

200{samples: [{distance_m, lat, lon, elevation_m, source, resolution_m, grade_percent}], total_distance_m, total_ascent_m, total_descent_m, coverage_fraction, sample_count}. grade_percent on sample i is the percent grade of the segment ending at i (null on sample 0, and whenever either endpoint lacks elevation). total_ascent_m/total_descent_m are null (not 0) when no consecutive pair of samples both have elevation
400Invalid request
401Missing or invalid API key
429Quota or rate limit exceeded
501Elevation not enabled on this deployment (SN_ELEVATION_ENABLED unset; the hosted gateway sets it true: this is a self-hosting gate for a Valhalla with no DEM tiles staged)
502Upstream routing engine failed

Error bodies follow the shared problem model documented on API conventions.

Also under elevation

Generated from https://api.mapmap.ai/openapi.json on 2026-09-17 · operationId post_elevation_along