Create a new schedule or a new version of an existing schedule.
Re-submitting for the same TSO + delivery date creates a new version. The TSO message ID is reused with an incremented version number as required by market rules (MaBiS for DE, MMC Hub for NL).
Submission flow
test=true)Gate closure (DE, per AG-FPM)
Gate closure (NL)
Request body for creating a new schedule.
Electricity market. Valid values: 'DE' or 'germany' (German market, MaBiS/ESS), 'NL' or 'netherlands' (Dutch market, TenneT MMC Hub).
DE, NL, germany, netherlands TSO identifier. DE values: '50HERTZ_DE_TSO' (50Hertz), 'DE-AMPRION-TSO' (Amprion), 'TTG_DE' (TenneT DE), 'DE-TRANSNETBWTSO' (TransnetBW). NL value: 'TENNET_TSO' (TenneT NL).
1EIC X code (organization code) of the receiving TSO. DE values by TSO — '50HERTZ_DE_TSO': '10XDE-VE-TRANSMK', 'DE-AMPRION-TSO': '10XDE-RWENET---W', 'TTG_DE': '10XDE-EON-NETZ-C', 'DE-TRANSNETBWTSO': '10XDE-ENBW--TNGX'. NL: EAN-13 code of TenneT NL: '8716867111163'.
1Time series to submit (0–50). DE requires at least 1 series. NL allows an empty list for zero-schedule or cancellation submissions.
50Delivery date (YYYY-MM-DD). If omitted, derived from the first timestamp in series data (UTC → Europe/Berlin). Example: omit when the first series timestamp is '2026-01-23T23:00:00Z' (= 2026-01-24 00:00 Berlin time) to get delivery date 2026-01-24.
If true, skip gate closure validation. Use in development/testing to submit outside normal market windows.
Successful Response
Response model for ScheduleVersion - matches eg-app contract.
Spec structure for schedule version.