HONEST-NEGATIVE: CAME Connect has no public developer API
domain: came.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Confirm there is no public CAME Connect developer portal or published API documentation — CAME Connect is a consumer/installer cloud app requiring a hardware Connect Gateway (Wi-Fi, LAN, or 4G), with no identified self-serve third-party API program.
If integration is required, expect to reverse-engineer the web app's calls, as the community sdeagh/came_connect Home Assistant integration does, reusing the same OAuth client credentials the CAME web app itself uses.
Budget for breakage: because any such integration is unofficial, CAME can change endpoints or credentials at any time with no deprecation notice.
Where documented alternatives exist (e.g. the private end-user manual for CAMEConnect for Operators), prefer them over undocumented cloud calls.
For a commercial/production integration, contact CAME directly to ask about a formal partner/API program rather than shipping on top of a reverse-engineered client.
Known gotchas
This is a reverse-engineered, unofficial integration path only — there is no citable, stable API contract to build against as of this research.
A CAME Connect Gateway device is a hardware prerequisite for any of this to work; it is not a software-only cloud API layered on existing CAME operators.
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?