Your electricity data in the systems your team works with.

Your portfolio management, ERP, energy management, or own dashboard receives the previous day's smart meter values for your Austrian metering points every day.

Overview of active integrations with webhook, MQTT, email, and SFTP, including enabled status, next scheduled run, and last used time.

Use smart meter data where your team already works

Feed systems with measurements

Your existing systems receive the electricity data they need for operations, analysis, or billing. A webhook endpoint can also hear, on request, when a customer approves, rejects, or revokes a meter connection, so it does not have to poll the status.
Assigned metering points for an integration, grouped by location, with active status and last data transfer.

Replace manual file handoffs

Nobody has to export, rename, and forward CSV files any more: new measurements go straight to the right systems after processing.
Data transfer log with status, record count, and time.

Share scheduled exports with teams and customers

Weekly, monthly, or quarterly CSV exports go to the people or systems that regularly need them.
Scheduled export with recipient, CSV attachment, and send status.

How smart meter electricity data flows into your systems

Grid-operator smart meter electricity data

How smart meter data reaches us →

energiedaten.at

We receive grid-operator data, put it into the right format, and route it to your systems.

Typical paths, depending on what the receiving system supports.

API Webhook MQTT SFTP CSV email Scheduled exports

Choose the connection by workflow

Systems & automation For receiving software and processes
Recurring analysis For scheduled CSV exports
I want to … Send measurements automatically to software, dashboards, IoT systems, or file targets. Receive scheduled CSV exports for a week, month, or quarter.
Typical paths API, webhook, MQTT, SFTP, or CSV email Scheduled CSV export by email
Time range New data after processing or on a schedule One week, month, or quarter
Fits when … Your system processes the data directly, for example ThingsBoard or enerchart as an MQTT recipient. Your team or customers regularly need a file for analysis.

You can see whether data arrived.

Every delivery is verifiable

For every transfer, you can see whether the data reached your system.

The last arrival is visible

Connections show when data was last transferred or retrieved, plus the next scheduled transfer when a schedule exists.

Failed transfers are flagged in the log

A failed transfer stays in the log, so you notice a gap before your analysis runs on incomplete data, and you can check the affected connection.

Ask about consumption in your AI assistant

Connect your assistant to the team's data through AI connections (MCP). Ask how consumption differs at the weekend or when a peak occurred.

Frequently asked questions

Are webhooks and MQTT a live data stream?
No. Smart meter values reach the platform from the EDA network on the following day. Webhooks and MQTT pass on new data after processing; scheduled connections run on the configured schedule.
Does my system learn when a customer approves or revokes a connection?
Yes, if you choose it on a webhook connection. The four events are pending customer approval, approved, rejected, and revoked. Each arrives with a timestamp, and with the HMAC security method it is also signed. Your system does not poll the meter status. A few cases send no event, for example a connection request that cannot be delivered, so keep the status endpoint as a fallback.
Can one metering point's data go to several systems?
Yes. One metering point's data can go to a backend, an IoT platform, and a file target, for example. Each connection has its own configuration and history.

Your smart meter data, daily in your systems

Smart meter consumption data via API, webhook, or CSV for all Austrian grid operators.