Reference · built on requestConnectorEnergy, EV & distributed resources

Easee Cloud API

Chargers, sites, circuits, sessions, and observations from the Easee Cloud, with commands for charging, dynamic current, and schedules.

Request accessPricing ↗

About

Easee makes home and commercial EV chargers and the Equalizer load balancer, all managed through the Easee Cloud at api.easee.com. Its REST API exposes chargers, sites, and circuits, per-charger observations, charging sessions summarized by hour, day, month, or year, energy measurements, and consumption reports, and it accepts commands to start, stop, pause, or resume charging, cap dynamic charger or circuit current for a set number of minutes, and manage daily and weekly schedules. A separate AMQP service streams live data and low-latency commands under its own agreement.

Through Fibric, an operator reads circuit states and ongoing sessions across your sites and proposes a dynamic current limit or a schedule change when the building load or the tariff calls for it. You approve, the command is sent once, and a receipt records the amps, the time to live, and the reversal.

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

  • Chargers for the account through GET /api/chargers, and each charger's details, configuration, and site
  • Last reported observations per device, such as state, current, and paired RFID token, through Get Observations with the documented observation IDs
  • Charging sessions per charger, user, or site through /api/sessions, summarized hourly, daily, weekly, monthly, or yearly, plus the ongoing session
  • Sites, circuits, dashboard circuit states, circuit settings, and the current dynamic circuit current of the primary charger
  • Lifetime, hourly, daily, and monthly energy measurements per charger, and site consumption reports
  • Live device data and command responses through the AMQP service, where subscribed

Proposed actions

  • Target capability: propose start, stop, pause, or resume through POST /api/chargers/{chargerId}/commands/start_charging and its stop, pause_session, and resume_session counterparts
  • Target capability: propose a temporary charger limit through set_dynamic_charger_current with an amp value and minutes to live
  • Target capability: propose a circuit-wide limit through POST /api/sites/{siteId}/circuits/{circuitId}/dynamicCurrent with a TTL in minutes
  • Target capability: propose creating or deleting daily and weekly schedules through the chargers schedules endpoints
  • Target capability: propose a settings change, such as max charger current or cable lock, through Change Charger Settings and Set Cable Lock State

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

What you can build

  • Cap a garage circuit at the tariff peak

    When the peak window opens, the operator proposes a dynamic circuit current for each garage circuit with a time to live that ends with the window. You approve once; the limit expires on its own.

    With Tariff Window, Charge Balancing

  • Pause charging when the building meter spikes

    Reading circuit states beside the main meter, the operator proposes pause_session on the lowest-priority chargers and a resume once load falls. Each step waits for your approval.

    With Peak Demand, Event Response

  • Bill tenants from session summaries

    Monthly session summaries per user and charger become a draft charge-back statement per tenant, with kWh and cost from the site's charging price, for review before it is sent.

    With Utility Chargeback, Parking Overflow

Requirements

  • An Easee account with access to the chargers: a Site Owner account for your own, or an approved Operator account to serve other site owners
  • For Operator access, a generic account created at portal.easee.com, an application reviewed by Easee's integrations team, and a signed data protection addendum
  • Chargers online over Wi-Fi or cellular, since commands are forwarded to the device
  • A separate paid agreement with Easee for the AMQP live-data and command service
Authentication
A Bearer access token from POST /api/accounts/login with the account's userName (email or phone number with country code) and password, valid for 1 hour and renewed with the refresh token.

Limits

  • Rate limits per endpoint: GET /api/chargers 2 per minute, sessions 10 per 60 minutes, observations 100 per 5 minutes, settings 20 per minute
  • A dynamic charger current limit clears when the charger reboots or the cable is disconnected; a limit with 0 minutes stays until replaced
  • Basic and weekly charge plan endpoints are marked for deprecation after 1 September 2026 in favor of the daily and weekly schedule endpoints
  • Site Owner integrations may not be used commercially, and Easee may limit calls per endpoint or data over cellular connections

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 Easee Cloud API ↗

Questions and answers

Do you need an Operator account?
Only to serve other site owners. A Site Owner account controls the chargers you own through the public API and cannot be used commercially. To offer smart charging or access control to other sites, Easee requires an Operator account, granted after an application review and a data protection addendum.
How long does a dynamic current limit last?
As long as the minutes you give it. Easee's example is 10 A for 4 minutes, after which the limit clears. Setting minutes to 0 keeps the limit until another is set. A charger-level limit also clears on reboot or when the cable is disconnected.
How often can sessions be polled?
Session endpoints are rate limited to 10 requests per 60 minutes each, and the charger list to 2 per minute. Observations allow 100 requests per 5 minutes. For live data, Easee offers the AMQP service as a separate paid subscription rather than faster polling.
Ask about Easee Cloud 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 Easee Cloud 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