EN 18222: the calls a back-up provider offers

Which EN 18222 calls must a back-up provider offer? Under clause 4.1, three read calls are a must: ReadDPPById, ReadDPPByProductId and ReadDPPIdsByProductIds. ReadDataElement, CreateDPP, DeleteDPPById and ReadDPPVersionByIdAndDate are recommended. dpp-backup.com offers all of them except ReadDataElement.

EN 18222:2026, Digital Product Passport – Application Programming Interfaces (APIs) for the product passport lifecycle management and searchability, describes the calls of a passport interface in abstract terms (clause 4) and maps them to HTTPS paths (clause 8). Commission Implementing Decision (EU) 2026/1736 cites it as a harmonised standard under ESPR. This page sums up the standard in our own words; it does not reproduce its text.

What clause 4.1 asks of a back-up provider

CallEN 18222 4.1dpp-backup.com
ReadDPPById (4.2)Shall be offeredOffered
ReadDPPByProductId (4.3)Shall be offeredOffered
ReadDPPIdsByProductIds (4.5)Shall be offeredOffered
ReadDataElement (6.2)Should be offeredNot offered
CreateDPP (4.6)Should be offeredOffered
DeleteDPPById (4.8)Should be offeredAnswers, and always refuses with 405: a back-up copy is kept for the life of the passport
ReadDPPVersionByIdAndDate (4.4)Should be offeredOffered
UpdateDPPById (4.7)Asked of the creator or its main provider when third parties may update the passportOffered, so your platform can send each change

"Shall" is a requirement of the standard. "Should" is a recommendation.

The calls in short

  • ReadDPPById returns the passport with a known passport id.
  • ReadDPPByProductId returns the current active passport, the latest version, for a unique product identifier as in EN 18219.
  • ReadDPPVersionByIdAndDate returns the version of a passport that applies at a given date and time, in UTC, written as in ISO 8601-1.
  • ReadDPPIdsByProductIds returns the passport ids that match a set of product identifiers.
  • CreateDPP creates a passport and returns its id.
  • UpdateDPPById sends only the parts that change. If one part fails, the whole update fails and nothing changes. Every change is archived as EN 18221 asks.
  • DeleteDPPById removes a passport, at the end of its life, if the access rules allow it.

For each call, access rules decide which data elements come back and whether a change is allowed.

The HTTPS paths (clause 8.2)

CallMethod and path
ReadDPPByIdGET v1/dpps/{dppId}
ReadDPPByProductIdGET v1/dppsByProductId/{productId}
ReadDPPVersionByIdAndDateGET v1/dppsByIdAndDate/{dppId}?date={timestamp}
ReadDPPIdsByProductIdsPOST v1/dppsByProductIds
CreateDPPPOST v1/dpps
UpdateDPPByIdPATCH v1/dpps/{dppId}
DeleteDPPByIdDELETE v1/dpps/{dppId}

Clause 8.1 adds that an id in a path should be percent-encoded, and that RFC 7396 (JSON merge patch) can be used for updates. Clause 4.1 recommends content negotiation as in EN 18216 when a call can answer in more than one format.

Errors (clause 7.2)

A failed call should return a result object with one or more messages. Each message has a type (Info, Warning, Error or Exception), a text, and may have a code and a time. Table 15 maps the status codes to HTTP: for example 400 for a bad request, 401 for missing credentials, 404 for not found, 405 for a method that is not allowed and 409 for a resource that exists already.

How dpp-backup.com uses it

  • Your platform sends with CreateDPP and UpdateDPPById, on the paths of clause 8.2 under https://dpp-backup.com/api/v1.
  • Updates are JSON merge patches. If the merged passport is not valid, nothing is stored.
  • A refused call gets the result object of clause 7.2.
  • The four read calls answer from the copy, on a domain that is open for reading.

Docs · EN 18221

Keep a back-up copy of your passports

Create an organisation with your company email. Once it is approved, you connect the platform that holds your passports.

A company email address is required. Our staff review new organisations on working days. The portal is in English.