Skip to main content
The Schedule Management API provides a unified interface for submitting energy schedules to Transmission System Operators (TSOs) in Germany and the Netherlands. You work with a single API regardless of the target market. The platform handles protocol differences, data format conversion, and validation rules for each TSO automatically.

​
Core concepts

A Schedule represents one delivery date for one TSO. Each submission creates a Schedule Version, and re-submitting for the same TSO + date increments the version. Each version contains one or more Schedule Series — the individual time series (internal trades, external trades, production, consumption) with quarter-hourly interval data.

​
Supported markets

MarketTSOsProtocolGate closure
Germany (DE)50Hertz, Amprion, TenneT DE, TransnetBWESS XML via Mako365 AS4DA: D-1 14:30 CET
Netherlands (NL)TenneT NLCIM XML via MMC HubDA: D-2 10:00 to D-1 15:00 CET

​
Versioning

Re-submitting for the same TSO + delivery date automatically creates a new version. The TSO message ID is reused with an incremented _v{N} suffix. Previous versions remain accessible and are annotated with is_active=false when a newer version is accepted.

​
Anomaly reconciliation

After submission, the TSO may send ANO (anomaly) messages indicating mismatches between your values and the counterparty’s values. Use the reconciliation endpoint to get a side-by-side comparison with per-interval deltas. For German schedules, counterparties with exchange priority (Börsenvorrang) are flagged — their values may be imposed by the TSO per Bilanzkreisvertrag clause 12.b.
See the Schedule Management product page for DE and NL market-specific submission guides with example requests.