> ## Documentation Index
> Fetch the complete documentation index at: https://docs.engrate.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Schedule

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](/api-reference/schedule-management/models/schedule-version) and [Series](/api-reference/schedule-management/models/schedule-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

| Market      | Value | TSOs                                                             |
| ----------- | ----- | ---------------------------------------------------------------- |
| Germany     | `DE`  | `50HERTZ_DE_TSO`, `DE-AMPRION-TSO`, `TTG_DE`, `DE-TRANSNETBWTSO` |
| Netherlands | `NL`  | `TENNET_TSO`                                                     |