Third-Party API Declaration
Last updated: 17 October 2026
Overview
Joule Genie integrates with a number of third-party APIs (Application Programming Interfaces) to connect with your energy hardware and services. These APIs are provided by the respective hardware manufacturers and service providers. This page explains how we use these APIs and the important limitations and disclaimers you should be aware of.
APIs We Use
Joule Genie connects to the following third-party APIs. For each piece of kit we say how we connect to it and whether we only read from it or can also change its settings. The list is generated from our integrations catalogue, so it always matches the integrations page.
Inverter & Battery APIs
- SunSynk — SunSynk Connect Cloud API (OAuth2 with RSA-encrypted password). Uses the same interface as the manufacturer’s own app, signed in with your account. The manufacturer does not publish it for third parties and can change or block it without notice. Used to read live data and to change the settings Joule Genie controls.
- Solis — SolisCloud API v1 (HMAC-SHA1 signed requests). An API the manufacturer publishes for third-party developers. Used to read live data and to change the settings Joule Genie controls.
- SolarEdge — SolarEdge Monitoring API v1 (Cloud, Read Only). An API the manufacturer publishes for third-party developers. Used to read data only. Joule Genie cannot change anything through it.
- Fox ESS — Fox ESS Cloud Open API. An API the manufacturer publishes for third-party developers. Used to read live data and to change the settings Joule Genie controls.
- GivEnergy — GivEnergy Cloud REST API v1. An API the manufacturer publishes for third-party developers. Used to read live data and to change the settings Joule Genie controls.
- Enphase — Enphase Enlighten API v4 (OAuth2). An API the manufacturer publishes for third-party developers. Used to read data only. Joule Genie cannot change anything through it.
- Fronius — Fronius Solar.web Query API. An API the manufacturer publishes for third-party developers. Used to read data only. Joule Genie cannot change anything through it.
- Growatt — Growatt ShineServer API (ShinePhone app login). Uses the same interface as the manufacturer’s own app, signed in with your account. The manufacturer does not publish it for third parties and can change or block it without notice. Used to read live data and to change the settings Joule Genie controls.
- SolaX Power — SolaX Cloud User Monitoring API v2 (token-based). An API the manufacturer publishes for third-party developers. Used to read data only. Joule Genie cannot change anything through it.
- Huawei SUN2000 — FusionSolar Northbound API (xsrf-token auth). An API the manufacturer publishes for third-party developers. Used to read data only. Joule Genie cannot change anything through it.
- SMA — SMA ennexOS Monitoring API v2 (OAuth2 ROPC). An API the manufacturer publishes for third-party developers. Used to read data only. Joule Genie cannot change anything through it.
- EcoFlow PowerOcean — EcoFlow Developer Cloud API (HMAC-SHA256 signed). An API the manufacturer publishes for third-party developers. Used to read data only. Joule Genie cannot change anything through it.
Energy Tariff APIs
- Octopus Energy — Octopus Energy Kraken API (GraphQL discovery + REST rates). An API the manufacturer publishes for third-party developers. Used to read data only. Joule Genie cannot change anything through it.
EV Charger APIs
- Pod Point — Pod Point Cloud API v5 (Firebase auth + Bearer token). Uses the same interface as the manufacturer’s own app, signed in with your account. The manufacturer does not publish it for third parties and can change or block it without notice. Used to read live data and to change the settings Joule Genie controls.
- Hypervolt — Hypervolt Cloud API (Keycloak OAuth2 + WebSocket JSON-RPC 2.0). Uses the same interface as the manufacturer’s own app, signed in with your account. The manufacturer does not publish it for third parties and can change or block it without notice. Used to read live data and to change the settings Joule Genie controls.
- myenergi Zappi — myenergi cloud API via the myenergi director (HTTP Digest Auth). Uses an access key you create in the manufacturer’s app; the manufacturer does not publish this interface for third parties. Used to read live data and to change the settings Joule Genie controls.
Vehicle APIs
- Audi — Volkswagen Group EU Data Act portal (read-only data snapshots, about every 15 minutes). Joule Genie signs in as you to the manufacturer’s owner portal and downloads the data you have asked the manufacturer to make available to you. The manufacturer can change or block this without notice. Used to read data only. Joule Genie cannot change anything through it.
- Volkswagen — Volkswagen Group EU Data Act portal (read-only data snapshots, about every 15 minutes). Joule Genie signs in as you to the manufacturer’s owner portal and downloads the data you have asked the manufacturer to make available to you. The manufacturer can change or block this without notice. Used to read data only. Joule Genie cannot change anything through it.
- MG (iSMART) — iSMART Cloud API. Uses the same interface as the manufacturer’s own app, signed in with your account. The manufacturer does not publish it for third parties and can change or block it without notice. Used to read live data and to change the settings Joule Genie controls.
- Tesla — Tesla account sign-in, as used by the Tesla app. Uses the same interface as the manufacturer’s own app, signed in with your account. The manufacturer does not publish it for third parties and can change or block it without notice. Used to read live data and to change the settings Joule Genie controls.
Home Automation APIs
- Home Assistant — Push webhook (bearer token). Your own system sends data to Joule Genie; we call nothing. Used to read data only. Joule Genie cannot change anything through it.
For British Gas, E.ON Next, OVO Energy, Scottish Power and EDF Energy, you enter your tariff's rates yourself. Joule Genie makes no call to those suppliers.
Weather & Solar Forecast APIs
- Forecast.Solar API — Used to obtain solar generation forecasts based on panel location and configuration.
- Open-Meteo API — Used when Forecast.Solar cannot answer, to estimate solar generation from forecast solar radiation and cloud cover.
- MET Norway Locationforecast API — Used for the weather forecast on the Forecast page. Our servers send it your solar panels' location rounded to about 1 km; your browser never contacts it.
Location APIs
- postcodes.io — When you look up your postcode while setting up your solar panels, our servers send the postcode to postcodes.io to find its latitude and longitude, and we cache the result for 30 days.
- OpenStreetMap map tiles — When you set up your solar panels, the map on that page is loaded by your browser from OpenStreetMap's tile servers.
Data credits
Weather data from MET Norway, licensed under CC BY 4.0. Fallback solar forecasts use weather data by Open-Meteo.com, licensed under CC BY 4.0. Solar forecasts by Forecast.Solar. Maps © OpenStreetMap contributors, available under the Open Database Licence. Postcode lookup by postcodes.io: contains OS data © Crown copyright and database right; contains Royal Mail data © Royal Mail copyright and database right; source: Office for National Statistics, licensed under the Open Government Licence v3.0.
Important Disclaimers
1. API Availability & Reliability
Third-party APIs are operated and maintained by their respective providers. Joule Genie has no control over the availability, reliability, performance, or uptime of these APIs. Service interruptions, rate limiting, maintenance windows, or outages on the part of third-party API providers may temporarily prevent Joule Genie from reading data from or sending commands to your hardware.
If we cannot reach a manufacturer's API, your hardware keeps the settings Joule Genie last sent it. Usually that is an ordinary charge schedule. But if the connection drops while we have, for example, told a charger to charge or a battery to charge from the grid, it carries on doing that until we can reach it again or you change it in the manufacturer's app. The optimiser picks up again once the API is back.
2. API Changes & Deprecation
Third-party API providers may, at their sole discretion, modify, deprecate, restrict, or discontinue their APIs at any time, with or without notice. Such changes may temporarily or permanently affect Joule Genie's ability to integrate with the affected hardware or service.
We actively monitor the APIs we depend on and endeavour to update our integrations promptly when changes occur. However, we cannot guarantee uninterrupted service in the event of breaking API changes by third-party providers.
3. How we connect
Where a manufacturer publishes an API for third-party developers, we use it. Some manufacturers do not, and for those Joule Genie uses the same interface as the manufacturer's own app or owner portal, signed in with the account details you give us. Each integration above says which kind it is.
An interface that is not published for third parties can change or stop working without warning, and a manufacturer may decide it does not want services like Joule Genie using it. If that happens we will tell you, and the integration may stop working for a while or for good. You should also check your manufacturer's terms if this matters to you: some say their app is for your personal use only.
We do not try to get around rate limits or access controls, and we poll no more often than the integration needs.
4. Security & Credential Handling
When you connect a third-party service through Joule Genie, your credentials are handled with the utmost care:
- All credentials are encrypted at rest using AES-256-GCM
- Credentials are transmitted exclusively over TLS-encrypted connections
- We store only the minimum credentials required to authenticate with each API
- Where available, we use OAuth 2.0 token-based authentication so that your password is never stored by Joule Genie
- Integrations that connect the way the manufacturer's app does need your account password to stay signed in, so we keep it, encrypted. Use a password you do not use anywhere else
- You can revoke access to any integration at any time from your settings page
- We never share your credentials with any party other than the relevant API provider during authentication
- Our support staff can view them only with your permission, to fix a problem with that integration, and every view is recorded (see our Terms of Service)
Security of the underlying authentication mechanisms (e.g. the OAuth 2.0 implementation, token issuance, and session management) is the responsibility of each third-party API provider. Joule Genie cannot be held responsible for vulnerabilities or breaches within a third-party provider's authentication infrastructure.
5. Data Accuracy
Data retrieved from third-party APIs (energy readings, tariff rates, vehicle state, solar forecasts) is provided by the respective third-party service. While we take reasonable steps to validate and cross-reference this data, Joule Genie does not guarantee the accuracy, completeness, or timeliness of data provided by third-party APIs.
Optimisation decisions are made based on the best available data at the time of each calculation cycle. Inaccurate data from a third-party source (e.g. incorrect tariff rates, stale battery readings) may result in sub-optimal scheduling decisions.
6. No Endorsement
The availability of an integration with a third-party API does not constitute an endorsement, recommendation, or warranty of the third-party's products or services. Similarly, the third-party API providers do not endorse or sponsor Joule Genie. See our Trademark Notice for full attribution details.
7. Liability
What we are and are not responsible for is set out in the Liability section of our Terms of Service. In particular, we are not responsible for loss caused by things outside our reasonable control, including:
- a manufacturer's or supplier's API being unavailable, failing, or being withdrawn
- changes to a manufacturer's or supplier's API, its terms or its pricing
- wrong, incomplete or late data from a manufacturer's or supplier's API that we could not reasonably have spotted
- security breaches in a manufacturer's or supplier's own systems
This does not limit our responsibility for our own failure to use reasonable care and skill, or anything else the law does not allow us to limit.
Reporting Issues
If you experience problems with a third-party integration, please contact us at support@joulegenie.com. We will investigate whether the issue is within our systems or on the third-party provider's side and advise you accordingly.
Updates to This Page
We may update this page as we add new integrations or as third-party API terms change. Material changes will be noted with an updated "Last updated" date. We recommend checking this page periodically if you rely on specific integrations.