Register on the Enphase Developer Portal to receive an API key and create an OAuth 2.0 application; the Enlighten API uses OAuth for system owner authorization.
Direct the system owner through the OAuth authorization code flow to obtain an access token scoped to their systems; store the refresh token for long-term access.
Retrieve the list of systems accessible to the authorized user via GET /api/v4/systems, noting each system's system_id.
Fetch energy production summary data for a system via GET /api/v4/systems/<SYSTEM_ID>/summary, which returns lifetime energy, current power, and last-reported timestamp.
For time-series production data, use the telemetry endpoints such as GET /api/v4/systems/<SYSTEM_ID>/telemetry/production_micro or the energy_lifetime endpoint, specifying start_at and end_at as Unix timestamps.
Known gotchas
Enphase API v4 introduced breaking changes from v2 — older integrations using v2 endpoints or parameter names will fail; always target the current documented version and do not assume backward compatibility.
Production data is reported at the microinverter level aggregated to system level; the reporting granularity is typically 15-minute intervals, but data may be delayed by several minutes to an hour depending on Envoy connectivity.
The API enforces rate limits per API key and per system; systems with many historical data points require paginated or date-bounded requests — requesting too wide a time range returns an error rather than truncated data.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp