Notes · 30 September 2026
EUDAMED certificate expiry dates
Public EUDAMED certificate expiry hangs on the basic UDI-DI, not the label UDI-DI. If the date is absent, the public response had none.
Searching for an EUDAMED certificate expiry usually means one of two jobs: a notified-body certificate is about to lapse, or someone wants proof that a device on a quote still has a valid CE certificate. The public register can help with the first only when the certificate was published against a basic UDI-DI that you can reach from the device.
Where the date actually lives
The UDI-DI detail often does not carry the expiry. The public certificate search does, and it expects the identifier type “basic UDI-DI” plus the basic UDI-DI value. That follows from how certificates are registered: the notified body selects basic UDI-DIs in scope, with an issue date, a start of validity, and an expiry. Expired certificates are marked in the Commission’s own certificate screens. A reissued certificate can point at the one it replaced.
So a serious lookup is three steps, not one:
- Resolve the UDI-DI from the label.
- Read the basic UDI-DI on that device.
- Search certificates with that basic UDI-DI and read number, expiry, and status.
UDI-DI 10887714028257 is a case where step 3 returns a date. UDI-DI 16977660098955 is a case where it does not. Both pages say which of those happened. Neither page fills a blank with a date from somewhere else.
What we will not pretend
- No public expiry does not mean the device is uncertified. Class I devices, legacy devices, and records the public API simply does not return all look empty.
- An expiry in the past, in the public row, is a date. It is not, by itself, our opinion that you must stop shipping. That decision sits with the manufacturer and the applicable transitional rules, which this site does not apply for you.
- A certificate can be withdrawn, suspended, or reissued. The fields worth comparing are the number, the expiry, and the status together. A new expiry with the same number is a different event from a new number.
UdiWatch stores those certificate fields on the device snapshot when the public search returns them. A later change is an audit-trail line. The app also lists stored expiries from 30 days in the past through 180 days ahead, so a date you have already captured does not depend on calling EUDAMED again just to sort it. If the snapshot never had a date, it will not appear on that list.
For the raw HTTP shape, the API reference shows the device route and GET /v1/expiring.
More notes
Not an official European Commission page. Public device and actor pages on this site repeat fields the register already publishes.