Integrate YoLink water leak sensors and sump-pump alert accessories into a basement monitoring workflow via YoLink's public API
domain: doc.yosmart.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Review the API overview at https://doc.yosmart.com/docs/overall/intro/ to understand YoLink's cloud (HTTP/MQTT) and local API options
For local-network control without depending on YoLink's cloud, follow the local API quick-start guide at https://doc.yosmart.com/docs/overall/qsg_local/
For cloud integration, use Open API V2 (https://doc.yosmart.com/docs/protocol/openAPIV2/), authenticating with a UAC (User Access Credential) issued from the YoLink app's account settings
Use the device-list and device-state calls to enumerate leak sensors and query current wet/dry status, then subscribe via MQTT for real-time alerts rather than polling
Reference YoSmart's official GitHub client (YoSmart-Inc/yolink-api) for a working reference implementation before writing a custom client from scratch
Known gotchas
Open API V1 is documented alongside V2 but is the older interface — target V2 for new integrations unless a specific device only supports V1
UAC credentials are generated per-account inside the YoLink mobile app, not via a self-service web developer console — plan the onboarding flow around that
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?