# How to register a Digital Product Passport: the EU registry API explained
> The EU DPP registry has been live since July, and the Commission has now published how to connect to it. Here is how registration works, what it needs, and what it means for brands.

Category: Compliance
Author: SmartLinks Team
Published: 2026-11-22
Tags: DPP, ESPR, EU Registry, API, Battery Passport, Compliance
Canonical URL: https://www.smartlinks.app/blog/eu-dpp-registry-api-how-to-register
Featured image: https://cdn.smartlinks.app/sites/kfcu8dvu5e/a/89147d84-7870-4119-9318-6644923db7d3
---
The EU Digital Product Passport registry has been live since 20 July 2026. On 30 October 2026 the European Commission published the technical documents that show how a brand, or the software working for it, actually registers a passport. This is a plain-English summary of what those documents say, and what it means if you are preparing for the first mandatory DPPs.

## What the registry is for

The central registry is the single point where competent authorities and customs can check that a product has a passport before it is placed on the market. It does not hold the passport itself. The passport data stays with you or your DPP provider, and the registry holds the pointer to it, tied to the product's unique identifier.

## What the Commission published on 30 October

- An **API Integration Guide for economic operators** (version 1.0)

- The **API specifications** and semantic data files

- A **Service Account guide** and a **Self-Hosted Authentication guide**

They sit on the Commission's DPP resources page, alongside the registry user guide for the web interface.

## How registration works through the API

- **Verify your organisation.** Protected calls need a bearer token, and the organisation must have completed verification first.

- **Use a service account for automation.** Machine clients sign in with a service account that has the "Register DPPs" role.

- **Submit your products.** The call is `POST /api/v1/dpp/submission`. The body names the product group and sub-group and lists the items being registered, each with its unique product identifier, granularity (model, batch or item), and batch and model identifiers where they apply.

- **Send an idempotency key.** Every submission needs one, so a retry never registers the same thing twice.

- **Poll for the result.** Registration is asynchronous. The registry replies with a task ID, and you check `GET /api/v1/tasks/{taskId}` until it completes.

There is also a separate test registry, which needs its own EU Login account, so you can try all of this before anything is real.

## The standards behind it

The unique identifier and data carrier rules come from the new CEN-CENELEC standards (EN 18216 and EN 18219 to EN 18223), which the Commission referenced in July 2026. Two more standards were still pending when we last checked, and the Commission's timeline pointed to November. In practice that means GS1 Digital Link style identifiers on a QR code or NFC tag, resolving to your passport data.

## What this means for brands

- **Batteries come first.** The battery passport becomes mandatory on 18 February 2027 for EV, light means of transport and industrial batteries over 2 kWh.

- **Other product groups follow.** The Commission's indicative plan has iron and steel next, then the DPP service provider rules and construction materials in 2027, textiles, tyres and aluminium later in 2027, furniture in 2028 and mattresses in 2029. Each act gives at least 18 months' transition, and the dates can move.

- **Identifiers matter now.** Every item, batch or model needs a stable unique identifier before it can be registered. If your labelling is not ready, that is the long lead item.

- **Nobody has to code to the API alone.** Most brands will register through a DPP provider rather than integrating directly.

## What we are doing

SmartLinks already runs a production GS1 Digital Link resolver and serves structured passport data. We are building registry submission against the Commission's published API and will announce when it is live. If you want to see how the pieces fit, our [CIRPASS reference architecture](/resources/cirpass-reference-architecture) maps each requirement, and the [DPP timeline](/resources/dpp-timeline) tracks the dates above.

_This is a summary, not legal advice. Check the Commission's documents for the authoritative text, and note that dates for later product groups are indicative._