Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Log into the Flume customer portal, open Settings, scroll to the bottom, and click 'Generate API Client' to obtain a client_id/client_secret pair.
Authenticate using the OAuth2 Resource Owner Password Credentials grant against the token endpoint (flumetech.readme.io/docs/authentication) with username, password, and client credentials to receive an access_token and refresh_token.
Call REST endpoints documented at flumetech.readme.io/reference using 'Authorization: Bearer <access_token>' to list devices and query water-use readings for a device/location.
Refresh the token via the documented refresh route before/near expiry, then manually delete the old access token since Flume does not auto-invalidate it.
Known gotchas
A client generated through the portal only works for the account that created it — this is explicitly a personal-use API, not a multi-tenant one.
Old access tokens keep working until natural expiry even after a refresh; failing to delete them is a real lingering-credential risk.
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?