oSIST prEN 18222:2025

Digital Product Passport - Application Programming Interfaces (APIs) for the product passport lifecycle management and searchability

This document aims to standardize the specifications for the API of the Digital Product Passport (DPP) as mandated by the ESPR of the European Commission. The purpose of this API is to facilitate the searchability of DPPs, as well as to provide the necessary means for interactions throughout the lifecycle of a product's DPP.

Digitaler Produktpass - Programmierschnittstellen (APIs) für das Lebenszyklusmanagement und die Durchsuchbarkeit vom Produktpass

Dieses Dokument soll die Spezifikationen für die API des digitalen Produktpasses (DPP) wie von der ESPR der Europäischen Kommission vorgeschrieben standardisieren. Der Zweck dieser API besteht darin, die Durchsuchbarkeit von DPPs zu verbessern und die erforderlichen Mittel für Interaktionen während des gesamten Lebensweges des DPP eines Produkts bereitzustellen.

Passeport numérique des produits - Interfaces de programmation d'applications (API) pour la gestion du cycle de vie et la recherchabilité du passeport d'un produit

Le présent document vise à normaliser les spécifications de l'API du passeport numérique de produit (DPP), tel que requis par le Règlement ESPR de la Commission européenne. L'objectif de ces API est de faciliter l’accès aux DPP, ainsi que de fournir les moyens nécessaires pour les interactions tout au long du cycle de vie du DPP d'un produit.

Digitalni potni list izdelka - Programski aplikacijski vmesniki (API) za upravljanje življenjskega cikla in možnost iskanja potnega lista proizvodov

General Information

• Status: Not Published
• Public Enquiry End Date: 18-Sep-2025
• ICS: 13.020.20 - Environmental economics. Sustainability
• ICS: 35.240.63 - IT applications in trade
• Technical Committee: DPP - Digital Product Passport
• Current Stage: 4020 - Public enquire (PE) (Adopted Project)
• Start Date: 17-Jul-2025
• Due Date: 04-Dec-2025
• Completion Date: 22-Sep-2025
• Mandate: M/604 - COMMISSION IMPLEMENTING DECISION of 31.7.2024 on a standardisation request to the European Committee for Standardisation, the European Committee for Electrotechnical Standardisation, and the European Telecommunications Standards Institute as regards digital product passports in support of Union policy on ecodesign requirements for sustainable products and on batteries and waste batteries
• Mandate: M/604 AMD 1 - COMMISSION IMPLEMENTING DECISION (EU) of 28.11.2025 amending Implementing Decision C(2024)5423 as regards the legal basis and the deadlines for the adoption of the standards.
• Ref Project: prEN 18222 - Digital Product Passport - Application Programming Interfaces (APIs) for the product passport lifecycle management and searchability

Overview

prEN 18222 (CEN draft) defines the Digital Product Passport (DPP) API specifications required by the European Sustainability Product Regulation (ESPR). The standard specifies a technology‑neutral set of methods to enable lifecycle management, searchability and registration of DPPs. A REST/HTTP mapping is provided in the draft to guide developers on practical implementation.

Key Topics

• Purpose: Standardize interfaces to read, create, update, delete and discover DPPs across custodians, service providers and archiving services.
• Main API methods (as specified): ReadDPPById, ReadDPPByProductId, ReadDPPIdsByProductIds, CreateDPP, UpdateDPPById, DeleteDPPById, ReadDPPVersionByProductIdAndDate, and PostNewDPPToRegistry.
• Fine‑grained operations: Support for reading and updating specific data element collections and single data elements (for partial updates and targeted queries).
• Inputs / outputs: Methods uniformly return a statusCode and payload (DPP or identifiers). Discovery endpoints support pagination via limit and cursor.
• Lifecycle & registry: Includes a Registry API method (PostNewDPPToRegistry) to register DPPs with the EC registry and return a registry identifier.
• Security, archiving & interoperability: The draft references Modules for payload content, exchange protocols, security requirements and archiving (Module 4, 5, 6, 7). Access control governs create/update/delete operations; archiving requirements apply to all DPP changes.
• Implementation guidance: The draft provides REST/HTTPS mappings and cites RFCs (e.g., RFC 7396 and RFC 5261 referenced in the text) as possible guidance for partial update semantics and message handling.

Applications

• Manufacturers & brand owners: Expose product sustainability data and lifecycle records via a standardized DPP API to meet ESPR obligations.
• Marketplaces & retailers: Discover and retrieve current DPPs for product listings, compliance checks and consumer transparency.
• Service providers / custodians: Host, update and archive DPPs; implement registry integration and provide searchability.
• Regulators & auditors: Query registered DPPs and historical versions for compliance verification.
• Developers / integrators: Implement REST/HTTP services conforming to the API mapping to ensure interoperability across the DPP ecosystem.

Related Standards

• ESPR (European Sustainability Product Regulation) - legal mandate motivating the DPP.
• CEN/CLC/JTC 24 outputs - the technical committee producing this draft.
• Module documents referenced in the draft: Module 4 (content), Module 5 (data exchange protocols), Module 6 (archiving), Module 7 (security).

Keywords: Digital Product Passport, DPP API, ESPR, lifecycle management, searchability, registry API, REST API, product lifecycle.

Standards Content (Sample)

SLOVENSKI STANDARD
01-september-2025
Digitalni potni list za proizvode - Programski aplikacijski vmesniki (API) za
upravljanje življenjskega cikla in možnost iskanja potnega lista proizvodov
Digital Product Passport - Application Programming Interfaces (APIs) for the product
passport lifecycle management and searchability
Digitaler Produktpass - Programmierschnittstellen (APIs) für das
Lebenszyklusmanagement und die Durchsuchbarkeit vom Produktpass
Passeport numérique des produits - Interfaces de programmation d'applications (API)
pour la gestion du cycle de vie et la recherchabilité du passeport d'un produit
Ta slovenski standard je istoveten z: prEN 18222
ICS:
13.020.20 Okoljska ekonomija. Environmental economics.
Trajnostnost Sustainability
35.240.63 Uporabniške rešitve IT v IT applications in trade
trgovini
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EUROPEAN STANDARD DRAFT
NORME EUROPÉENNE
EUROPÄISCHE NORM
June 2025
ICS 13.020.20; 35.240.63
English version
Digital Product Passport - Application Programming
Interfaces (APIs) for the product passport lifecycle
management and searchability
Passeports numériques de produit - interfaces de Digitaler Produktpass -
programmation d'applications (API) pour la gestion du Anwendungsprogrammierschnittstellen (APIs) für die
cycle de vie et la recherchabilité du passeport d'un Lebenszyklusverwaltung, Auffindbarkeit und
produit Durchsuchbarkeit des Produktpasses
This draft European Standard is submitted to CEN members for enquiry. It has been drawn up by the Technical Committee
CEN/CLC/JTC 24.
If this draft becomes a European Standard, CEN and CENELEC members are bound to comply with the CEN/CENELEC Internal
Regulations which stipulate the conditions for giving this European Standard the status of a national standard without any
alteration.
This draft European Standard was established by CEN and CENELEC in three official versions (English, French, German). A
version in any other language made by translation under the responsibility of a CEN and CENELEC member into its own language
and notified to the CEN-CENELEC Management Centre has the same status as the official versions.

CEN and CENELEC members are the national standards bodies and national electrotechnical committees of Austria, Belgium,
Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy,
Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Republic of North Macedonia, Romania, Serbia,
Slovakia, Slovenia, Spain, Sweden, Switzerland, Türkiye and United Kingdom.

Recipients of this draft are invited to submit, with their comments, notification of any relevant patent rights of which they are
aware and to provide supporting documentation.Recipients of this draft are invited to submit, with their comments, notification
of any relevant patent rights of which they are aware and to provide supporting documentation.

Warning : This document is not a European Standard. It is distributed for review and comments. It is subject to change without
notice and shall not be referred to as a European Standard.

Contents Page
European foreword . 3
Introduction . 4
1 Scope . 5
2 Normative references . 5
3 Terms and definitions . 5
4 Specification of the Life Cycle API (Main Methods) . 6
4.1 General . 6
4.2 Method ReadDPPById . 6
4.3 Method ReadDPPByProductId . 6
4.4 Method ReadDPPVersionByProductIdAndDate . 7
4.5 Method ReadDPPIdsByProductIds . 7
4.6 Method CreateDPP . 8
4.7 Method UpdateDPPById . 8
4.8 Method DeleteDPPById . 9
5 Specification of the Registry API for Register . 9
5.1 General . 9
5.2 Method PostNewDPPToRegistry . 9
6 Specification of the Fine Granular API Operations of the Life Cycle API . 10
6.1 General . 10
6.2 Method ReadDataElementCollection . 10
6.3 Method ReadDataElement . 10
6.4 Method UpdateDataElementCollection . 11
6.5 Method UpdateDataElement . 11
7 Status Code, Error Handling & Result Messages . 12
8 Mappings . 13
8.1 General . 13
8.2 HTTPS/REST for Life Cycle API . 13
8.3 HTTPS/REST for Register API for Register . 14
8.4 HTTPS/REST for Fine Granular Life Cycle API . 14
Annex ZA (informative) Relationship between this European Standard and the ecodesign
requirements of Commission Regulation (EU) No 2024/1781 aimed to be covered . 15
Bibliography . 17
European foreword
This document (prEN 18222:2025) has been prepared by Technical Committee CEN/CLC/JTC 24
"Digital Product Passport – Framework and System", the secretariat of which is held by DIN.
This document is currently submitted to the CEN Enquiry.
This document has been prepared under a standardization request addressed to CEN by the European
Commission. The Standing Committee of the EFTA States subsequently approves these requests for its
Member States.
For the relationship with EU Legislation, see informative Annex ZA, which is an integral part of this
document.
Introduction
The European Sustainability Product Regulation (ESPR) is an initiative by the European Commission
aimed at promoting sustainable products by setting comprehensive requirements for product design,
production, and lifecycle management. Central to this initiative is the Digital Product Passport (DPP),
which tracks and provides essential information about a product's sustainability attributes. Beside of
that also other data can be stored in a DPP depending on future delegated acts and the needs of economic
operators.
This document introduces the spécifications for the API of the DPP, as mandated by the ESPR. The API
is designed to enhance the searchability of DPPs and to support interactions throughout the lifecycle of
a product's DPP. Furthermore, it also provides an API to register a DPP at the DPP registry.
The API methods are presented on a technology-neutral level, detailing the expected inputs and outputs
for each method. A detailed technological implementation using a REST-HTTP API is described in the
Clause 9, providing guidelines for developers to implement the functionality effectively within their
spécific environments.
The spécification document of Module 4 “System Interoperability” describes the logical content of the
payload that is used by the API. Module 5 “Data Exchange Protocols” définés the basic principles of the
exchange protocol and the allowed serialization formats of the payload data. Security requirements
need to be followed based on the spécification document of Module 7.
1 Scope
This document aims to standardize the spécifications for the API of the Digital Product Passport (DPP)
as mandated by the ESPR of the European Commission. The purpose of this API is to facilitate the
searchability of DPPs, as well as to provide the necessary means for interactions throughout the lifecycle
of a product's DPP.
2 Normative references
There are no normative references in this document.
3 Terms and definitions
For the purposes of this document, the following terms and définitions apply.
ISO and IEC maintain terminology databases for use in standardization at the following addresses:
— ISO Online browsing platform: available at http://www.iso.org/obp
— IEC Electropedia: available at http://www.electropedia.org/
3.1
API
application programming interface
set of methods provided by an application component for use by other application components
3.1.1
REST API
representational state transfer application programming interface
service that allows for interaction with resources via a stateless, client-server architecture, typically
using standard HTTP calls like GET, POST, PUT, and DELETE to perform methods by an application
component on these resources
3.2
digital product passport
DPP
digital record of product characteristics throughout its life cycle
Note 1 to entry: Example characteristics include environmental sustainability, environmental impact, and
recyclability
3.3
method
particular way used to perform a spécific action on a resource
EXAMPLE        Read a DPP.
3.4
parameter
data provided by a client, that is needed to perform a method
EXAMPLE        DPP ID for read DPP.
3.5
result
return value after the execution of a method
EXAMPLE        The DPP.
4 Specification of the Life Cycle API (Main Methods)
4.1 General
In this clause only the API methods as can be made available by the custodian of a DPP (either economic
operator or service provider) is contained. This methods are spécifiéd in abstract manner, the precise
implementation is provided in Clause 8, which also contains information how the input and output
parameters are provided.
The following methods shall be made available by the custodian of DPPs and by archiving services:
— ReadDPPById
— ReadDPPByProductId
— ReadDPPIdsByProductIds
The following methods should be made available by a service provider of DPPs and by archiving services:
— CreateDPP
— DeleteDPPById
— ReadDPPVersionByProductIdAndDate
The following methods shall be made available by the custodian of DPPs if authorized third parties shall
have the access rights to update parts of the DPP:
— UpdateDPP
In case of archiving services no update of DPPs is requested any longer.
In principal, the DPP API will offer these set of methods, that is requested with some parameters,
performing a behaviour (e.g. execution an action), and responding with a result. These expectations are
formally described for each method in the following subclauses.
4.2 Method ReadDPPById
This method returns the DPP through a known DPP idéntifiér. See Table 1.
Table 1 — ReadDPPById
Method Name ReadDPPById
Explanation Returns the DPP with the spécifiéd DPP ID
semanticId https://jtc24/dpp/API/ReadDPPById/1/0
Name Description Mand. Type Card.
Input Parameter
dppIdéntifiér The DPP’s unique ID yes Idéntifiér 1
Output Parameter
statusCode Status code yes StatusCode 1
payload Requested DPP yes DPP 1
4.3 Method ReadDPPByProductId
This method returns the current active DPP (latest version) through a known product idéntifiér. See
Table 2.
Table 2 — ReadDPPByProductId
Method Name ReadDPPByProductId
Explanation Returns the current active DPP with the spécifiéd Product ID
semanticId https://jtc24/dpp/API/ReadDPPByProductId/1/0
Name Description Mand. Type Card.
Input Parameter
productIdéntifiér Product ID yes Idéntifiér 1
Output Parameter
statusCode Status code yes StatusCode 1
payload Requested DPP yes DPP 1
4.4 Method ReadDPPVersionByProductIdAndDate
This method returns a DPP based on its product idéntifiér and given date. The method is optional for
the economic operator. See Table 3.
Table 3 — ReadDPPVersionByProductIdAndDate
Method Name ReadDPPVersionByProductIdAndDate
Explanation Returns a DPP version based on its product idéntifiér and given date
semanticId https://jtc24/dpp/API/ReadDPPVersionByProductIdAndDate/1/0
Name Description Mand. Type Card.
Input Parameter
productIdéntifiér Product ID yes Idéntifiér 1
date Date value for which yes Timestamp (UTC- 1
the DPP is requested based)
Output Parameter
statusCode Status code yes StatusCode 1
payload Requested DPP yes DPP 1
4.5 Method ReadDPPIdsByProductIds
This method returns a list of DPP idéntifiérs that matches a set of product idéntifiérs.
The input parameters "limit" and "cursor" can be set by the client to control pagination. The value of
the cursor shall not be empty. See Table 4.
Table 4 — ReadDPPIdsByProductIds
Method Name ReadDPPIdsByProductIds
Explanation Returns a list of DPP idéntifiérs based on discovery information (key-value-pairs of
product idéntifiying information)
semanticId https://jtc24/dpp/API/ReadDPPIdsByProductIds/1/0
Name Description Mand. Type Card.
Input Parameter
productId Product IDs yes Idéntifiér 1
limit The maximum size of no nonNegativeInteger 1
the result set
cursor The position from no string 1
which to resume a
result listing
p
...