Powercast aims to lower the boundary to query, view and understand energy pricing.
Go and check the graphs:
The following datasets are used to look up data.
The network- and system-tariff in Denmark are defined by law and published by Energinet yearly.
The electricity charge is defined by law.
- Danish krone is pegged to a rate of 7.46 krones per Euro.
- Danish VAT is always 25%
Begin here to load all data using the API:
curl -v https://codereaper.github.io/powercast-data/api/energy-price/
The response will contain paths to latest and oldest available data points for each zone using the following format:
[
{
"latest": "/api/energy-price/<yyyy>/<MM>/<dd>/<zone>.json",
"oldest": "/api/energy-price/<yyyy>/<MM>/<dd>/<zone>.json",
"zone": "<zone>"
},
// ...
]
Request the specific data by replacing data and zone information in this request:
curl -v https://codereaper.github.io/powercast-data/api/energy-price/<yyyy>/<MM>/<dd>/<zone>.json
The response is the cost over time using the following format:
[
{
"euro": <cost>, // of one MWh
"timestamp": <unix timestamp>
},
// ...
]
Begin here to load all data using the API:
curl -v https://codereaper.github.io/powercast-data/api/renewables/
The response will contain paths to latest and oldest available data points for each zone using the following format:
[
{
"latest": "/api/renewables/<yyyy>/<MM>/<dd>/<zone>.json",
"oldest": "/api/renewables/<yyyy>/<MM>/<dd>/<zone>.json",
"zone": "<zone>"
},
// ...
]
Request the specific data by replacing data and zone information in this request:
curl -v https://codereaper.github.io/powercast-data/api/renewables/<yyyy>/<MM>/<dd>/<zone>.json
The response is the grouped energy amount over time using the following format:
[
{
"timestamp": <unix timestamp>,
"sources": [
{
"type": <generation-type>,
"energy": <MWh>
},
// ...
],
},
// ...
]
Begin here to load all data using the API:
curl -v https://codereaper.github.io/powercast-data/api/emission/co2/
The response will contain paths to latest and oldest available data points for each zone using the following format:
[
{
"latest": "/api/emission/co2/<yyyy>/<MM>/<dd>/<zone>.json",
"oldest": "/api/emission/co2/<yyyy>/<MM>/<dd>/<zone>.json",
"zone": "<zone>"
},
// ...
]
Request the specific data by replacing data and zone information in this request:
curl -v https://codereaper.github.io/powercast-data/api/emission/co2/<yyyy>/<MM>/<dd>/<zone>.json
The response is the emission over time using the following format:
[
{
"timestamp": <unix timestamp>,
"co2": <amount>, // in g/kWh
},
// ...
]
Note that only DK zones are available Note that local currency for DK zones means Øre per kWh
All data for a zone is available on a single endpoint:
curl -v https://codereaper.github.io/powercast-data/api/energy-charges/grid/
The response is the charges and tariffs over time using the following format:
[
{
"from": <unix timestamp>,
"to": <unix timestamp>,
"electricityCharge": <local currency>,
"transmissionTariff": <local currency>,
"systemTariff": <local currency>,
"zone": <zone>
},
// ...
]
All available networks are available on a single endpoint:
curl -v https://codereaper.github.io/powercast-data/api/energy-charges/network/
The response will contain a list of attributes for each network:
[
{
"id": <id>,
"name": <name>,
"zone": <zone>
},
// ...
]
All data for a specific network is available on a single endpoint:
curl -v https://codereaper.github.io/powercast-data/api/energy-charges/network/<id>/
The response is the tariffs over time using the following format:
[
{
"from": <unix timestamp>,
"to": <optional unix timestamp>,
"tariffs": [<local currency>, ...] // 24 entries with hourly tariff
},
// ...
]
The endpoints that serve data which is automatically updated from an upstream data source also has an endpoint to retrieve ongoing and past incidents.
The endpoints in question in are:
curl -v https://codereaper.github.io/powercast-data/api/incidents/emission/co2/<zone>.json
curl -v https://codereaper.github.io/powercast-data/api/incidents/energy-price/<zone>.json
curl -v https://codereaper.github.io/powercast-data/api/incidents/renewables/<zone>.json
The response for the incidents are using the following format:
[
{
"from": <unix timestamp>,
"to": <optional unix timestamp>,
"type": <string> // Specific enumeration value see table below
},
// ...
]
Tip
There will only be one ongoing incident with a specific type
until it becomes a past incident.
Note
Incidents started being recorded as of 2024 mid April.
The list of used types are enumerated here:
Type | Description |
---|---|
delay | Data expected to be updated according to schedule remains unchanged |