Overview
Meter readings represent individual timestamped measurements from physical meters attached to consumer or producer contracts. Each reading captures an energy value in Wh along with metadata such as the measurement reason, data quality classification, OBIS number, and cancellation status. Readings are retrieved per contract and support rich filtering so you can query specific time windows, devices, or modification events. Base URL:https://api.lumenaza.de/ · Test URL: https://api.test.lumenaza.de/
A meter reading is uniquely identified by the combination of its
timestamp,
obis_number, and device_identification. Avoid treating any single
field alone as a unique key.Consumer Meter Readings
GET /v3/consumers/{userID}/contracts/{contractID}/meter_readings/
Returns a paginated list of meter readings for a specific consumer contract.Path Parameters
Query Filters
All filter parameters are optional. Date/time filters accept ISO 8601 datetime strings.Response Fields
Each reading in theresults array contains:
Cancellation
Whenis_cancelled is true, the meter operator has marked this reading as invalid. Readings can only be modified when they are in a cancelled state. Non-cancelled readings are considered finalized and locked.
Quality Values
Thequality field uses the following German-language classifications:
Example: Filter by Timestamp Range
Example Response
Producer Meter Readings
GET /v3/producers/{userID}/contracts/{contractID}/meter_readings/
Returns a paginated list of meter readings for a specific producer contract. The response structure and all filter parameters are identical to the consumer endpoint.Path Parameters
Supported Filters
All filters available on the consumer endpoint apply here as well. Thedevice_identification filter is particularly useful for producers with multiple meters or generation units on a single contract.

