Skip to main content
A schedule represents one delivery date for one TSO. It is the top-level object you create when submitting energy values, and serves as the container for all Versions and Series associated with that date. Schedules are scoped to a single organization, market, and TSO. Re-submitting for the same TSO + delivery date creates a new version under the existing schedule rather than a new schedule.

​
Identifying a schedule

Each schedule is uniquely identified by its uid. Within an organization, a schedule is also uniquely identified by the combination of market + tso + date.

​
Markets

MarketValueTSOs
GermanyDE50HERTZ_DE_TSO, DE-AMPRION-TSO, TTG_DE, DE-TRANSNETBWTSO
NetherlandsNLTENNET_TSO

A Schedule header representing a single delivery-date submission to a TSO.

​
created_ts
string
required

ISO 8601 datetime when the schedule was created.

Example:

"2026-03-25T14:00:00+00:00"

​
date
string
required

Delivery date in ISO 8601 format (YYYY-MM-DD).

Example:

"2026-03-26"

​
last_modified_ts
string
required

ISO 8601 datetime of the most recent modification.

Example:

"2026-03-25T16:30:00+00:00"

​
market
string
required

Target market. DE for Germany, NL for the Netherlands.

Examples:

"DE"

"NL"

​
org_uid
string
required

Organization that owns this schedule.

Example:

"9b2e4d8f-1c3a-4f5e-8d7b-6a9e0f2c1b3d"

​
tso
string
required

Transmission System Operator identifier.

Examples:

"50HERTZ_DE_TSO"

"DE-AMPRION-TSO"

"TTG_DE"

"DE-TRANSNETBWTSO"

"TENNET_TSO"

​
uid
string
required

Unique identifier for this schedule.

Example:

"f47ac10b-58cc-4372-a567-0e02b2c3d479"