Overview for integrators and evaluators
How the data reaches you
You either pull the data through the REST API or have it delivered by webhook, MQTT, CSV by email or SFTP. One connection can receive data from several metering points, and one metering point's data can go to several connections. Which channels exist and how they fit together is in Data deliveries: Overview. Whether a delivery arrived is shown in the delivery logs.
What you get each day
A day's values arrive on the following day (T-1). For electricity the grid operator usually delivers them as quarter-hour values. Webhooks and MQTT pass on new data after processing, and scheduled deliveries run on the configured schedule. What to expect after connecting: First data & next steps.
Historical data
For the period before the data sharing started, you can request data from the grid operator. How far back depends on the plan. The grid operator delivers the best resolution it holds, which for older periods is mostly daily values. How it works and where it stops: Requesting Historical Data.
Consent for many metering points
You enter the metering point number, but the contract holder confirms the data sharing in the grid operator's portal. In a portfolio this happens per metering point, and the metering points can belong to different grid operators. How to prepare it is in The Consent Process. If you create metering points through the API, the sequence is in Consent flow in detail. A webhook can notify you when a consent is granted, rejected or revoked.
Gaps and corrections
energiedaten.at re-requests missing days from the grid operator automatically, see Automatic Data Retry. The Data Completeness report shows which days are missing. A value can arrive again later with better quality, so write every value as an upsert, as described in Corrections and re-delivery.
Do you only want your metering data forwarded into your own systems? Talk to us.