Sign in

v1

latestOpenAPI 3.0.02026-07-263365201.7 KB
Subscriptions

Terminate a subscription

Terminate a subscription. Three reasons are supported:

  • ORDINARY: regular termination. intended_end_at is optional; when omitted, the plan's cancellation period applies.
  • MOVE_OUT: special termination right tied to a move-out date. intended_end_at is mandatory and still has to leave the grid operator a few working days of notice.
  • WITHDRAWAL: 14-day cooling-off period (Widerruf) after contract confirmation. The end date is calculated to comply with grid-operator notice periods.

All end dates in the request and response are exclusive midnight Europe/Berlin: from that moment the customer is no longer supplied. The customer's last day of supply is the day before the named date.

Every termination reason has to clear the grid operator's working-day notice; ORDINARY additionally has to respect the plan's cancellation period.

Conflict responses (409) carry a dedicated errors[].code:

  • invalid_termination_date — the requested date is in the past or violates the plan's / grid operator's notice period.
  • withdrawal_not_allowed — the 14-day withdrawal window has elapsed (or the subscription has no confirmed_at to count from).
post/subscriptions/{id}/terminate

Path parameters

idstring required
Example:sub_mi4f0oda6x9m7gcsvjk0ole1

Request body

OR
OR

Example request

{
  "intended_end_at": "2026-12-31T00:00:00+01:00"
}

Response

The subscription's termination details

reason'ORDINARY' | 'MOVE_OUT' | 'WITHDRAWAL' required
intended_end_atstring date-time required

Customer-provided or system-calculated exclusive end timestamp at midnight Europe/Berlin. From this instant the customer is no longer supplied.

Example response

{
  "intended_end_at": "2026-12-31T00:00:00+01:00"
}