How broker agencies and large property managers benefit from the Energyausweis API™

Joost Jansky

Energieberater, Blogger

Significant admin load many partners will feel even more with the GModG

For you, the certificate is rarely the core product — it is the bottleneck between property file, listing and appointment. Sale, new tenancy, change of owner, HOA resolution: the same question appears everywhere whether a valid certificate exists and whether mandatory listing fields are correct. As long as the team orders via an external provider link and stores the PDF manually, metrics, deadlines and status are missing from your in-house data records.

That is why the effective date matters: from 1 January 2027 Article 2 of the GModG applies (GEG §§ 79–88). New certificates must be digital and machine-readable ( § 79(2) GEG; formats and practice: digital certificate from 2027 ). Article 2 changes little about how long a certificate stays valid. What is new are mainly more reasons to issue or update certificates, consumption data duties and listing fields you must keep current in property files, listings and portfolios — not as a PDF filed once and then dropped from everyday work.

What becomes due from 1 January 2027

Article 2 EPBD duties affect everyone who markets or manages property commercially. Here is an overview of your duties that an API integration can simplify:

These duties do not live in a PDF attachment — they live in your systems: on lease renewal, certificate status and deadlines; annual consumption from HeizkostenV billing; structured modernisation recommendations and pre-fill for exposés. Who still solves that manually with forward links does not scale — and you lose contacts and orders to third parties.

Where spreadsheets, e-mail and external provider links still cause media breaks

The media break is not merely awkward — it is costly and carries legal and operational risks: duplicate data entry, outdated metrics in listings, no team-wide status. The comparison below shows why an API integration becomes essential as volume grows:

Rule of thumb from agency practice: from five to ten new certificates per year an external source pays off; from twenty onward direct CRM or management software integration is the obvious path — lower unit cost, fewer breaks, you keep clients tied to your brand. Agent risk details are in the GModG guide for agents.

The Energyausweis API™ as a building block in CRM and management software

The Energyausweis API™ is not a document stub — it is a platform service for the full certificate lifecycle: create, capture building and consumption data, upload evidence via presigned URLs, order, poll status, receive PDF and structured JSON for listing fields. Issuance and technical review under § 88 GEG is handled by energyausweis.de — with certified assessors and DIBt registration — without having to build an in-house consultant team.

For integration, your developers use secure authentication and separate test and production environments — so you can validate workflows before clients order in production. Partners pay no hidden fees per API call; you are billed when a certificate is actually issued. The full product story is in the main API overview article; the product page summarises value by audience.

White-label, margin and CRM pre-fill

The API becomes economically interesting when you serve end customers under your brand and determine the end price yourself. The partner programme offers two paths:

• Affiliate: refer to energyausweis.de; commission on list price — 20% standard, up to 30% at higher monthly volume.
• API partner: you determine the end-customer price yourself (white-label in the order flow and on the PDF). That way you keep margin above your purchase price — terms in conversation.

At the same time the API solves § 87 pre-fill: metrics, class, energy carriers, year of construction and registration number return as structured fields — not a text block to retype. For broker CRMs and management portals that is the difference between “listing approved” and “listing waiting for a callback”.

OpenAPI specification: integration and try-out

Your developers work from the spec and sandbox — not from marketing decks. The API is specified in OpenAPI 3.1.2; at /api/try-out there is a simple UI for testing — with many examples, including error cases down to field level, ready to try and test. Useful when your interface should show feedback directly in the form. The machine-readable specification is at /api/spec.

Liability: who checks what — clearly assigned

Partners rightly ask who checks what — and who is liable for what. Here is how responsibility is divided:

The API reduces error sources (pre-fill, status, less duplicate care) but does not remove your data duties or the advertiser’s duty under § 87. Sensible integration means planning for management contracts, brokerage mandates and § 108 GModG fine risk from the start — the API helps you meet these duties and significantly reduces error and fine risk.

A trustworthy service behind the API — backed by customer reviews

White-label means the end customer does not leave your client portal to order an energy certificate. As an API partner you delegate issuance — you still need a reliable issuer you can depend on — on deadlines, status, document quality and your clients’ follow-up questions.

energyausweis.de is that service — not just an interface. On energyausweis.de/kundenstimmen/en we publish curated customer reviews on turnaround, price transparency and the online process; the aggregate rating profile is on ProvenExpert. That way you can show clients: behind your brand stands a provider that other owners and agents have already rated — not an anonymous background service.

You do not need to embed testimonials and ProvenExpert in your client portal. In conversation, a link or brief reference is often enough for “Is this serious?” and “How fast is it?” — and you can plan the API integration without having to rely on the issuer unchecked.

Live integrations and steady partner inquiries

Over recent months we see several productive API integrations in different software environments — from broker and management workflows to embedded order modules. At the same time, partner inquiries about white-label, test credentials and CRM pre-fill are increasing, often with the same driver — for many teams GModG 2027 is still on the implementation list, which should be completed by 1 January 2027.

Whether broker software, a management portal or an embedded order module — the same technical pattern keeps showing up: integration with your software instead of a parallel island solution, JSON for listing and expose fields, PDF for the file and handover. White-label, pre-fill and upcoming GModG mandatory disclosures scale on that stack — without rebuilding the flow for every property.

What everyday work feels like with an integrated certificate

Your Monday without an urgent energy-certificate to-do list: in your online portal, every property shows energy certificate status — valid until, in progress or due — at a glance. A lease renewal starts the status check automatically. The listing pulls metrics from the API response; nobody retypes the efficiency class. The owner uploads photos in your client portal; your team sees progress like any other pipeline stage.

That is the difference between “another to-do beside daily work” and “certificate is part of the property workflow”. That is why it pays to integrate before 1 January 2027 — and beyond.

FAQ before you integrate the API

Is the API worth it before 1 January 2027?

Yes if media breaks already mean noticeable extra work and error risk. The test environment is free; 2027 GModG fields roll out on Article 2 timing — integration still needs lead time.

What does the API cost?

API usage is free for partners; issued certificates are billed. Affiliate: commission on list price (up to 30% at volume). API: your end-customer price.

What liability does energyausweis.de assume?

energyausweis.de handles issuance under § 88 GEG: technical review, calculation, DIBt registration number and a legally compliant PDF — with certified assessors. You as the partner remain responsible for complete, plausible building and consumption data, your processes and deadlines, and correct § 87 disclosures in listings; API pre-fill does not replace the advertiser’s duty to check — see the table above.

Can we push mandatory fields into CRM or listing templates?

Yes. Besides the PDF the API returns structured JSON — certificate type, metrics, energy carriers, year of construction, efficiency class, DIBt registration number and status. Listing and exposé modules can be filled automatically without retyping values.

How do developers get an overview?

At /api/try-out you will find the OpenAPI 3.1.2 reference with a simple UI for testing, separate test and production environments and secure authentication via API key. The machine-readable specification is at /api/spec.

Is the issuer behind the API trustworthy?

Yes — regardless of white-label: testimonials and ProvenExpert document the energyausweis.de service (turnaround, transparency, serious issuance). You use the API; you can give your clients verifiable trust while ordering stays in your client portal.

How to get started as an API partner

1. Clarify use case and volume — sales, new tenancy, renewal, portfolio; leading system (CRM vs. management portal).
2. Choose partner model — affiliate or API white-label in the partner programme.
3. Try-out — walk through OpenAPI at /api/try-out with a test token.
4. Plan CRM pre-fill and renewal checks — § 87 fields, deadlines, lease renewal; sharpen contracts.
5. Pilot and production launch — one office or anchor client, then phased rollout with production key.

Next steps

If you develop and operate property management software or real-estate platforms, the platform GModG article offers more tips on integration and our integration support. For a conversation on volume, white-label and joining the partner programme: Contact.