EUDAMED Device Search & Export (EU MDR/IVDR)

Search public EUDAMED medical-device records and export normalized results to JSON, CSV, Excel, XML, or HTML through Apify.

Use it to turn a registry search into a dataset that can be scheduled, downloaded, queried through the Apify API, or connected to downstream workflows.

The European Commission launched a documented Public EUDAMED API in 2026. This actor is an Apify-native adapter, not an exclusive data source. It currently uses the public, no-auth endpoint behind the EUDAMED search interface because that payload exposes useful registry fields in a compact shape.

What this actor is good for

• Export a bounded EUDAMED search without paging through the website manually.
• Normalize UDI, manufacturer, risk-class, status, and version fields into one dataset.
• Schedule repeatable search/export jobs through Apify.
• Feed public device data into spreadsheets, databases, webhooks, or compliance tooling.

What you get per device

basicUdi, primaryDi, uuid, deviceName, tradeName, deviceModel, reference, riskClass, manufacturerName, manufacturerSrn, deviceStatusType, applicableLegislation, sterile, multiComponent, issuingAgency, containerPackageCount, version fields, and scrapedAt.

Enable Fetch full device detail to attach the richer per-device response. This adds one request per device, so keep the result cap low.

Input

Field	Meaning
searchParams	Advanced filters passed to EUDAMED's public UI-backed endpoint. Leave {} to list records without a filter.
maxItems	Stop after N devices. Use a modest cap; the registry contains millions of records.
pageSize	Records requested per page through the effective size parameter, maximum 300.
fetchDetails	Fetch the deeper record for each device. Slower: one extra request per device.
includePersonalData	Include the authorised-representative name. Off by default.
languageIso2Code	Language for EUDAMED reference labels, default en.

Example:

{
  "searchParams": {
    "deviceStatusCode": "refdata.device-model-status.on-the-market"
  },
  "maxItems": 100,
  "pageSize": 100,
  "fetchDetails": false,
  "includePersonalData": false,
  "languageIso2Code": "en"
}

Change-monitoring status

The former monitorSince mode is temporarily unavailable. EUDAMED's current device-list payload exposes lastUpdateDate as null, so using it as a date cursor would silently return unfiltered data.

Version 0.1.4 rejects legacy monitorSince input explicitly instead of presenting a false change feed. Use search/export mode while a trustworthy snapshot-diff or supported update cursor is being evaluated.

Reliability

• Schema-drift guard fails loudly if the list response changes shape or an unfiltered first page unexpectedly becomes empty.
• Dataset-contract test validates normalized live records against the actual Apify Dataset Schema, including nullable fields.
• De-duplication uses the device version UUID, with a UDI fallback; identity-less records are kept rather than folded together.
• Core-field completeness is recorded each run and warns if data quality collapses.
• The automated read-back test (npm test) checks the live public endpoint.

Data and compliance

• Public, no-auth European Commission EUDAMED data only.
• The authorised-representative name can identify a natural person, so it is redacted by default. Enable it only when you have a lawful basis.
• Attribute the source as European Commission – EUDAMED and follow the Commission's reuse terms.
• This actor is not affiliated with the European Commission. Verify important regulatory decisions against the official source.
• Requests use bounded retries and polite pacing.

FAQ

Is there now an official Public EUDAMED API?

Yes. The European Commission's 2026 Public API is open to individuals and organisations, provides GET endpoints for EUDAMED public data, and synchronizes production data on a regular cadence. This actor remains useful when you want Apify-native scheduling, dataset exports, normalized field names, and workflow integration.

How do I export to Excel or CSV?

Run a bounded search, open the run's Storage / Dataset tab, and choose the required export format. You can also retrieve the dataset through the Apify API.

Can I use monitorSince?

Not in version 0.1.4. It now fails explicitly because the source list timestamp is nullable. This prevents an apparently successful run from returning the wrong scope.

How large should a run be?

Start with 25–100 records and a narrow filter. Increase maxItems only after checking runtime and compute usage. Avoid repeated unfiltered full-registry pulls.