Reference · built on requestConnectorEnergy, EV & distributed resources

SolarEdge Monitoring API

Site energy, power, alerts, and inverter, meter, and battery telemetry from the SolarEdge Monitoring API V2 on SolarEdge ONE.

Request accessPricing ↗

About

SolarEdge makes power optimizers, inverters, batteries, and meters, and its Monitoring platform holds the record of every site an installer commissions. The Monitoring API V2 at monitoringapi.solaredge.com/v2 is the read interface to that record: a Basic Monitoring API for sites, energy, power, devices, telemetry, and alerts, and an Advanced Monitoring API for per-destination breakdowns, live power flow, Weather Guard, and battery backup reserve.

Through Fibric, an operator reads a fleet's alerts and daily energy, ranks sites by performance ratio, and drafts the work order or customer notice for your approval. This connector reads only. Nothing on the site changes.

This is a reference listing. It documents what Fibric would read from SolarEdge Monitoring API and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Site List, Site Details, Site Overview, and Site Performance with specific yield and performance ratio
  • Site Energy at QUARTER_HOUR, HOUR, DAY, WEEK, MONTH, YEAR, or TOTAL resolution, and Site Power at QUARTER_HOUR or HOUR
  • Fleet Alerts across every site the key reaches, and Site Alerts, each with category, type, impact 1 to 9, status, and error codes
  • Devices at a site, filtered by type: inverters, batteries, meters, and gateways
  • Bulk inverter, meter, and storage telemetry: production, consumption, import, and export power and energy; charge, discharge, and state of energy
  • Per-destination power and energy, live power flow, Weather Guard state, and battery backup reserve on Business Pro and Enterprise

Proposed actions

Read-only. Actions need a separate connector.

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Rank underperforming sites each morning

    The operator reads Site Performance and yesterday's energy for every site, flags the ones whose performance ratio fell, and drafts a checklist ordered by lost yield for your review.

    With Array Yield, Anomaly Notice

  • Turn an equipment alert into a work order

    A Fleet Alert with high impact and an inverter serial number becomes a proposed work order with the error codes attached. You approve before anything is dispatched.

    With Alarm Triage, Predictive Maintenance

  • Notice a site that stopped reporting

    When a site's power series goes flat while neighbors keep producing, the operator checks its devices and alerts, then proposes a customer notice or a technician visit.

    With Sensor Health, Data Freshness

Requirements

  • A developer account at developer.solaredge.com and an Application created there with Fleet Access or Site Access
  • For Fleet Access, a SolarEdge account linked to the sites, or a consent link approved by the installer who owns the fleet
  • For Site Access, the SITE_DATA scope for site measurements and DEVICE_DATA for device-level telemetry, granted by the homeowner per site
  • Business Pro or Enterprise for the Advanced Monitoring API; lower tiers receive 403 on those endpoints
Authentication
Fleet Access uses an App API Key in the X-API-Key header; Site Access uses OAuth 2.0 authorization code through SolarEdge Connect, with a 2 hour Bearer access token and a rotating refresh token.

Limits

  • Calls per minute and monthly credits by tier: Free 10 and 2,000; Starter 25 and 20,000; Growth 50 and 100,000; Pro 100 and 400,000
  • Site Power queries cover at most 12 hours at QUARTER_HOUR and 24 hours at HOUR; longer spans return 400
  • Site List and Fleet Alerts accept an API Key only, not an OAuth token, and multi-site bulk paths from V1 were removed
  • The legacy V1 Monitoring API is planned for deprecation in November 2026; V2 drops fields such as dcVoltage, inverter temperature, and per-phase values

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request SolarEdge Monitoring API ↗

Questions and answers

Can this connector change settings on a SolarEdge site?
No. The Basic and Advanced Monitoring APIs are read APIs. The one write, POST /sites/{id}/power-flow, only starts a 1 minute live telemetry session. SolarEdge says Weather Guard and backup reserve updates belong to a separate, forthcoming Fleet Management API.
Which access type should a fleet operator use?
Fleet Access. An App API Key in the X-API-Key header covers every site owned by or linked to your SolarEdge account with no consent step. Site Access, with OAuth 2.0, is for apps that act for individual homeowners who authorize each site through SolarEdge Connect.
What happens when the tier limit is reached?
The gateway returns 429. If x-ratelimit-remaining-minute is 0, the per-minute limit was hit and the window resets at the next clock minute. If it is above 0, the monthly credit limit was reached and calls stay blocked until the billing cycle resets, unless overage is enabled.
Ask about SolarEdge Monitoring API

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with SolarEdge Monitoring API through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy