Execute a remote elevator destination or landing call via KONE's Elevator Call API
domain: dev.kone.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Register a KONE API Portal account at dev.kone.com and create a Sandbox application to get a CLIENT_ID and CLIENT_SECRET
Call the Authentication API v2 token endpoint requesting a scope such as callgiving/group:<BUILDING_ID>:<GROUP_ID> plus inventory/application
Open a WebSocket connection to the Elevator WebSocket API v2 and send a Common API 'config' request to fetch the building's area/floor topology
Submit a destination call (source area + call.destination) or a landing call (source area + direction) over the same WebSocket session
Listen on the WebSocket for call-state and assigned-elevator events, or send a cancel request to cancel a call already placed
Known gotchas
Elevator Call API only works with buildings/equipment KONE has provisioned into the Sandbox or production environment you were granted access to, not arbitrary buildings
The API is a persistent WebSocket session per building/group, not simple REST request/response, so a token and the building topology must be fetched before any call is placed
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?