BEUDAMED API
The BEUDAMED API provides JSON access to regulatory search workflows across EU EUDAMED and US FDA data: identifier resolution, dossiers, verification, FDA pathway analysis, and search.
Authentication
Bearer token
API access requires a bearer token created in your BEUDAMED API dashboard. Send the token in the
Authorization header.
Authorization: Bearer YOUR_API_TOKEN
Tokens are shown only once when created. Store them securely. You can revoke old tokens and create new ones from your dashboard.
MCP Server
AI connectors
The MCP endpoint exposes the same regulatory data to AI tools through a read-only Model Context Protocol
server. Add https://beudamed.com/mcp
as a remote HTTP MCP server; OAuth sign-in is handled by the client.
claude mcp add --transport http beudamed https://beudamed.com/mcp
codex mcp add beudamed --url https://beudamed.com/mcp
After adding the server, follow the OAuth prompt in your client to authorize BEUDAMED access.
Workflow Endpoints
Regulatory researchWorkflow endpoints compose existing BEUDAMED records into research-ready JSON. They are read-only and use the same bearer-token authentication and quota metering as lookup and search endpoints.
curl "https://beudamed.com/api/v1/resolve?identifier=K123456" \
-H "Authorization: Bearer YOUR_API_TOKEN"
curl "https://beudamed.com/api/v1/device_dossiers/fda_udi/07615208382464" \
-H "Authorization: Bearer YOUR_API_TOKEN"
curl "https://beudamed.com/api/v1/cross_references?record_ref=fda_udi:07615208382464&target_provider=eudamed" \
-H "Authorization: Bearer YOUR_API_TOKEN"
Cross-reference results are advisory research leads only. They include confidence and match reasons but do not claim regulatory equivalence.
Lookup FDA UDI by Primary DI
GET endpointUse this endpoint when you already have an FDA primary device identifier and need the corresponding FDA UDI record as JSON.
GET /api/v1/fda_udis/07615208382464
curl https://beudamed.com/api/v1/fda_udis/07615208382464 \
-H "Authorization: Bearer YOUR_API_TOKEN"
The response includes stable top-level fields such as
primary_di,
brand_name,
company_name,
identifiers, product codes, GMDN terms, and the original FDA source payload under
raw.
Lookup EUDAMED Device by UDI-DI
GET endpointUse this endpoint when you have an EUDAMED UDI-DI and need the matching device record. For legacy devices, the same parameter is the EUDAMED ID.
GET /api/v1/eudamed_devices/06958481466379
curl https://beudamed.com/api/v1/eudamed_devices/06958481466379 \
-H "Authorization: Bearer YOUR_API_TOKEN"
The response includes stable top-level fields such as
primary_di,
basic_udi_di,
manufacturer, regulation, classification, legacy status, and the original EUDAMED source payload under
raw.
Lookup EUDAMED Basic UDI-DI
GET endpoint
Use this endpoint when you have an EUDAMED Basic UDI-DI. For legacy devices this is the EUDAMED DI,
commonly represented with a B-
prefix. The endpoint also accepts the unprefixed legacy EUDAMED ID and resolves it to the matching
B-...
record when present.
GET /api/v1/eudamed_basic_udi_dis/B-06958481466379
curl https://beudamed.com/api/v1/eudamed_basic_udi_dis/B-06958481466379 \
-H "Authorization: Bearer YOUR_API_TOKEN"
Search
Paginated JSONUse search when users provide a producer, brand, material, model, or other free-text query. The API reuses the same search backend as the website and returns paginated JSON.
GET /api/v1/search?q=IPSInLine%20dentin&type=fda_udi&dedupe=primary_di
curl "https://beudamed.com/api/v1/search?q=IPSInLine%20dentin&type=fda_udi&dedupe=primary_di" \
-H "Authorization: Bearer YOUR_API_TOKEN"
curl "https://beudamed.com/api/v1/search?q=ceramic&provider=eudamed" \
-H "Authorization: Bearer YOUR_API_TOKEN"
fda, eudamed.fda_udi, eudamed_device, eudamed_basic_udi_di.1.10 and is capped at 50.primary_di to return unique primary DIs within the current result page.