Danish electricity spot price history: DK1/DK2 cutover avatar

Danish electricity spot price history: DK1/DK2 cutover

Pricing

from $0.00005 / actor start

Go to Apify Store
Danish electricity spot price history: DK1/DK2 cutover

Danish electricity spot price history: DK1/DK2 cutover

Get DK1 and DK2 day-ahead prices in EUR/MWh and DKK/MWh across the Elspotprices to DayAheadPrices transition. Native hourly and 15-minute area-day bundles, Danish time offsets, source links and coverage diagnostics. Up to 31 dates per run.

Pricing

from $0.00005 / actor start

Rating

0.0

(0)

Developer

Michal Pšenčík

Michal Pšenčík

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

3 days ago

Last modified

Share

Get complete day-ahead electricity prices for the Danish price areas DK1 (West) and DK2 (East) from Energinet's free Energi Data Service API, across the 1 October 2025 switch from hourly prices (Elspotprices) to quarter-hour prices (DayAheadPrices). Each result is one complete Danish calendar day for one area, with every native interval in EUR/MWh and DKK/MWh, exact UTC and Danish-offset timestamps, the source link and a content hash. Useful for EV charging and battery simulations, backtests and energy analytics that need correct history on both sides of the cutover and on daylight-saving days.

Input

{
"startDate": "2025-09-30",
"endDateExclusive": "2025-10-02",
"areas": ["DK1", "DK2"],
"maxRows": 62,
"requestIntervalMs": 1100
}
  • startDate / endDateExclusive: Danish calendar dates (Europe/Copenhagen), give both or neither. With neither, the run returns yesterday. Earliest start 2024-01-01, latest included date tomorrow, at most 31 dates per run.
  • areas: DK1, DK2 or both (default both).
  • maxRows: most bundles to store and pay for in this run (1 to 62, default 62).
  • requestIntervalMs: idle time after each source response (1100 to 60000, default 1100).

Output

One dataset item per complete area-day. Dates before 2025-10-01 have 24 hourly intervals (23 or 25 on daylight-saving days); from 2025-10-01 there are 96 quarter-hours (92 or 100).

{
"recordId": "energinet:DK2:2025-09-30",
"localDate": "2025-09-30",
"area": "DK2",
"timezone": "Europe/Copenhagen",
"sourceDataset": "Elspotprices",
"sourceUrl": "https://api.energidataservice.dk/dataset/Elspotprices?start=2025-09-30&end=2025-10-01&...",
"observedAt": "2026-10-17T04:34:15.619Z",
"coverageStatus": "complete",
"expectedIntervalCount": 24,
"intervalCount": 24,
"contentHash": "127197d118770ab4864ea9fb769f25811dd15c9abe36794745358b5f5342fff7",
"intervals": [
{
"intervalStartUtc": "2025-09-30T21:00:00Z",
"intervalStartDK": "2025-09-30T23:00:00+02:00",
"intervalMinutes": 60,
"priceEUR_MWh": 92.480003,
"priceDKK_MWh": 690.252246
}
]
}

Prices are the source's own values, kept exactly as JSON numbers (raw exports may spell them in exponent form, such as 9.2480003e1 for 92.480003; the value is identical) (no rounding, VAT, tariffs, kWh conversion or exchange-rate recalculation; negative and zero prices are kept). observedAt is when the source was actually read: a repeat within the cache period shows the original read time. recordId stays the same across runs, so you can upsert on recordId and detect source corrections when contentHash changes. A day with any missing, duplicated-and-conflicting, null or malformed interval is never returned as a bundle; it is listed in the free SUMMARY record instead. Each stored bundle is read back (and read again whenever a run resumes after a restart) and its content hash is recomputed from the stored row: if storage ever changed a price, the run fails with delivery_not_exact instead of returning a rounded bundle as exact.

Pricing

Pay per event: $0.008 per complete area-day bundle stored (including repeat checks served from the cache) plus $0.00005 per run start. The four cutover bundles above cost $0.03205; 30 days for both areas cost $0.48005. Incomplete days, errors, cooldown deferrals and the run summary are free. Set a spending limit and the actor stops before a bundle the limit cannot cover.

Run summary and limits

Every run writes a free SUMMARY record to the default key-value store: run status (complete, partial, failed, deferred), request and cache counts, delivered record IDs, source statuses, missing or invalid UTC slots per area and date, errors with source URL and HTTP status, retryNotBeforeUtc and a continuation (the first date and areas not delivered) for the next run.

The free API is rate-limited (it answered HTTP 429 "Try again in 298 seconds" during research). The actor therefore makes at most one request per dataset per run (two when a window spans 1 October 2025), waits at least five minutes before asking the same dataset again (across runs) and caches validated responses for 24 hours (5 minutes when the window includes today or tomorrow). A run that would need the source during a cooldown returns deferred without charge for bundles; run it again after retryNotBeforeUtc. Run one backfill at a time: runs share one cache and a simple lease, which is not a distributed lock. Longer backfills use adjacent runs.

Tomorrow's prices appear after Energinet publishes them; the source recommends requesting them around 13:00 to 14:00 CET, roughly every five minutes. An unpublished day is reported as publication_unknown, never as a zero price.

Source and attribution

Data: Energinet, Energi Data Service (api.energidataservice.dk), datasets Elspotprices and DayAheadPrices. Keyless public API; no personal data. This actor is not affiliated with Energinet or Nord Pool.