Skip to main content
GET
/
schedules
/
{schedule_uid}
/
versions
List Schedule Versions
curl --request GET \
  --url https://api.engrate.io/schedules/{schedule_uid}/versions \
  --header 'Authorization: Bearer <token>'
[
  {
    "uid": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
    "schedule_uid": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
    "created_ts": "<string>",
    "last_modified_ts": "<string>",
    "version": 500,
    "org_uid": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
    "spec": {
      "market": "<string>",
      "tso": "DE-AMPRION-TSO",
      "sender_id": "<string>",
      "receiver_id": "<string>",
      "series": [
        {
          "ids": {
            "in_area": "<string>",
            "out_area": "<string>",
            "in_party": "<string>",
            "out_party": "<string>"
          },
          "type": "production",
          "data": [
            {
              "ts": "<string>",
              "amount": 1
            }
          ]
        }
      ]
    },
    "status": "rejected",
    "acceptance_level": "accepted_preliminary"
  }
]

Authorizations

​
Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

​
schedule_uid
string<uuid>
required

Query Parameters

​
limit
integer | null
​
after
string<uuid> | null
​
after_ts
string<date-time> | null
​
date
string | null
​
order
enum<string> | null
Available options:
oldest-first,
newest-first
​
market
enum<string> | null

Supported market IDs.

Available options:
germany,
netherlands

Response

Successful Response

​
uid
string<uuid>
required
​
schedule_uid
string<uuid>
required
​
created_ts
string
required
​
last_modified_ts
string
required
​
version
integer
required
Required range: 1 <= x <= 999
​
org_uid
string<uuid>
required
​
spec
GermanScheduleSpec · object
required

Specs for production schedules for the German market.

​
status
enum<string>
required

High-level schedule statuses.

Available options:
rejected,
ingested,
submitted,
pending,
imposed,
anomaly,
accepted,
settled,
unknown
​
acceptance_level

When a schedule has been accepted, it happens in three stages. Also used for time series statuses.

Available options:
accepted_preliminary,
accepted_final,
accepted_settled