Reference · built on requestConnectorEnergy, EV & distributed resources

Enphase API

System, production, consumption, battery, and EV charger data from Enphase Monitoring API v4, with DER control through the VPP API.

Request accessPricing ↗

About

Enphase Energy makes microinverters, IQ Batteries, and IQ EV Chargers, and its cloud reports on every system through Enlighten. The Monitoring API v4 at api.enphaseenergy.com/api/v4 exposes system details, site and device level production, consumption, storage telemetry, events, and alarms. A separate VPP API at vpp.enphaseenergy.com lets grid-services programs enroll sites and dispatch PV, battery, heat pump, and EVSE events.

Through Fibric, an operator watches a fleet of Enphase systems for production shortfalls, open alarms, and battery state, then proposes a battery setting change or a dispatch event for your approval. Each approved change is sent once and leaves a receipt: what changed, why, and how to undo it.

This is a reference listing. It documents what Fibric would read from Enphase 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

  • Systems and their status through GET /systems, POST /systems/search, and GET /systems/{system_id}/summary
  • Production telemetry for microinverters and production meters through /telemetry/production_micro and /telemetry/production_meter, in 5 or 15 minute intervals
  • Consumption, battery, grid import, and grid export telemetry through /telemetry/consumption_meter, /telemetry/battery, /energy_import_telemetry, and /energy_export_telemetry
  • Events and alarms through /events, /alarms, /open_events, and /open_alarms, with /event_types listing each event's recommended action
  • Revenue-grade meter intervals through /rgm_stats, 15 minutes long and starting at the top of the hour
  • Last reported PV, consumption, battery, and EVSE power through /latest_telemetry, and an on-demand live stream through /live_data
  • IQ EV Charger devices, sessions, schedules, and interval energy through the /ev_charger endpoints

Proposed actions

  • Target capability: propose a battery settings change through PUT /systems/config/{system_id}/battery_settings, available on the Megawatt plan
  • Target capability: propose a VPP event through POST /api/v2/events to curtail PV, charge, discharge, or idle a battery, or set EVSE charge mode
  • Target capability: propose enrolling or unenrolling a site in a grid-services program through POST /api/v1/applications
  • Target capability: propose opting a site out of a scheduled event through PUT /api/v1/events/optout/{event_id}, up to 1 minute before it starts

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

What you can build

  • Catch a system that stopped producing

    The operator compares each system's production telemetry with its open events. When an inverter or gateway stops reporting, it drafts a ticket with the event type and recommended action for your review.

    With Array Yield, Alarm Triage

  • Hold battery reserve ahead of a storm

    Reading storm guard and battery settings alongside a weather alert, the operator proposes a higher reserve for the sites in the warning area. You approve, and the setting is written once.

    With Storm Reserve, Battery Dispatch

  • Dispatch a demand-response event

    For sites enrolled in a program, the operator proposes a VPP event with a start time and duration. After approval it posts the event and records which sites opted out.

    With Event Response, Peak Demand

Requirements

  • A developer account on developer-v4.enphase.com with an application subscribed to the Watt, Kilowatt, or Megawatt plan
  • Approval from each system owner, which yields the auth code you exchange for access and refresh tokens
  • The Megawatt plan for System Configurations, which includes reading and updating battery settings
  • Registration with Enphase Grid Services as a utility, aggregator, or third-party owner before the VPP API is available
  • Access tokens expire after 1 day and refresh tokens after 1 month, so the connector keeps tokens current
Authentication
OAuth 2.0 authorization code flow, approved by each system owner, plus your application's API key sent with every Monitoring API request; the VPP API uses client credentials and an x-api-key header.

Limits

  • Plan rate limits: Watt allows 10 hits per minute and 1,000 per month, Kilowatt 50 and 50,000, Megawatt 100 and 300,000
  • Events reach back 9 months, at most 1 week per call; /rgm_stats returns at most 7 days per call within the last 2 years
  • Start and stop charging on the Monitoring API are illustrative only; charger control runs through the VPP API
  • The VPP API creates events for a single site per call, and the live status stream runs for 30 to 300 seconds per request

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 Enphase API ↗

Questions and answers

Which plan do you need to change battery settings?
The Megawatt plan. Enphase lists System Configurations, which includes battery_settings, as a Megawatt-only access control. Watt and Kilowatt cover system details, site and device production, consumption, and EV charger monitoring.
Can this connector control chargers or batteries directly?
Only through the VPP API, which Enphase makes available to registered grid-services programs. Events there can curtail PV, charge or discharge a battery, or set an EVSE to Charge or Dont_Charge. The Monitoring API's start_charging and stop_charging calls are marked illustrative only.
How fresh is the telemetry?
Interval telemetry arrives in 5 minute or 15 minute buckets depending on the endpoint, and /latest_telemetry returns the last reported power per device. For real-time values, /live_data streams for 30 seconds by default and up to 300 seconds, with each Live Status hit metered separately on paid plans.
Ask about Enphase 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 Enphase 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