Application 5 min read Phillip Fickl

Smart meter data via API in Austria

You want to pull a smart meter's consumption data into your own software programmatically, refreshed every day. The obvious search is then "Wiener Netze Smart Meter API" or "EVN Smart Meter API". Developers usually mean a publicly documented REST API that returns consumption data as JSON after authentication. Austria organizes that access differently.

Under the ElWG, the end customer decides who receives a metering point's data: they give consent in their grid operator's web portal, and the grid operator transmits the data via EDA to the service they chose.[1] That works with every grid operator. Only a few grid operators offer their own customer API on top. Through a platform with an EDA connection, you therefore retrieve the data from every grid operator through a single REST API.

Is there a Smart Meter API from Wiener Netze or EVN?

A publicly documented REST API in the usual developer format is not the standardized access route. Section 58 ElWG refers to programmatic interfaces operated by grid operators, but it does not prescribe a public REST endpoint using Bearer tokens and JSON responses.[1]

The market role also matters when searching for an "EVN Smart Meter API": Netz Niederösterreich is the grid operator for smart meter data in EVN's network area. EVN Energievertrieb is the electricity supplier.

The reason lies in how the Austrian electricity market is structured. Grid operators store the measurement data and make it available through a regulated shared infrastructure, the EDA network. EDA stands for Energiewirtschaftlicher Datenaustausch (energy data exchange), and it is a decentralized messaging system. Market participants use it to exchange encrypted XML messages following an industry-specific standard.

EDA lists three connection types for energy service providers:[2]

  • The EDA Portal, with an integrated process environment for sending and processing messages.
  • An email connection, which requires your own software application.
  • A dedicated communication endpoint, which requires your own IT environment and software application.

The integration task therefore lies in market communication: processing EDA messages, managing consent, and normalizing readings. We trace the full path from meter to your system, station by station, in the data journey.

What a smart meter interface in Austria needs to cover

Whether you can work with the data depends on whether the interface does three things:

  • The interface bundles all distribution grid operators into a single connection, so you don't maintain a separate integration per operator.
  • The data arrives in one consistent format across all grid operators, with documented fields, ready for your software to process.
  • Quality stays traceable. Readings carry quality levels, and some are corrected later; if that isn't visible, you are working with numbers whose reliability you can't judge.

On top of that come the end customer's consent, daily delivery on a T-1 cadence, and a delivery channel that fits your architecture. All three are covered below.

Consent comes before the data

Before an eligible third party receives meter data, the end customer must consent to the transfer. Section 60 ElWG governs that permission and the right to revoke it at any time.[1]

In the online process, an authorized service provider submits a data request for a specific metering point via the EDA network. The responsible grid operator validates it, and the end customer then gives consent in their grid operator's web portal. This step cannot be automated, because it is a deliberate decision by the end customer, and data delivery only starts after it. An offline process also exists, in which consent is obtained outside the portal and demonstrated to the grid operator.

Consent is valid for the period defined in the request and can be revoked at any time. Historical readings can be requested for up to three years into the past.[3] Your software starts the consent process through the API, and in the online process the customer gives the consent itself through their grid operator. Your onboarding flow therefore has to allow for a wait until that consent is in.

One REST API for every grid operator

energiedaten.at covers these requirements. You talk to a single REST API, and the platform handles the EDA communication, the preparation of the raw data and the quality checks. You receive consumption data your software can process directly.

The basic flow takes three calls:

POST /api/v1/smart-meters                  → register a meter
POST /api/v1/smart-meters/{id}/consent     → start the consent process
GET  /api/v1/smart-meters/{id}/data        → retrieve consumption data

Further endpoints cover status queries and revocation. Consent and data delivery remain asynchronous processes.

How to access the data via API

Authentication uses a Bearer token with defined scopes such as data:read or consents:request, so you can keep access tightly limited per integration. Retrieving the consumption data for a metering point then looks like this:

curl https://energiedaten.at/api/v1/smart-meters/{id}/data \
  -H "Authorization: Bearer $API_KEY"

The API returns the readings supplied by the grid operator at the finest available resolution, which with quarter-hour reading active means 96 values per day. Ongoing delivery follows the T-1 principle, so the previous day's values are supplied the following day, and the next synchronization picks up later corrections through the sync cursor. Responses include standard rate-limit headers. The full reference, with every endpoint, scope, and response field, lives in the API documentation; a guided way in is on the developer page.

Pull the data or have it pushed

The REST API is the pull route: you request data when you need it. For many integrations the push route is more practical: new values are delivered to you as soon as they reach us. There are further channels for that:

  • Webhooks notify your system as soon as new values are available.
  • MQTT suits IoT and streaming applications.
  • CSV via email delivers files to a mailbox your systems pick up.
  • SFTP provides files for ERP integration.

The REST API is included in every plan. Which push channels are added depends on the plan you choose; the details are on the pricing page.

Prefer ready-made exports to writing code? Our reporting route delivers consumption data straight into your spreadsheet or reporting tool.

What you don't have to build yourself

Building your own EDA integration is feasible, but it is a project in its own right. You register as a market participant, run a dedicated communication endpoint with licensed specialist software and manage consent per metering point. Then there is parsing and transforming the XML messages, monitoring the quality of the readings, efficient time-series storage, and several delivery channels, each with its own error handling. You also have to keep up with the EDA network's twice-yearly protocol updates.

Ongoing maintenance continues after launch. For businesses whose core product is not EDA infrastructure, that effort quickly outweighs the benefit. Our comparison of your own connection and energiedaten.at shows which work that is. How energiedaten.at takes on this task for software products and for energy service providers is described on the pages for developers and energy service providers.

Frequently asked questions

Is there an official Smart Meter API from Wiener Netze or EVN?

Only a few grid operators offer their own customer API; the Wiener Netze web portal, for example, points to one. The route that works with every grid operator is consent: the end customer allows, in their grid operator's portal, that the meter data goes via EDA to a service of their choice. A service such as energiedaten.at provides one REST API in the usual developer format across all grid operators.

Can I read my own smart meter data via API?

Yes, with every grid operator. In practice, your right to your meter data under the ElWG runs through EDA: you give consent in your grid operator's web portal, the grid operator transmits the data via EDA to the service you chose, and that service delivers it to you via REST API. Only a few grid operators offer their own customer API on top: Salzburg Netz documents a programming interface for automated retrieval,[4] and the Wiener Netze web portal points to a customer API.[5] Registered market participants can establish their own EDA connection.

Do I need a separate consent for each metering point?

Yes. Consent applies per metering point. In the online process, the end customer gives it in their grid operator's portal. The API starts the consent process; the consent itself stays with the customer.

How current is the data through the API?

Ongoing data delivery follows the T-1 principle. The previous day's values are supplied the following day at the finest resolution available for the metering point.

What do the quality levels in the readings mean?

Each value carries a quality level: L1 (measured) and L2 (reliable substitute) are considered dependable, L3 is preliminary. When a grid operator replaces an L3 value with better data, the correction appears during the next synchronization through the sync cursor.

More on smart meter data

For the wider context, see our guide to smart meter data in Austria, and when manual data collection reaches its limits is covered in the article on automation.

If you want to bring consumption data into your product, take a look at the plans or start on the page for developers.


[1] Elektrizitätswirtschaftsgesetz (ElWG), BGBl. I No. 91/2025, Section 58: meter data through a programmatic interface and web portal; Section 60: permission and revocation of meter-data transfers to eligible third parties.

[2] EDA Energiewirtschaftlicher Datenaustausch GmbH, "Energy service providers": EDA Portal, email connection, and communication endpoint as connection types.

[3] ebUtilities, "Request energy data" process: historical requests are limited to a maximum of three years into the past.

[4] Salzburg Netz GmbH, programming interface in the service portal (accessed 9 November 2026): customers and authorised third parties retrieve data per personal API key for metering points the service portal grants them access to.

[5] Wiener Netze GmbH, Smart Meter portals (accessed 9 November 2026): the web portal lists the customer API under "Kundenschnittstelle" and links to the Wiener Stadtwerke API portal.

Stay up to date

Get new articles and product updates directly in your inbox.

Related articles

Your smart meter data, daily in your systems

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

Try for free