Live map example
Loading the Mapsource map…
Request / Response
Run a dependent spatial workflow
Find nearby hospitals, sort by distance and return only the closest five in one request.
API call
curl --fail-with-body "https://api.mapsource.io/compute" \
-H "Authorization: Bearer $MAPSOURCE_API_KEY" -H "Content-Type: application/json" \
--data '{"pipeline":[{"id":"hospitals","op":"nearby","args":{"lat":47.6062,"lon":-122.3321,"category":"hospital","radius":3000}},{"id":"ranked","op":"sort","args":{"input":"$hospitals","by":"distanceMeters"}},{"id":"closest","op":"limit","args":{"input":"$ranked","count":5}}],"return":"$closest"}'Example response
{"schema":"mapsource-compute.v1","returns":"$closest","steps":[{"id":"hospitals","status":"complete"},{"id":"ranked","status":"complete"},{"id":"closest","status":"complete"}],"result":{"type":"place_collection","count":5,"handle":"rh_c44e50b878b3e87a15a2d5ec9f21b640"}}Move the workflow, not every payload
A pipeline can connect search, routing and analysis without downloading each intermediate result. Estimate cost first, then execute up to twelve ordered steps.
Pass large results by handle
Typed result handles carry expiry, lineage, source versions, size and supported next operations. Retrieve a summary or payload only when the client actually needs it.
Service details
Built around a published contract
Inputs, outputs and limits remain inspectable in the generated API reference.
- Pipeline
- POST /api/compute
- Result
- GET /api/results/{id}
- Steps
- Up to 12 ordered operations
- Handles
- Typed, scoped and expiring