MaBiS-Bestellungen

A BKV cannot order a summed series: the party that forms it activates each MaBiS-Zählpunkt on its own (UTILMD 55062) once market locations are assigned. What a BKV may order are three things, each an ORDERS over the MakoFlow AS4 gateway (ORDERS AHB 1.1b ch. 5):

Prozess	PID	To	Asks for	Answer
`bilanzkreiszuordnungsliste`	17203	ÜNB or NB	The balance group’s active MaBiS-Zählpunkte (MaBiS 10.6 / 11.4 / 11.5)	UTILMD 55067
`clearingliste_bas`	17204	BIKO	The clearing list behind one BAS version (MaBiS 13.11)	UTILMD 55070
`aggregationsebene_rz`	17207	ÜNB	The level of the BK-SZR (Kategorie B): control area (Z98) or per Bilanzierungsgebiet (Z99) (MaBiS 11.7 / 11.8)	ORDRSP 19204 on refusal only

Modes

modus is the AHB’s IMD code:

abo_start (Z01) — start a subscription of the Bilanzkreiszuordnungsliste, or order the control-area level.
abo_ende (Z02) — end it, or cancel the control-area level so the BK-SZR (Kategorie B) arrives per Bilanzierungsgebiet only.
einmalig (Z03) — one list, for monat (YYYY-MM): the Bilanzkreiszuordnungsliste of one area, or the Clearingliste BAS (which is only ever ordered once).

ausfuehrung (DTM+203, midnight German time) dates a subscription and a level change. A level change applies from the 1st of a month and must go out at the latest 2 WT before that month; the send endpoint refuses a later one and the preview names the deadline (frist).

Defaults

control_area defaults to the home control area; from it the bridge takes the ÜNB (17203, 17207) or BIKO (17204) MP-ID from the BDEW register, our balance group there, and — for a one-off list from the ÜNB — the Regelzone EIC. A one-off list from an NB needs its receiver_mp_id and Bilanzierungsgebiet (gebiet_eic). The Clearingliste BAS takes the BAS Zählpunkt the BIKO activated for the balance group (ZA6, Zeitreihentyp BAS); version is the BAS version it is for.

In the console

The Bestellungen tab of the console does the same: choose the order, Regelzone and kind, Vorschau, then Senden — which previews once more and asks for confirmation with the resolved receiver and deadline — and the list below shows every order with its status.

Calls

Preview first; send only after a human go:

# Cancel the control-area level from 1 December (Z99 per Bilanzierungsgebiet)
curl -X POST "$BRIDGE/v1/process/bestellungen/preview" \
  -H "X-API-Key: $NLEAD_PROCESS_KEY" -H "Content-Type: application/json" \
  -d '{"prozess":"aggregationsebene_rz","modus":"abo_ende","ausfuehrung":"2026-12-01","control_area":"TenneT"}'

# Subscribe to the Bilanzkreiszuordnungsliste of the TenneT ÜNB
curl -X POST "$BRIDGE/v1/process/bestellungen" \
  -H "X-API-Key: $NLEAD_PROCESS_KEY" -H "Content-Type: application/json" \
  -d '{"prozess":"bilanzkreiszuordnungsliste","modus":"abo_start","ausfuehrung":"2026-10-15","control_area":"TenneT"}'

# The Clearingliste of BAS version 1 for September from the Amprion BIKO
curl -X POST "$BRIDGE/v1/process/bestellungen" \
  -H "X-API-Key: $NLEAD_PROCESS_KEY" -H "Content-Type: application/json" \
  -d '{"prozess":"clearingliste_bas","monat":"2026-09","version":"1","control_area":"Amprion"}'

GET /v1/process/bestellungen lists every order sent with its acknowledgment (CONTRL/APERAK) and answer. status is abgelehnt (a negative acknowledgment or the ORDRSP 19204), beantwortet (the list arrived), angenommen (a level change without refusal after 1 WT), quittiert (positive APERAK only) or gesendet. Every send stores the exact interchange in the audit trail (bestellung_*.json under the send day) and a summary in the bestellungen ledger; the event log carries bestellung_sent / bestellung_failed. The UTILMD answers are acknowledged by the regular APERAK loop.

Implementing the Service

Running the Service

Reference

Internal API

Modes

Defaults

In the console

Calls

​Modes

​Defaults

​In the console

​Calls

Modes

Defaults

In the console

Calls