# EUDAMED Medical Device Companies Scraper (`scrapers_lat/eudamed-medical-device-actors-scraper`) Actor

Directory of EU EUDAMED-registered medical device operators: manufacturers, authorised reps, importers and pack producers with email, phone, EU VAT, EORI, trade register number and named regulatory-compliance contacts. JSON, CSV, Excel.

- **URL**: https://apify.com/scrapers\_lat/eudamed-medical-device-actors-scraper.md
- **Developed by:** [Scrapers Lat](https://apify.com/scrapers_lat) (community)
- **Categories:** Business, Automation, Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $17.00 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

[![EUDAMED Medical Device Companies Scraper](https://scrapers.lat/banners/eudamed-medical-device-actors-scraper.png)](https://console.apify.com/actors/BlbCoXR7WzMuhTVbe/input)

## EUDAMED Medical Device Companies Scraper

Here is one real result, with every field the actor returns:

```json
{
  "name": "'Drux' rotierende Dentalinstrumente GmbH",
  "srn": "DE-MF-000005337",
  "actorType": "Manufacturer",
  "actorTypeSrnCode": "MF",
  "actorStatus": "Active",
  "country": "Germany",
  "countryCode": "DE",
  "countryType": "EU_MEMBER_STATE",
  "electronicMail": "info@drux-gmbh.de",
  "telephone": "0049 2261 29020",
  "website": "www.drux-gmbh.de",
  "street": "Hardtstraße 2",
  "city": "Gummersbach",
  "postalCode": "51643",
  "europeanVatNumber": "DE120678877",
  "eori": "DE4774175",
  "tradeRegister": "Köln HRB 65732",
  "dateOfRegistration": "2021-05-27T08:35:08.218",
  "lastUpdateDate": "2021-05-27T08:35:08.17",
  "versionNumber": 1,
  "regulatoryComplianceResponsibles": [
    {
      "fullName": "Claudia Stevenson",
      "firstName": "Claudia",
      "familyName": "Stevenson",
      "position": "Geschäftsführerin",
      "email": "c.stevenson@drux-gmbh.de",
      "phone": "0049 2261 290215",
      "city": "Gummersbach",
      "country": "Germany"
    }
  ],
  "authorisedRepresentatives": null,
  "organizationIdentificationDocuments": null,
  "competentAuthority": "DE/CA21 - Bezirksregierung Köln Dezernat 24",
  "competentAuthoritySrn": "DE-CA-038",
  "eudamedUrl": "https://ec.europa.eu/tools/eudamed/#/screen/search-eo?submitted=true&text=DE-MF-000005337",
  "observedAt": "2026-08-16T21:14:21.270Z",
  "error": null
}
```

The most complete EUDAMED company scraper available. It returns every registered medical device **economic operator** in the European database, manufacturers, authorised representatives, importers and system/procedure pack producers, with their contact email and phone, **EU VAT number, EORI number and national trade-register number**, website, full address, the **named regulatory-compliance responsible person(s)** with their own email and phone, and the competent authority that validated the registration. Filter by country and operator role, or search by company name.

**📥 [Input](https://apify.com/scrapers_lat/eudamed-medical-device-actors-scraper/input-schema) · 📤 [Output](https://apify.com/scrapers_lat/eudamed-medical-device-actors-scraper/output-schema) · 💰 [Pricing](https://apify.com/scrapers_lat/eudamed-medical-device-actors-scraper/pricing) · ▶️ [Examples](https://apify.com/scrapers_lat/eudamed-medical-device-actors-scraper/examples)**

![Apify](https://img.shields.io/badge/Platform-Apify-1CE1CE?logo=apify\&logoColor=white)
![Coverage](https://img.shields.io/badge/Coverage-European%20Union-blue)
![Output](https://img.shields.io/badge/Output-JSON%20%7C%20CSV%20%7C%20Excel-orange)
![Billing](https://img.shields.io/badge/Billing-Pay%20per%20result-brightgreen)

### Table of contents

- [What it does](#what-it-does)
- [Quickstart](#quickstart)
- [Input reference](#input-reference)
- [Output reference](#output-reference)
- [Use cases](#use-cases)
- [Run via API and CLI](#run-via-api-and-cli)
- [Billing and limits](#billing-and-limits)
- [FAQ and troubleshooting](#faq-and-troubleshooting)

### What it does

EUDAMED is the European Database on Medical Devices, the EU-wide register every manufacturer, authorised representative, importer and system/procedure pack producer must register in to place devices on the European market. This actor reads the public economic-operator register, applies the filters you pass, paginates through every matching company, and writes one normalized record per operator to the run's dataset.

Each record carries:

- **Company identity**: registered name, Single Registration Number (SRN), operator role, status, and a direct link to the operator's EUDAMED page.
- **Contact block**: email, phone, website and full postal address.
- **Verification identifiers**: EU VAT number, EORI (customs) number and national trade-register number, ideal for KYB, onboarding and matching to local company registries.
- **Named decision-maker contacts**: the regulatory-compliance responsible person(s) (the "PRP" required under EU MDR/IVDR Article 15) with their own name, position, email and phone.
- **Regulatory context**: the validating national competent authority and its SRN, plus registration and last-update timestamps.

Coverage is the entire European Union register, roughly 49,000 operators across all member states.

### Quickstart

Open the actor, paste this into the input, and press Run. It returns 5 German manufacturers with full enrichment.

```json
{
  "country": ["DE"],
  "actorType": ["manufacturer"],
  "maxRecords": 5,
  "fetchDetails": true
}
```

Leave every filter empty to pull operators across all countries and roles. All filters are optional and combine together.

### Input reference

| Field | Type | Required | Default | Description |
|---|---|---|---|---|
| `maxRecords` | integer | no | `10` | Maximum number of operators to collect. The register holds ~49,000 operators; for large pulls narrow by country and/or operator type. |
| `searchName` | string | no | (empty) | Free-text keyword matched against the operator's registered name, for example `medical`, `Medtronic`. Leave empty to pull all operators matching the filters. |
| `actorType` | array | no | (all) | One or more operator roles: `manufacturer`, `authorised-representative`, `importer`, `system-procedure-pack-producer`. |
| `country` | array | no | (all) | Two-letter ISO country codes of the operator's registered address, for example `DE`, `IT`, `FR`, `NL`. Multiple codes are each fetched. |
| `fetchDetails` | boolean | no | `true` | When on (recommended), each operator is enriched with EU VAT, EORI, trade-register number, website, structured address, the named regulatory-compliance contact person(s) and the validating competent authority. Turn off for a faster name/email/phone-only pull. |
| `proxyConfiguration` | object | no | (none) | Standard Apify proxy configuration. Not required; the source is a keyless public EU API. |

### Output reference

One dataset item per economic operator. Types: `string`, `integer`, `object[]`, or `null` when the source value is absent.

| Field | Type | Description |
|---|---|---|
| `name` | string | Registered operator (company) name. |
| `srn` | string | Single Registration Number, the EUDAMED identifier (e.g. `DE-MF-000005337`). |
| `actorType` | string | Operator role: Manufacturer, Authorised Representative, Importer or System / Procedure Pack Producer. |
| `actorTypeSrnCode` | string | Two-letter role code embedded in the SRN (`MF`, `AR`, `IM`, `PR`). |
| `actorStatus` | string | Registration status (Active / Inactive). |
| `country` | string | Country of the operator's registered address. |
| `countryCode` | string | Two-letter ISO country code. |
| `countryType` | string | `EU_MEMBER_STATE` or `NON_EU`. |
| `electronicMail` | string | Operator contact email. |
| `telephone` | string | Operator contact phone. |
| `website` | string | Operator website (enrichment). |
| `street` | string | Street and building number. |
| `city` | string | City. |
| `postalCode` | string | Postal code. |
| `europeanVatNumber` | string | EU VAT number (enrichment). |
| `eori` | string | EORI customs registration number (enrichment). |
| `tradeRegister` | string | National trade-register number and registry name (enrichment). |
| `dateOfRegistration` | string | ISO 8601 timestamp the operator was registered in EUDAMED. |
| `lastUpdateDate` | string | ISO 8601 timestamp of the operator's last update (enrichment). |
| `versionNumber` | integer | EUDAMED record version number. |
| `regulatoryComplianceResponsibles` | object\[] | Named regulatory-compliance responsible person(s): `fullName`, `firstName`, `familyName`, `position`, `email`, `phone`, `city`, `country` (enrichment). |
| `authorisedRepresentatives` | object\[] | Authorised representative(s) linked to a non-EU operator: `name`, `srn`, `email`, `country` (enrichment). |
| `organizationIdentificationDocuments` | object\[] | Additional organisation identifiers when present: `type`, `identifier` (enrichment). |
| `competentAuthority` | string | National competent authority that validated the registration (enrichment). |
| `competentAuthoritySrn` | string | SRN of that competent authority (enrichment). |
| `eudamedUrl` | string | Link to search this operator on the EUDAMED public site. |
| `observedAt` | string | ISO 8601 timestamp of when the record was collected. |
| `error` | string | `null` on success. On a failed run, a single item with a populated `error` field is written instead. |

Enrichment fields are populated when `fetchDetails` is on (the default). Fields marked `null` are genuinely absent for that operator in the source.

### Use cases

- **B2B sales and lead generation**: reach medical device manufacturers and importers by country and role, with a company email, phone and a named regulatory-compliance decision-maker.
- **KYB, onboarding and compliance**: verify a device company by SRN, EU VAT, EORI and trade-register number, and confirm its registration status and validating authority.
- **Regulatory and market intelligence**: map every manufacturer, authorised representative and importer active in a member state, and track new registrations by date.
- **Supplier and distributor discovery**: build a sourcing list of manufacturers or importers for a given country.

### Run via API and CLI

Any Apify run option works. Example with the Apify CLI:

```bash
apify call scrapers_lat/eudamed-medical-device-actors-scraper \
  --input '{"country":["IT"],"actorType":["importer"],"maxRecords":50}'
```

Or via the REST API:

```bash
curl -X POST "https://api.apify.com/v2/acts/scrapers_lat~eudamed-medical-device-actors-scraper/runs?token=YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"country":["FR"],"actorType":["manufacturer"],"maxRecords":100}'
```

### Fetch results

Results land in the run's dataset and can be exported as JSON, CSV or Excel from the Apify console or the API:

```bash
curl "https://api.apify.com/v2/datasets/DATASET_ID/items?clean=true&format=csv&token=YOUR_TOKEN"
```

### Billing and limits

- **Pay per result.** You are charged once per operator record written to the dataset. Failed runs never charge.
- Free Apify plans are capped at 10 results per run; upgrade your Apify plan for larger pulls.
- Set `maxRecords` to control run size and cost. The register holds ~49,000 operators total; use the country and operator-type filters to target the exact segment you need.

### FAQ and troubleshooting

**Which companies are covered?** Every economic operator registered in the EU's EUDAMED database: manufacturers, authorised representatives, importers and system/procedure pack producers, across all member states.

**How fresh is the data?** It is read live from the EUDAMED public register on each run, and every record includes `dateOfRegistration` and (with enrichment) `lastUpdateDate`.

**Why are some enrichment fields `null`?** Not every operator publishes a VAT number, EORI, website or a named compliance contact. Those fields are returned as `null` when the source has no value; they are only ever omitted, never guessed.

**Can I get more than the count I set?** No. `maxRecords` is a hard cap; the actor stops once it is reached.

**Do I need a proxy or an API key?** No. The source is a keyless public EU API and needs no proxy.

# Actor input Schema

## `maxRecords` (type: `integer`):

Maximum number of economic operators to collect. The registry holds ~49,000 operators in total, so for large pulls narrow by country and/or operator type.

## `searchName` (type: `string`):

Free-text keyword matched against the operator's registered name (for example "medical", "Medtronic"). Leave empty to pull all operators matching the filters below.

## `actorType` (type: `array`):

Limit to one or more economic-operator roles. Leave empty for all roles.

## `country` (type: `array`):

Two-letter ISO country codes of the operator's registered address, for example DE, IT, FR, NL. Leave empty for all countries.

## `fetchDetails` (type: `boolean`):

When enabled (recommended), each operator is enriched with its EU VAT number, EORI number, national trade-register number, website, structured address, the named regulatory-compliance responsible person(s) with their own email/phone, and the validating competent authority. Disable for a faster, name/email/phone-only pull.

## `proxyConfiguration` (type: `object`):

Optional. The source is a keyless public EU API and normally needs no proxy.

## Actor input object example

```json
{
  "maxRecords": 10,
  "actorType": [],
  "fetchDetails": true
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "maxRecords": 10,
    "searchName": ""
};

// Run the Actor and wait for it to finish
const run = await client.actor("scrapers_lat/eudamed-medical-device-actors-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "maxRecords": 10,
    "searchName": "",
}

# Run the Actor and wait for it to finish
run = client.actor("scrapers_lat/eudamed-medical-device-actors-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "maxRecords": 10,
  "searchName": ""
}' |
apify call scrapers_lat/eudamed-medical-device-actors-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,scrapers_lat/eudamed-medical-device-actors-scraper"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/BlbCoXR7WzMuhTVbe/builds/lmTyTvIp2BH4uKgDe/openapi.json