The DPP registry now has documentation for developers

Kiril ShivachevKiril Shivachev•Published •7 min read
A fibre-optic patch panel with numbered ports and yellow cables

One faulty passport is enough to stop the other 99 in the same request from being registered. That rule is written into the documentation for the EU Digital Product Passport Registry. The European Commission published it on 30 October 2026, and the Directorate-General for Internal Market, Industry, Entrepreneurship and SMEs announced it officially on 16 November. It is the first time anyone has set down in black and white how a passport gets into the registry. For now, though, the description is all we have. Testing features will appear gradually before the registry is fully operational.

What the Commission published on 30 October

The Commission put six technical documents on its digital product passport resources page. All of them are version 1.0, dated 30 October 2026, and available in English only. Three matter most to manufacturers and importers:

  • the API Integration Guide explains how to submit passports for registration and how to track the result;
  • the Semantic Data Guide sets out the schemas and vocabularies the registry checks the data against;
  • the Self-Hosted Authentication Guide describes how the server hosting the passport has to respond to the registry.

The other three are the OpenAPI specifications, the semantic artefact files and the Service Account guide.

The registry has been running since 20 July 2026, but until now only organisations could register in it. The guide for economic operators still says that a passport cannot currently be registered successfully. The new documents describe how that will work. If you want to read about the registry itself first, we wrote about its launch in July.

Five endpoints, up to 100 passports per request, all or nothing

The registration interface for digital product passports, described in the API Integration Guide v1.0 of 30 October 2026, has exactly five public endpoints. The first returns the list of product groups and sub-groups the registry accepts. The second takes in the passports for registration. The other three show how far processing has got: a list of tasks, the status of a particular task, and the result for each passport individually (in JSON or CSV).

Registration does not happen on the spot. You send a request, the registry replies with code 202 and a task number, and you check the result later. Every request carries a mandatory key (Idempotency-Key). Thanks to it, if the connection drops and you send the same request again, you will not end up with duplicates.

The limits are specific:

  • from 1 to 100 passports per request, up to 10 MB in total;
  • one product group and one sub-group per request (for example batteries, sub-group LMT);
  • the request is atomic: if even one passport fails to meet the requirements, none of them is registered.

That last rule has a direct practical consequence. If you are an importer receiving passports from several suppliers, you are better off sending a separate request for each of them. Otherwise one error in one supplier's data will hold up everyone else's passports as well. The corrected set goes out as a new request with a new key.

The unique identifier must be a web address that opens the passport

According to the Commission's API documentation, the unique product identifier (UPI) must be an HTTPS URL between 8 and 2,000 characters long. The registry does not receive the passport itself in the request. It receives the address, opens it at the moment of the check and validates the content against Implementing Regulation (EU) 2026/1778. If the address does not open, the error is UPI_NOT_RESOLVABLE and, because the request is atomic, the whole request is rejected. The registry does not keep the content it has read.

That makes the order strict: first you publish the passport, then you register it. A supplier who tells you “we'll put it online once you've registered it” has the sequence backwards, and the registration will fail. A bare serial number from your own system is not a UPI either. It can be part of the address, but the registry wants an address that works.

The Self-Hosted Authentication Guide adds a few more rules for the server where the passport lives. The public part must open without a login, with no more than three redirects on the way. Protected data is released only when the registry presents a signed token from the Commission's authentication system, valid for 120 seconds at most. If the token is invalid, the server must refuse access. Quietly serving the public version in place of the protected one is not allowed.

Before the first request: a verified organisation and a service account

The DPP registry accepts requests only from an organisation that has been verified. Verification is done with a qualified electronic seal, and this is where companies often trip up, because an ordinary electronic signature will not do. We covered this in detail in our article on the electronic seal. Verified status lasts until the seal expires, but no longer than three years. After that, the registry accepts no new registrations or changes until the verification is renewed.

The requests to the API are sent by a service account. The Service Account guide, also dated 30 October, sets these limits:

  • the account is created by the organisation's administrator and is given the role “Register DPPs”;
  • an organisation can have no more than 5 such accounts;
  • each account can have up to 2 active keys, with a recommended validity of one year and a maximum of two;
  • the private key is the economic operator's responsibility: the operator generates it, stores it and controls it.

According to the guide for economic operators, the registry is not expected to charge a subscription fee. The real costs are the seal and the integration.

JSON is the only mandatory format, and for now only batteries have schemas

The Commission's Semantic Data Guide v1.0 says registration will require JSON, because it is the only mandatory format under the EN 18216:2026 standard. JSON-LD and XML are also checked if you send them, but they are not required. That is good news for small and medium-sized companies: they do not need linked data or RDF to register a passport.

Specific schemas and vocabularies so far exist only for batteries, in three sub-groups: electric vehicle batteries, industrial batteries and batteries for light means of transport (LMT). Textiles, furniture, iron and steel, and construction products share the common core of 12 basic concepts (identifier, status, date of last change, language and others), but do not yet have schemas of their own. They will get them with the delegated act for each group. The registration interface will stay the same; only the product group in the request will change.

Some things are still unclear. The documents have no complete catalogue of error codes and set no limits on the number of requests, and the format of the identifier the registry returns is not described. Nor has the Commission said when the registry will start accepting test passports for batteries. It is holding a webinar on the API and the semantic model on 26 November 2026. We will add anything new to our regulatory changes page.

What you can prepare before the testing features become available

With the registry documentation of 30 October you can start preparing now, without waiting for the registry to be fully operational:

  • check whether your organisation has a qualified electronic seal and when it expires;
  • decide who will be the administrator in the registry and where the service account's private keys will be kept;
  • ask your suppliers to confirm that their passports will be published at a working HTTPS address before you register them;
  • plan your requests by product sub-group and by supplier, so that a single error does not stop everything.

We at WIARA are building the DigitalProductPassport platform to the version 1.0 guides: passports are published in JSON at a permanent address, and each organisation's verified identifier is stored as a separate setting. We will test registration in the Commission's environment once the testing features become available. The private key for the registry stays with you, not with us. If you would like to know what this means for your products, write to us.

DigitalProductPassport in other countries: Albania · Bulgaria · Croatia · Czechia · Greece · Hungary · Poland · Romania · Serbia · Slovakia · Slovenia