Validation Endpoints for IBAN and Market Location IDs

The Lumenaza API provides lightweight validation endpoints you can call before submitting a consumer or producer registration. Use these to surface input errors in your UI immediately — before making a full registration call that would return a 400.

Validate an IBAN

GET /v3/validation/bank_data_iban/

Validates an IBAN (International Bank Account Number) for correct format and check digit.

string

required

The IBAN to validate (e.g. DE89370400440532013000).

Responses

200 OK — The IBAN is valid. No response body. 400 Bad Request — The IBAN failed validation.

string

A human-readable error message describing the validation failure.

curl --request GET \
  --url "https://api.lumenaza.de/v3/validation/bank_data_iban/?iban=DE89370400440532013000" \
  --header "Authorization: Bearer <token>"
# Returns: HTTP 200 (no body)

curl --request GET \
  --url "https://api.lumenaza.de/v3/validation/bank_data_iban/?iban=DE00000000000000000000" \
  --header "Authorization: Bearer <token>"
# Returns: HTTP 400

Common 400 errors:

Error	Detail message
Unsupported country code	`"the IBAN country code is currently not supported"`
Invalid check digit	`"IBAN check digit validation failed"`

Validate a Market Location ID

GET /v3/validation/market_location/

Validates an 11-digit German market location identifier (Marktlokations-ID / MaLo-ID). These identifiers are required when registering consumers (meteringpoint_id) or producers (market_location_identifier).

string

required

The 11-digit numeric market location identifier to validate.

Responses

200 OK — The market location ID is valid. No response body. 400 Bad Request — The ID failed validation.

string

A human-readable error message describing the validation failure.

curl --request GET \
  --url "https://api.lumenaza.de/v3/validation/market_location/?market_location_id=51238696600" \
  --header "Authorization: Bearer <token>"
# Returns: HTTP 200 (no body)

Common 400 errors:

Error	Detail message
Non-digit character	`"market location identifier contains non-digit character"`
Too many characters	`"market location identifier contains too many characters"`
Too few characters	`"market location identifier contains too few characters"`
Invalid start digit	`"market location identifier must start with a digit between 1-9"`
Invalid check digit	`"check digit validation failed"`

Market location IDs must be exactly 11 digits, start with a digit between 1 and 9, and have a valid check digit. Use this endpoint to validate user-entered IDs before submitting registration requests.

Validate a Preferred Delivery Start

GET /v3/validation/preferred_delivery_start/

Checks whether a proposed delivery start date is valid for a given customer type and subscription reason.

string

required

The proposed delivery start date in YYYY-MM-DD format.

string

required

The type of customer being registered.

string

required

The subscription reason code: E01 (move), E02 (new installation), or E03 (supplier switch).

Responses

200 OK — The delivery start date is valid. No response body. 400 Bad Request — The date is not valid for the given parameters.

string

A human-readable error message.

string

When the delivery start is too early, this field contains the earliest date that would be accepted (ISO date format).

Common 400 errors:

Error	Detail message
Unknown customer type	`"unknown customer_type"`
Unsupported change reason	`"unsupported change_reason for selected customer_type"`
Date not possible	`"delivery start to this date is not possible"` (includes `earliest_possible_delivery_start`)

Overview

API Endpoints

Validation Endpoints for IBAN and Market Location IDs

Validate an IBAN

Responses

Validate a Market Location ID

Responses

Validate a Preferred Delivery Start

Responses

​Validate an IBAN

​Responses

​Validate a Market Location ID

​Responses

​Validate a Preferred Delivery Start

​Responses

Validate an IBAN

Responses

Validate a Market Location ID

Responses

Validate a Preferred Delivery Start

Responses