A pharmaceutical data API is the most efficient way to integrate structured drug information — PZN identifiers, pricing, active ingredients, and clinical data — into your own software. Whether you are building a health-tech application, an ERP module, or a clinical decision support system, accessing a reliable drug database API eliminates the need to manually maintain pharmaceutical master data. This guide covers the data landscape in Germany and Europe, licensing requirements, technical integration options, and realistic cost estimates for developers and product teams.

The digital health sector is expanding rapidly across the DACH region and the European Union. Electronic health records (EHRs), telehealth platforms, digital health applications (DiGA in Germany), pharmacy management systems, and pharmaceutical ERP solutions all require structured, machine-readable drug data to function correctly.

Typical use cases for a drug database API integration include:

• PZN barcode scanning in mobile health applications — scan a product and instantly retrieve trade name, dosage form, active ingredient, and pricing.
• Autocomplete search in clinical or pharmacy software — suggest matching products after three keystrokes.
• Master data synchronization in ERP and warehouse management systems — automatically update prices, pack sizes, and distribution channels.
• Drug interaction checks in clinical systems — detect contraindications using structured active ingredient data.
• Market surveillance for pharmaceutical manufacturers — monitor competitor pricing, new product launches, and shortage status.

The central challenge is data fragmentation. In Germany, no single public API provides comprehensive pharmaceutical data. The IFA — Informationsstelle fuer Arzneispezialitaeten assigns PZN numbers and supplies basic identification data. Avoxa (formerly ABDA) enriches this data with active ingredients, ATC codes, and clinical information. The BfArM (Federal Institute for Drugs and Medical Devices) manages marketing authorization and shortage reporting. Integrating all of these sources into a usable format requires either significant in-house effort or a specialized data service provider.

What Drug Data Is Available via API

German pharmaceutical data is structured across two primary sources. The IFA database provides identification and commercial data, while the Avoxa database (ABDA database) adds scientifically curated clinical content. The following table shows which data fields each source covers and whether they are accessible through an API integration.

The ABDA-Artikelstamm — the official master data set for all drugs authorized for sale in Germany — forms the foundation of most pharmaceutical data integrations. It covers over 50,000 German products. For international coverage, consolidated data platforms like pharmazie.com extend this to 120,000+ products across 50+ countries.

Licensing: Understanding IFA and Avoxa Raw Data Licenses

A pharmaceutical raw data license is a contractual agreement that authorizes you to download, store, process, and redistribute pharmaceutical data within your own software environment. You need a raw data license whenever drug data leaves the frontend of an external platform and enters your own system — for example, when your application stores PZN records locally, synchronizes drug master data into an ERP, or serves pharmaceutical information to your end users via your own interface.

IFA Raw Data License

The IFA raw data license is the baseline license for anyone working with German drug master data. The IFA dataset contains approximately 160 to 170 data fields per product, covering identification, commercial, and pricing information. It is well suited for use cases such as product identification, price lookups, compliance checks, and warehouse management.

What the IFA data does not include: active ingredients, strengths, ATC codes, indications, SmPC texts, patient information leaflets, or product images. The IFA delivers pure identification and trade data — no scientifically curated pharmaceutical content.

New in 2026: The IFA now offers IFA Online-Daten Premium at approximately EUR 30 per month, which provides an online interface with Excel export capability for up to 50,000 records. However, this product still does not include active ingredients or ATC codes, and it is not designed for system-to-system integration. For automated data feeds, the classical IFA raw data license remains required.

Avoxa Raw Data License

The Avoxa raw data license (formerly ABDA) provides the scientifically enriched version of German pharmaceutical data. It includes everything in the IFA dataset plus active ingredients with strengths, ATC codes, indications, full-text SmPC and PIL documents, interaction data, and product images. Behind the Avoxa database are editorial teams of pharmacists who validate and curate every entry.

The Avoxa license is essential for clinical applications, drug interaction checks, e-prescribing systems, and any use case that requires pharmacological or therapeutic data. The higher data quality comes at a significantly higher cost compared to the IFA license.

The Data Processing Layer

Both IFA and Avoxa deliver their raw data in proprietary formats — fixed-field CSV structures with format changes typically two to three times per year. Most companies do not process this raw data themselves. Instead, they work with a specialized data service provider that handles format conversion, structural updates, quality assurance, and delivery in standard formats such as JSON, XML, CSV, or SQL.

A data service provider like pharmazie.com takes the raw data from IFA and Avoxa, normalizes it, enriches it with additional sources (e.g., shortage data from BfArM, international product databases), and delivers it through a REST API or scheduled data feed. This approach eliminates the need for in-house format parsing and reduces maintenance overhead significantly.

Technical Integration Options

REST API

A REST API is the most common integration method for real-time or near-real-time access to pharmaceutical data. The typical workflow is straightforward:

• PZN lookup: Send a single PZN as a query parameter and receive the full structured product record as a JSON or XML response.
• Batch queries: Send a list of PZNs in a single request and receive bulk data in one response — useful for synchronizing large product catalogs.
• Search queries: Query by trade name, active ingredient, ATC code, or manufacturer to retrieve matching products.
• Authentication: API key-based authentication. Each customer receives a unique API key that is passed in the request header.
• Response formats: JSON (recommended for modern applications) and XML (for legacy system compatibility).

REST APIs are ideal for applications that need current data on demand — such as pharmacy software, clinical decision support, or mobile health apps. Response times are typically under 200 milliseconds for single-record lookups.

Scheduled Downloads

For applications that require a local copy of the full dataset, scheduled downloads offer a practical alternative to real-time API calls:

• Delivery method: FTP server or secure download area, with biweekly update cycles aligned to the official IFA/Avoxa publication schedule.
• Formats: CSV (tab-separated), Excel, or SQL backup files — depending on your technical environment.
• Custom filtering: Receive only the data fields and product groups you actually need. For example, only prescription drugs, only a specific ATC group, or only products from selected manufacturers.

Scheduled downloads are well suited for ERP systems, warehouse management software, and data warehouse environments where batch processing is the standard workflow.

Custom Data Exports

Some integration scenarios require highly specific datasets that do not fit standard API or download templates. Custom data exports address these needs:

• Specific product segments — for example, all cannabis-based medicines, all hospital-only products, or all products affected by current shortages.
• Delivered in your preferred format and structure, with field mapping tailored to your internal schema.
• Accessible through a dedicated customer download area with versioning and change logs.

pharmazie.com provides all three integration methods. You can explore the available options on the API and Webservices page.

Cost Structure

The total cost of a German drug data API integration depends on four components. The following table provides a realistic overview of the cost structure as of 2026.

For smaller use cases — such as occasional PZN lookups or limited exports — a frontend subscription may be sufficient without a separate raw data license. For full system integration with automated data feeds, the combination of raw data license plus data processing service is the standard approach.

Getting Started: Step by Step

Integrating pharmaceutical data into your software follows a structured process. These five steps cover the typical path from initial requirements to production deployment.

1. Define your data requirements. Determine which data fields you need (identification only, or including active ingredients and clinical data), which product segments you require (all German products, specific ATC groups, international products), and how many users or systems will access the data.
2. Obtain a raw data license. Contact IFA for basic identification and pricing data, or Avoxa for enriched clinical data. Both organizations provide quotes based on your specific use case. If you only need limited data volumes, a platform subscription with export rights may suffice.
3. Choose your data processing approach. Decide whether to process the proprietary raw data formats in-house (requires dedicated development resources and ongoing maintenance for format changes) or to work with a data service provider that delivers normalized, API-ready data.
4. Set up your integration. Configure API credentials, FTP access, or download area access. Map the incoming data fields to your internal data model. Implement authentication, error handling, and update scheduling.
5. Test with sample data and go live. Validate your data mapping against known products. Verify that price fields, PZN identifiers, and — if applicable — active ingredient data are parsed correctly. Run a parallel operation period before switching to production.

pharmazie.com supports customers through each of these steps, from initial data scope consultation to technical onboarding and ongoing data delivery.

Frequently Asked Questions

Is there a free API for German drug data?

No. There is no free, publicly accessible API that provides comprehensive German pharmaceutical data. The BfArM publishes some regulatory data (e.g., marketing authorization lists, shortage reports) in open formats, but structured master data with pricing, dosage forms, and active ingredients requires a license from IFA or Avoxa. The IFA Online-Daten Premium product (approx. EUR 30/month) offers limited online access but is not an API and does not include active ingredients or ATC codes.

Can I get real-time shortage data via API?

Yes. pharmazie.com provides daily-updated shortage data for the German market through its API, covering official BfArM shortage reports as well as distributor-level availability. The platform also identifies alternative products available in EU member states. This is particularly valuable for hospital pharmacies and pharmaceutical supply chain applications.

What data formats are supported?

The pharmazie.com API delivers data in JSON and XML format. Scheduled downloads are available as tab-separated CSV, Excel (.xlsx), or SQL backup files. Custom exports can be configured in virtually any structured format to match your internal data schema. The raw data from IFA and Avoxa is delivered in proprietary fixed-field formats, which is why most companies use a data service provider for format conversion.

How do I handle biweekly data updates in my application?

The official IFA and Avoxa raw data is published every 14 days, aligned to the 1st and 15th of each month. If you use a scheduled download, implement a batch import process that runs on these dates. If you use the REST API, you automatically receive the latest data with every query — no manual update scheduling required. For price-sensitive applications (e.g., reimbursement calculations), ensure your system reflects the update date to avoid using outdated pricing.

Can I store pharmaceutical data locally on mobile devices?

This depends on the terms of your raw data license. Most IFA and Avoxa licenses permit local storage within your application environment, but you must ensure that the data is updated according to the contractual update cycle and that access is restricted to authorized users (healthcare professionals). Offline caching for mobile apps is generally permissible, but redistribution of cached data to third parties typically requires an extended license. Consult your license agreement or contact your data provider for clarification.

What about GDPR when integrating drug data?

Pharmaceutical master data (product names, PZNs, prices, active ingredients) is not personal data under the GDPR. Integrating drug databases into your software does not trigger GDPR obligations by itself. However, if your application links drug data to patient records — for example, in an e-prescribing or medication management context — the patient data component falls under GDPR. In that case, ensure that your data processing architecture separates pharmaceutical master data from personal health data and that appropriate data processing agreements are in place.