Skip to main content
POST
/
schedule-management
/
v1
/
mabis
/
clearing-periods
/
{uid}
/
objections
Create Objection
curl --request POST \
  --url https://api.engrate.io/schedule-management/v1/mabis/clearing-periods/{uid}/objections \
  --header 'Authorization: <api-key>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "disputed_values": {},
  "objection_type": "volume",
  "reason": "<string>"
}
'
{
  "clearing_period_uid": "<string>",
  "created_ts": "<string>",
  "disputed_values": {},
  "last_modified_ts": "<string>",
  "objection_type": "<string>",
  "status": "<string>",
  "uid": "<string>",
  "reason": "<string>",
  "resolved_ts": "<string>",
  "submitted_ts": "<string>",
  "tso_response": "<string>"
}

Authorizations

​
Authorization
string
header
required

Path Parameters

​
uid
string<uuid>
required

Clearing period unique identifier.

Body

application/json

Request to create an objection.

​
disputed_values
Disputed Values · object
required

Free-form dict describing the disputed values. Example: {"date": "2026-01-15", "interval": 42, "our_value_mwh": 1.5, "tso_value_mwh": 1.8}.

​
objection_type
enum<string>
required

Objection type. 'volume': disputed energy quantity (MWh). 'price': disputed reBAP price. 'metering_point': incorrect metering point assignment. 'allocation': incorrect balance group allocation. 'timing': wrong delivery period or timestamp. 'other': any other dispute.

Available options:
volume,
price,
metering_point,
allocation,
timing,
other
​
reason
string | null

Human-readable reason for the objection.

Response

Successful Response

An Objection (Einspruch) filed against settlement data within a clearing period.

​
clearing_period_uid
string
required

Parent Clearing Period identifier.

​
created_ts
string
required

ISO 8601 datetime when this objection was created.

Example:

"2026-02-26T10:00:00+00:00"

​
disputed_values
Disputed Values · object
required

Free-form data describing the disputed values (dates, intervals, amounts).

​
last_modified_ts
string
required

ISO 8601 datetime of the most recent status change.

Example:

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

​
objection_type
string
required

Objection category: volume, price, metering_point, allocation, timing, or other.

Examples:

"volume"

"price"

​
status
string
required

Objection status: draft, submitted, accepted, rejected, or withdrawn.

Examples:

"submitted"

"accepted"

"rejected"

​
uid
string
required

Unique identifier for this objection.

Example:

"e7f8a9b0-c1d2-4e3f-8a4b-5c6d7e8f9a0b"

​
reason
string | null

Human-readable reason for the objection.

​
resolved_ts
string | null

ISO 8601 datetime when the objection was resolved (accepted or rejected).

​
submitted_ts
string | null

ISO 8601 datetime when the objection was submitted to the TSO.

​
tso_response
string | null

TSO response text, if the objection has been reviewed.