Skip to main content
GET
/
schedule-management
/
v1
/
schedules
/
{uid}
/
anomalies
Get Schedule Anomalies
curl --request GET \
  --url https://api.engrate.io/schedule-management/v1/schedules/{uid}/anomalies \
  --header 'Authorization: <api-key>'
[
  {
    "business_type": "<string>",
    "business_type_label": "<string>",
    "created_ts": "<string>",
    "in_area": "<string>",
    "in_party": "<string>",
    "incoming_message_uid": "<string>",
    "intervals": [
      {}
    ],
    "message_sender_id": "<string>",
    "out_area": "<string>",
    "out_party": "<string>",
    "reason_codes": [
      {}
    ],
    "series_id": "<string>",
    "uid": "<string>",
    "schedule_series_uid": "<string>"
  }
]

Authorizations

​
Authorization
string
header
required

Path Parameters

​
uid
string<uuid>
required

Schedule unique identifier.

Response

Successful Response

​
business_type
string
required

ESS business type code: A01 (production), A02 (internal), A03/A06 (external), A04 (consumption), A85 (system).

Examples:

"A01"

"A02"

"A03"

​
business_type_label
string
required

Human-readable label for the business type.

Examples:

"production"

"internal"

"external"

"consumption"

​
created_ts
string
required

ISO 8601 datetime when this anomaly record was received.

Example:

"2026-03-26T08:00:00+00:00"

​
in_area
string
required

EIC Y code of the receiving control area.

Example:

"10YDE-VE-------2"

​
in_party
string
required

EIC X code of the receiving party.

Example:

"11XDE-EXAMPLE--A"

​
incoming_message_uid
string
required

Identifier of the incoming ANO message that contained this record.

​
intervals
Intervals · object[]
required

Interval-level anomaly data. Each entry contains pos (1-based position) and qty (MW delta).

Example:
[
  { "pos": 1, "qty": 0.1 },
  { "pos": 2, "qty": -0.05 }
]
​
message_sender_id
string
required

EIC X code of the entity that sent the anomaly message (typically the TSO).

Example:

"10XDE-VE-TRANSMK"

​
out_area
string
required

EIC Y code of the sending control area.

Example:

"10YDE-VE-------2"

​
out_party
string
required

EIC X code of the sending party.

Example:

"11XDE-EXAMPLE--B"

​
reason_codes
Reason Codes · object[]
required

Reason codes explaining the anomaly.

Example:
[
  {
    "code": "A09",
    "text": "Counterpart schedule missing"
  }
]
​
series_id
string
required

Time series identifier within the ANO document.

Example:

"TS-ANO-001"

​
uid
string
required

Unique identifier for this anomaly record.

Example:

"b4c5d6e7-f8a9-4b0c-8d1e-2f3a4b5c6d7e"

​
schedule_series_uid
string | null

Matched Schedule Series identifier, if the anomaly could be correlated to a submitted series.