messpunkt.io runs the ETL and aggregation layer for German sub-metering — Wärme, Wasser, Heizkostenverteiler, Strom. Our Partner API lets your ERP read consumption and meter-reading data on behalf of a landlord, with an auth model a compliance officer will sign off on.
1.0.0-rc.2 · SemVer · changelog/v1 · 6 months deprecation overlapA contract designed so your integration stays the same as the industry standards underneath it evolve.
Generate a client for C#, Java, TypeScript, Python with openapi-generator-cli. No anyOf escape hatches, every field typed.
User-delegated tokens, scoped per Tenant, sender-constrained against token theft. DPoP guide →
Landlord picks which Liegenschaften an ERP can see. Out-of-scope queries return 404, never 403 — no scope enumeration.
Every reading carries an OBIS code (IEC 62056-6-1). Compare across vendors without bespoke mapping tables.
Device changes are first-class: separate segments, clear installation windows. You never have to diff serials to detect a swap.
Synthetic data from real production distributions. Runs a full OAuth flow. Same fixture every time — reproducible demos.
One source of truth. REST and (later) BVED 3.10 XML are two renderings on top.
Read-only in V1. Write endpoints (ERP pushes its external_ref) are planned for V1.1.
The one-picture version: landlord consent with a Property picker, runtime requests with DPoP-bound tokens + server-side scope filtering, and later scope edits via the dashboard — all three phases in one sequence.
Source: auth-flow.mmd (Mermaid sequence diagram) · SVG generated via mermaid-cli.
Three ways in, depending on what you're here to do.
Four shell commands from zero to your first authenticated call, with the full OAuth 2.1 + PKCE round-trip.
Start the walkthroughEvery endpoint, schema, example, OBIS code, error response — rendered in Redoc with search and code samples.
Open the reference13 pre-wired requests covering every endpoint and scenario. Download the zip, click Get Access Token, send.
Download the collectionEvery status code, the type suffix, whether it's retryable, and the recommended client action.
Sender-constraining tokens with working code in C#, Node, Python, and curl. Required for GA.
Implement DPoPScalar with built-in OAuth flow, code-sample tabs for 8 languages, and Test Request against the live sandbox.
Open in ScalarWe're actively working with property-management ERPs on the V1 contract before GA. Integration time is typically 3–5 days for a seasoned .NET or Java team. Feedback shapes the final shape of the schema.