Digital EPDs: From PDFs to Plug-and-Play Data in XML or JSON

Goodbye copy-paste, hello API

For two decades EPDs meant a forty-page PDF that building teams had to hand-key into their tools. Today, many major program operators also provide a machine-readable file (ILCD+EPD XML and/or JSON) alongside the PDF, and uptake is clearly accelerating (ECO Platform, 2025).

The core schemas you will meet

• ILCD+EPD: the established XML schema used by ECO Platform databases and many European operators; support spans everything from free viewers to enterprise LCA suites (InData, 2024).
• openEPD: a JSON/JSON-LD spec developed since ≈ 2021–2022 to simplify API exchange and versioning; early implementers include Building Transparency’s EC3 ecosystem and Smart EPD (openEPD Forum, 2025).
• ECO Portal CSV export: a simple table format that some teams prefer for quick Buy-Clean bids, provided alongside ILCD XML (ECO Platform, 2025).

Each covers the same impact tables yet handles metadata and units a bit differently, so plan on a conversion step if you publish into multiple hubs.

Where to pull ready-made files

1. ÖKOBAUDAT and INIES provide machine-readable endpoints (ILCD/soda4LCA principles) that let tools fetch digitized EPD data; PDFs and verification details are available, though attachments vary (INIES, 2025).
2. EC3 hosts ≈ 200 000 digitized EPDs and offers a free REST API (account required; usage limits apply) (Building Transparency, 2025).
3. IBU makes ILCD XML downloads available via IBU.data (IBU, 2025).

What is bubbling up next

BIM integration: ISO 22057 defines data templates for using EPD data in BIM, paving the way for smoother hand-offs with IFC-based models (ISO 22057, 2022).

Digital trust: sector initiatives such as ECO Portal and openEPD are adding provenance features and cryptographic checksums to cut down fake or expired declarations (ECO Platform, 2025).

Knowledge graphs: the openEPD community is exploring SKOS vocabulary alignment, letting search engines reason over synonyms like “gypsum board” and “drywall”. There is still debate about region-specific terms.

Five moves to get ready this quarter

1. Ask your team to store internal BoM data in SI units. Data-type mismatches are the top cause of failed ILCD uploads.
2. Keep process IDs stable across upgrades; changing them forces re-validation in third-party hubs.
3. Budget a half-day for schema validation on each new EPD. Free online checkers exist and save bruised pride later.
4. Document plant location to six decimal places; many Buy-Clean calculators auto-label impacts by grid region.
5. Reserve room in your LCA model for “additional modules”. Emerging PCR revisions will push more end-of-life scenarios into the digital file.

The payoff in plain numbers

Manufacturers that supply a clean XML or JSON file see their products appear in EC3 searches up to six weeks sooner than PDF-only peers (Building Transparency internal API stats, 2025). Faster visibility means earlier spec wins, and on public projects a compliant digital EPD increasingly acts as the ticket to bid.

Tying it together

Machine-readable EPDs turn compliance paperwork into living data that flows from your production line to the architect’s model without friction. Invest a few hours in schema hygiene now and your next declaration will not just sit in a folder—it will sell.