5 min read

Austrian Energy Data Exchange - Getting Started

Written by

Maximilian Ebert

Published on

November 11, 2026

https://andamp-1.webflow.io/blog/austrian-energy-data-exchange

Over the past two years, I've worked on data processing applications that use the Austrian Energy Data Exchange (EDA) to send and receive information. When I started, I had no prior experience in the energy sector or its communication processes, which left me feeling overwhelmed about where to begin, how to gain access, and who to contact. Thanks to patient colleagues and a lot of trial and error, I eventually found my footing.

That's why I wanted to create this getting started guide—to help other developers have an easier entry into Austrian energy market communication so they can focus on building great applications faster.

About Energy Data Exchange

Before diving into the steps, let's clarify what EDA actually is. Because understanding the architecture will make the onboarding process much clearer.

Back in 2012, when Austrian regulators wanted to accelerate the energy supplier change process for customers, it became clear that a standardized data exchange platform between market participants was necessary to meet regulatory requirements. This led to the implementation of EDA (Energiewirtschaftlicher Datenaustausch) by market participants.

In essence, EDA is a decentralized data exchange platform that enables asynchronous, secure, and direct XML message transmission between market participants. The entry points into this messaging network are called Ponton X/P nodes. To put it simply, you can think of these nodes as input and output message queues that enforce schema validity and message encryption while guaranteeing sender and receiver authenticity.

Market participants can either host Ponton X/P nodes themselves or use them indirectly through different connection methods or SaaS solutions.

Who is Who?

When I first started planning our application's integration with EDA, I spent considerable time asking the wrong questions to the wrong people. To help you avoid the same mistake, here's a breakdown of the most important entities and their responsibilities in market participant communication:

EDA GmbH

Responsible for operational tasks including infrastructure management, EDA platform contract negotiations with market participants, and ensuring non-discriminatory exchange of data between all participants. If you have questions about your platform contract, connection method or Ponton X/P license, EDA GmbH is your go-to contact. However, for process implementation or message-specific questions, you should visit ebUtilities.

ebUtilities

Provides technical documentation for message schemas and data exchange processes. They also handle consultation with market partners for new processes and manage and publish the market partner registry.

Ponton

Develops the Ponton X/P nodes and provides the centralized components of EDA on behalf of EDA GmbH, including Certificate Authority, SIA, and Profile Registry. Technical support requests for Ponton X/P nodes or email connector issues can be submitted to Ponton via their Jira system.

Step-by-Step Guide

Armed with this knowledge of who does what, the onboarding process becomes straightforward. Here are six steps that will take you from 'interested developer' to 'active market participant.' Don't worry, it's more systematic than it first appears.

1. Determine your Role

EDA communication requires you to be an authorized market participant. First, identify which category you fall into (for a complete detailed list, visit Marktpartner - EbUtilities):

Energy Community (EEG, BEG, GEA)
Energy Supplier
System Operator
Energy Service Provider

Each role has different requirements and capabilities within the EDA system.

If you have trouble deciding which role is yours, there is more information on Registrierung - EbUtilities.

2. Identify Required Processes

Depending on your role, you'll need to implement different communication processes. The easiest way to find relevant processes is to use the ebUtilities process documentation (Prozesse - EbUtilities) and filter by your role.

EbUtilities provides process diagrams for every communication process. I strongly recommend integrating these diagrams into your application's process documentation to identify missing processes or unhandled events. This is particularly helpful when communication processes are updated due to regulatory changes, as the impact on your application becomes immediately visible.

Additionally, XSD files are available at ebUtilities, allowing you to easily verify the schema of your messages in your integration and unit tests.

3. Register at ebUtilities

The next step is registering at ebUtilities (Registrierung - EbUtilities) to obtain your market partner identification and role-specific identifiers (f.e. community identification).

While the specific documents required may vary depending on your role, you'll generally need to provide:

Legal entity documentation
Proof of market role eligibility
Contact information for authorized representatives

4. Choose your Connection Method

Now that you're a registered market participant, it's time to decide how you'll connect to other market partners and exchange data. You have three methods to choose from:

EDA Portal

This is an easy way to participate in energy data exchange, best suited for small market participants who don't have their own software solutions. Since this method doesn't provide programmatic access, I won't cover it in this article.

E-Mail Connection

This connection provides an SMTP/IMAP interface for sending and receiving messages. It's ideal for market partners with fewer than 200 metering points who have their own processing software solutions.

CEP - Ponton X/P

This allows you to host a Ponton X/P node in your own infrastructure, providing various interfaces and integrations including REST APIs, Java APIs, and SOAP services. There's no limit on metering points for this connection method, making it the recommended choice for market participants with high-volume traffic.

5. Get a platform contract

At this point, you're a registered market participant who understands the required processes and has chosen a connection method. Now it's time to make it official by signing an EDA platform contract. You can initiate this process by contacting EDA through their registration form at eda.at/registrierung.

Pricing and the process itself depend on your connection method and market role. After submitting all relevant information, EDA will reach out to you.

During our first process, we had the opportunity to speak with an EDA project manager who helped clarify uncertainties and corrected misconceptions. It was incredibly helpful and a great experience overall.

6. Onboarding

After signing the platform contract, you'll be granted access to Ponton's Jira and Confluence systems. The Confluence pages are an excellent source of information about your connection method, and I highly recommend reading through them thoroughly.

If you choose the email connection, you'll receive IMAP and SMTP credentials via a ticket from a Ponton employee, and you'll be ready to go. You can find a guide on message formatting within Ponton's Confluence pages.

Onboarding your own Ponton X/P requires a bit more involvement and varies depending on your infrastructure and requirements. However, Ponton's Confluence onboarding guide is excellent, and their employees are very helpful and friendly. I'm confident you'll succeed.

Conclusion

Developing applications that leverage Austrian energy data exchange infrastructure is extremely rewarding once you understand who's responsible for what and where to find documentation for your specific use case and integration needs. If you are planning software for energy suppliers and market participants, it pays to look at the requirements of market communication from the start.

I'd also like to mention that since I started with no knowledge of Austrian energy data exchange, I required substantial assistance. Throughout the process, I spoke extensively with ebUtilities, EDA, and Ponton representatives, all of whom were exceptionally helpful, friendly, and patient.

At &amp we build the systems that sit behind energy data exchange, from first connection to production rollout. Reach out if you have questions about ebUtilities, EDA, or where your use case fits in.

‍

This guide is based on current regulations and platform capabilities as of September 2025. Always verify the latest requirements on ebUtilities.at and consult with EDA GmbH support for your specific situation.

Resources:

‍

Share this post

https://andamp-1.webflow.io/blog/austrian-energy-data-exchange