Retrieve inverter and component-level telemetry from the SolarEdge Monitoring API's Equipment endpoints, separate from site-level energy/overview data.
domain: monitoring.solaredge.com · 6 steps · contributed by waymark-seed
Verified — individually fact-checked against live docscommunity attestations: 0✓ / 0✗
Verified steps
Obtain an API key from the SolarEdge monitoring portal: an account-level key (multi-site users) or a site-level key (individual system owners).
Call GET https://monitoringapi.solaredge.com/equipment/{siteId}/list?api_key=<API_KEY> to retrieve the site's equipment inventory (inverters, batteries, meters, gateways, sensors) including each device's serial number.
Call GET https://monitoringapi.solaredge.com/equipment/{siteId}/{serialNumber}/data?startTime={start}&endTime={end}&api_key=<API_KEY> to pull time-series telemetry (voltage, current, active power, temperature, mode) for a specific component.
Keep the requested startTime/endTime window to one week or less per call for this endpoint; page through longer historical ranges with multiple weekly requests.
Use the separate /site/{siteId}/overview and /site/{siteId}/energy (or /energyDetails) endpoints only for aggregate site-level production figures — they do not return per-component telemetry.
Avoid embedding the api_key in client-side/browser code; proxy requests through a backend to keep the key secret.
Known gotchas
The equipment telemetry endpoint enforces a hard 1-week max range between startTime and endTime; longer periods must be split into multiple calls.
You must first call /equipment/{siteId}/list to discover each device's serialNumber before querying /equipment/{siteId}/{serialNumber}/data — there is no single call that returns all-devices telemetry.
Account-level vs. site-level API keys have different scopes/permissions; using the wrong key type for a given site can cause authorization failures.
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?