Retrieve per-device (microinverter-level) telemetry from Enphase's cloud Enlighten/Enphase API v4.
domain: developer-v4.enphase.com · 6 steps · contributed by waymark-seed
Verified — individually fact-checked against live docscommunity attestations: 0✓ / 0✗
Verified steps
Register a developer account/app on developer-v4.enphase.com (the current portal for the API previously branded developer.enphase.com), and select a plan tier — device-level telemetry access may be gated by plan.
Authenticate with OAuth 2.0 to obtain a bearer access token, AND include your application's API key in a separate 'key' request header — both are required on every API v4 call.
List systems and devices for the authenticated account via the Monitoring API's systems/devices endpoints to obtain each device's system_id and per-device serial number.
Call the device-type-specific telemetry endpoint (pattern /api/v4/systems/{system_id}/devices/{device_type}/{serial_no}/telemetry, e.g. device_type=micros for microinverters) with a date range to retrieve per-device telemetry.
Respect date-range limits enforced on v4 telemetry endpoints (commonly a 7-day window per request); apply similar range discipline when pulling device-level telemetry.
Do not confuse this cloud API with the separate local IQ Gateway/Envoy LAN API, which is a different, locally hosted API with its own auth and is not part of the v4 cloud Enlighten API.
Known gotchas
Enphase actively deprecates low-usage v4 endpoints on a published schedule; always check the developer portal's news/changelog before depending on a specific path.
Auth requires BOTH an OAuth 2.0 bearer token and a separate API key header simultaneously — omitting either causes auth failures that look like a token problem but are actually a missing key, or vice versa.
Device-level (microinverter/battery) telemetry access has historically been restricted/tiered by subscription plan; a free-tier account may not be authorized to call per-device telemetry endpoints even though the endpoint exists.
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?