Obtain a site API key from the SolarEdge monitoring portal under the Admin panel for the target site; the key is per-site and passed as the 'api_key' query parameter.
Call GET https://monitoringapi.solaredge.com/sites/list?api_key=<API_KEY> to enumerate sites accessible with the key, retrieving site IDs.
Retrieve energy production over a time period via GET /site/<SITE_ID>/energy?timeUnit=DAY&startDate=YYYY-MM-DD&endDate=YYYY-MM-DD&api_key=<API_KEY>; supported timeUnit values include QUARTER_OF_AN_HOUR, HOUR, DAY, WEEK, MONTH, YEAR.
For real-time power data, call GET /site/<SITE_ID>/currentPowerFlow to get current power flow between panels, battery, grid, and load.
To access inverter-level telemetry, use the equipment endpoints such as GET /equipment/<SITE_ID>/list to get serial numbers, then GET /equipment/<SITE_ID>/<SERIAL_NUMBER>/data for detailed telemetry.
Known gotchas
The SolarEdge API enforces a rate limit of 300 requests per day per API key at the free tier; automated polling at intervals shorter than about 5 minutes will exhaust the quota — cache responses aggressively.
Date parameters use the YYYY-MM-DD format in the site's local timezone, not UTC; sending UTC midnight can return data for the wrong day if the site is in a UTC-offset timezone.
Equipment-level data requires that the monitoring system have inverter-level visibility enabled; sites using only a revenue-grade meter may not expose per-inverter endpoints even though the site-level endpoints respond normally.
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