Retrieve live and historical channel readings from UbiBot IoT temperature/humidity loggers via the Platform API
domain: ubibot.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Generate an account_key from your UbiBot web console (no sales gate)
Optionally generate a per-channel read_key via POST /channels/{CHANNEL_ID}/api_keys?action=generate_read_key&account_key=... for scoped, channel-only access
Call GET https://webapi.ubibot.com/channels?account_key=... to list all channels along with their last_values
Call GET /channels/{CHANNEL_ID}?... for a single channel's field1-field10 readings and last_entry_date
Parse last_values (keyed by field1, field2, etc.) for the value and created_at timestamp of each reading
Known gotchas
Field names are generic (field1...field10), not semantically labeled - map them to temperature/humidity based on your channel's own sensor configuration
Prefer a per-channel read_key over the account-wide account_key when giving a third-party integration limited access
Check UbiBot's own API changelog before integrating, since endpoint/field behavior has changed over time
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?