Create a new Schedule or a new Schedule 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 1. Validate gate closure (skipped when test=true) 2. Validate EIC codes, business types, and interval counts 3. Build ESS XML (DE) or CIM XML (NL) 4. Submit to TSO via AS4 messaging 5. Create audit event 6. Return the created schedule version
Gate closure (DE, per AG-FPM) - Day-ahead: open until D-1 14:30 CET for all series types - DA matching (D-1 14:30–16:00 CET): internal series accepted; external/foreign corrections only - Intraday: D-1 16:00 CET until GCT (15-minute lead time for external/foreign)
Gate closure (NL) - Day-ahead window: D-2 10:00 CET to D-1 15:00 CET
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 EIC 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: '8716867999983'.
1Time series to submit (0–50). DE requires at least 1 series. NL allows an empty list for zero-schedule or cancellation submissions.
50TSO identifier. DE values: '50HERTZ_DE_TSO' (50Hertz), 'DE-AMPRION-TSO' (Amprion), 'TTG_DE' (TenneT DE), 'DE-TRANSNETBWTSO' (TransnetBW). NL value: 'TENNET_TSO' (TenneT NL).
1Delivery 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
A Schedule Version representing one submission attempt. Each re-submission creates a new version.
Highest acceptance level reached: empty string, ack, or cnf.
"cnf"
"ack"
""
ISO 8601 datetime when this version was created.
"2026-03-25T14:00:00+00:00"
ISO 8601 datetime of the most recent status change.
"2026-03-25T14:05:00+00:00"
Organization that owns this version.
"9b2e4d8f-1c3a-4f5e-8d7b-6a9e0f2c1b3d"
Full submission specification including market routing and series references.
Processing status: ingested, submitted, accepted, rejected, cnf_partial, or icnf.
"accepted"
"submitted"
"rejected"
Unique identifier for this version.
"c8d7e6f5-4a3b-4c2d-9e1f-0a8b7c6d5e4f"
Sequential version number (1-based). Increments with each re-submission.
1
2
3
Whether this version is the active one according to the authoritative TSO message ID. Older versions become inactive when a new version is accepted.
TSO document identification assigned to this version's message.
"MSG-20260325-001"
Whether a Non-Repudiation of Receipt (NRR) delivery confirmation has been received from the TSO.
Mako365/AS4 transmission report identifier for delivery tracking.
"TR-20260325-001"
TSO warnings from the ACK response, if any.