Skip to main content
A schedule series represents one time series within a schedule version — for example one internal trade between two balance responsible parties, or one production injection.

Series types

TypeDescription
internalTrade within the same TSO control area
externalCross-border trade between two TSO areas (requires market_agreement_id)
foreignCross-border trade where your party is not a direct market participant (requires market_agreement_id)
productionOwn generation injected into the grid
consumptionOwn load withdrawn from the grid

A Schedule Series representing one time series within a schedule version (e.g. one internal or external trade).

created_ts
string
required

ISO 8601 datetime when this series was created.

Example:

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

last_modified_ts
string
required

ISO 8601 datetime of the most recent status change.

Example:

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

spec
ScheduleSeriesSpec · object
required

Full series specification including identifiers, type, and interval data.

status
string
required

Processing status of this series: ingested, submitted, accepted, rejected, cnf_partial, or icnf.

Examples:

"accepted"

"rejected"

time_series_uid
string
required

Time series identifier used in the ESS/CIM document.

Example:

"TS-001"

uid
string
required

Unique identifier for this series record.

Example:

"d1e2f3a4-b5c6-4d7e-8f9a-0b1c2d3e4f5a"

version
integer
required

Version number of the parent schedule version.

Examples:

1

2

acceptance_level
string | null

Highest acceptance level reached for this series: ack, cnf, or null if not yet responded to.

Example:

"cnf"

interval_statuses
Interval Statuses · object

Per-interval status map (interval index to status string). Present only when the TSO provides interval-level feedback (e.g. partial CNF).

Example:
{ "0": "accepted", "1": "rejected" }