Furo Docs
OperateTelemetry API

Telemetry API

Send your asset's measurements to Furo and fetch the schedule for your controller.

With the Telemetry API you send your asset's measurements — consumption, PV, grid import and grid feed-in — directly to Furo. Furo runs the live optimization on them and shows you the result as a virtual battery in the app. If software on site controls your battery, it fetches the schedule over the same API.

How it works

  1. Start a new analysis and create a virtual battery from it.
  2. Send the URL of the virtual battery to support@furoenergy.com and request an API key and system ID.
  3. You get your individual API key and the system ID back through a secure channel.
  4. Send your data to the API. You get back the URL of your virtual battery with live data.

Fetching the schedule

Your controller asks Furo for the schedule — every 15 minutes, always outbound. Furo never opens a connection into your network; your controller only needs to reach api.furoenergy.com over HTTPS.

For every quarter hour it receives control values, not just optimizer numbers:

  • a setpoint for the battery — or none, where self-consumption is the better controller
  • charge and discharge limits that always apply
  • import and export limits at the grid connection, which take precedence over the setpoint
  • an operating mode: self-consumption, peak shaving or direct command

Each response also says whether it is to be followed. While an asset runs in test mode, Furo serves the schedule for reading along only (control_enabled: false); we switch it live once you are ready. If a fetch fails, the controller keeps following the last schedule — up to the validity end the response names.

The fields in detail are under Schedule.

On this page