messpunkt.io Partner API · Documentation
Preview · 1.0.0-rc.2 V1 release candidate — target GA Q2 2026. Become a pilot partner: kontakt@messpunkt.io
For property-management ERPs

Metering data, by the book.

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.

OpenAPI 3.1 · fully typed
OAuth 2.1 + PKCE + DPoP
Live sandbox · zero PII
API version
1.0.0-rc.2 · SemVer · changelog
Stability contract
No breaking changes within /v1 · 6 months deprecation overlap
Standards
OAuth 2.1 · RFC 9449 · RFC 7807 · IEC 62056 OBIS
Security contact

What's in the box

A contract designed so your integration stays the same as the industry standards underneath it evolve.

OpenAPI 3.1, fully typed

Generate a client for C#, Java, TypeScript, Python with openapi-generator-cli. No anyOf escape hatches, every field typed.

OAuth 2.1 + PKCE + DPoP

User-delegated tokens, scoped per Tenant, sender-constrained against token theft. DPoP guide →

Property-level scope

Landlord picks which Liegenschaften an ERP can see. Out-of-scope queries return 404, never 403 — no scope enumeration.

OBIS-aligned metrics

Every reading carries an OBIS code (IEC 62056-6-1). Compare across vendors without bespoke mapping tables.

Meter replacement, explicit

Device changes are first-class: separate segments, clear installation windows. You never have to diff serials to detect a swap.

Live sandbox, zero PII

Synthetic data from real production distributions. Runs a full OAuth flow. Same fixture every time — reproducible demos.

The canonical model

One source of truth. REST and (later) BVED 3.10 XML are two renderings on top.

Tenant // Vermieter-Organisation └─ Property // Liegenschaft └─ UsageUnit // Wohn-/Gewerbeeinheit └─ MeasuringPoint // stable across swaps └─ Device // installation window └─ Reading // timestamped value

Endpoints at a glance

Read-only in V1. Write endpoints (ERP pushes its external_ref) are planned for V1.1.

  • GET/v1/whoamiVerify token + scope
  • GET/v1/propertiesList Liegenschaften
  • GET/v1/usage-unitsList units, filterable
  • GET/v1/usage-units/{id}/consumptionUnit-level billing
  • GET/v1/measuring-points/{id}/readingsPer-meter drill-down

How the auth flow works

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.

Sequence diagram: consent with Property picker, authorized runtime requests with DPoP-bound tokens, scope updates from the landlord dashboard.

Source: auth-flow.mmd (Mermaid sequence diagram) · SVG generated via mermaid-cli.

Pick your path

Three ways in, depending on what you're here to do.

Pilot partner spots are open.

We'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.

Talk to partnerships Or start the Quickstart