A pharmaceutical data API is a programmatic interface that delivers structured drug information — PZN identifiers, pricing, active ingredients, dosage forms, and clinical data — directly into your software. In 2026, with Germany’s electronic patient record (ePA) rolling out to all 73 million statutory health insurance holders and a provider-use mandate in effect since October 2025, telehealth platforms scaling across the EU, and digital health applications (DiGA) entering routine care, the demand for reliable drug database API integration has never been higher. This guide explains how to connect your application to German drug data API sources, what licensing you need, which technical options exist, and what the process actually costs.
The healthcare software landscape in Germany and Europe is undergoing a structural shift. Regulatory mandates, interoperability standards such as HL7 FHIR — now mandated or recommended in 73% of countries with electronic health data regulations, up from 56% in 2023 — and patient expectations are pushing every health-tech product toward real-time, machine-readable drug data.
Three forces are driving this acceleration:
- ePA and E-Prescribing: Germany’s electronic patient record — available since April 2025 to all statutory-insured citizens, with an 80% adoption target by end of 2026 — requires structured medication data at every touchpoint. The system uses Medical Information Objects (MIOs) to ensure machine-readable data exchange, and applications that participate in this ecosystem need standardized drug identifiers (PZN), active ingredient data, and pricing in real time.
- Digital Health Applications (DiGA): Approved DiGA products listed in the BfArM directory increasingly incorporate drug data for medication management, adherence tracking, and interaction checks. A medicine database API for health apps is now a baseline requirement, not a differentiator.
- Supply Chain Digitization: Pharmaceutical wholesalers, hospital pharmacies, and ERP vendors need automated master data synchronization to manage procurement, pricing updates, and shortage monitoring across thousands of products.
The regulatory trajectory is clear: Germany’s Digital Health Act (DigiG) and the EMA’s SPOR data services — which are introducing a public Product Management Service (PMS) API in 2026 — both assume that structured drug data is available in real time. Any health-tech product operating in Germany without programmatic access to this data is building on an unstable foundation.
Typical use cases for a drug database API integration include:
- PZN barcode lookup: Scan a product barcode in a mobile app and instantly return the trade name, dosage form, active ingredient, pack size, and current pricing.
- Autocomplete search: Offer real-time product suggestions in clinical or pharmacy software after two to three keystrokes.
- ERP master data synchronization: Automatically update prices, pack sizes, distribution channels, and availability status in warehouse management systems.
- Drug interaction checks: Query active ingredient data to detect contraindications and interactions before prescribing or dispensing.
- Market surveillance: Monitor competitor pricing, new product launches, shortage status, and regulatory changes for pharmaceutical manufacturers.
What Drug Data Is Available via a Pharmaceutical Data API
German pharmaceutical data originates from two primary sources. The IFA database (Informationsstelle fuer Arzneispezialitaeten) provides identification and commercial data. The Avoxa database — formerly known as the ABDA database — adds scientifically curated clinical content. Understanding which fields each source covers is critical for scoping your integration correctly.
| Data Field | IFA Raw Data | Avoxa (ABDA) Enriched Data | API Access |
|---|---|---|---|
| PZN (Pharmazentralnummer) | Yes | Yes | Yes |
| Trade name / product designation | Yes | Yes | Yes |
| Dosage form | Yes | Yes | Yes |
| Manufacturer / supplier | Yes | Yes | Yes |
| Pack size and norm size (N1, N2, N3) | Yes | Yes | Yes |
| Prices (APU, AEP, AVP, fixed amount) | Yes | Yes | Yes |
| Prescription status | Yes | Yes | Yes |
| Distribution channel | Yes | Yes | Yes |
| Active ingredients with strength | No | Yes | Yes |
| ATC code | No | Yes | Yes |
| Indications | No | Yes | Yes |
| SmPC (Summary of Product Characteristics) | No | Yes | Yes |
| PIL (Patient Information Leaflet) | No | Yes | Yes |
| Interaction data | No | Yes | Yes |
| Product images | No | Yes | Yes |
| Shortage status (Germany + EU) | No | No | Yes (via BfArM + pharmazie.com) |
The ABDA-Artikelstamm — the authoritative master dataset for all drugs authorized for sale in Germany — is the foundation of most pharmaceutical data integrations. It covers over 50,000 German products with approximately 260 evaluable data fields per record. For international coverage, consolidated platforms like pharmazie.com extend this to 120,000+ products across 50+ countries, searchable through a single API endpoint.
An important distinction: pharmazie.com contains the ABDA-Artikelstamm but does not include Lauer-Taxe data. If your use case requires Lauer-Taxe-specific fields (e.g., AVWG substitution tables or combination discount calculations under Section 130e SGB V), you will need to license that data separately.
Licensing: Understanding IFA and Avoxa Raw Data Licenses
A pharmaceutical raw data license is required whenever drug data leaves the user interface of an external platform and enters your own systems. This applies to any scenario where your application stores PZN records locally, synchronizes master data into an ERP, or serves drug information to end users through your own interface.
IFA Raw Data License — Identification and Commercial Data
The IFA raw data license is the baseline license for working with German drug master data. The IFA dataset contains approximately 160 to 170 data fields per product, covering identification, commercial, and pricing information.
The IFA license is appropriate for:
- Product identification and PZN barcode lookup API implementations
- Price lookups and reimbursement calculations
- Warehouse management and logistics systems
- Compliance checks and distribution channel verification
What IFA data does not include: active ingredients, strengths, ATC codes, indications, SmPC texts, patient information leaflets, interaction data, or product images. If your application requires any of these fields, you need the Avoxa license.
New in 2026: IFA now offers IFA Online-Daten Premium at approximately EUR 30 per month, providing an online interface with Excel export capability for up to 50,000 records. However, this product does not include active ingredients or ATC codes and is not designed for system-to-system integration. For automated drug master data feed scenarios, the classical IFA raw data license remains required.
Avoxa Raw Data License — Clinically Enriched Data
The Avoxa raw data license provides the scientifically curated layer on top of IFA 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 every entry.
The Avoxa license is essential for:
- Clinical decision support systems
- Drug interaction checking engines
- E-prescribing platforms
- Medicine database API implementations that serve pharmacological or therapeutic data
The higher data quality is reflected in significantly higher licensing costs compared to IFA.
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 data in-house. Instead, they work with a specialized data service provider that handles format conversion, normalization, 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 (shortage data from BfArM, international product databases from 50+ countries), and delivers it through a drug database API REST JSON endpoint or scheduled data feed. This eliminates the need for in-house format parsing and reduces maintenance overhead by an estimated 200 to 400 development hours per year.
Technical Integration Options for German Drug Data API Access
There are three primary methods to integrate pharmaceutical data into your software. The right choice depends on your latency requirements, data volume, and technical architecture.
REST API — Real-Time Queries
A REST API is the standard integration method for real-time or near-real-time pharmaceutical data access. The typical workflow:
- PZN lookup: Send a single PZN as a query parameter and receive the full structured product record as a JSON or XML response. Response times are typically under 200 milliseconds.
- Batch queries: Submit a list of PZNs in a single request and receive bulk data in one response — ideal for synchronizing large product catalogs overnight.
- Search queries: Query by trade name, active ingredient, ATC code, or manufacturer to retrieve matching products. Supports fuzzy matching and partial string search.
- Authentication: API key-based. Each customer receives a unique API key passed in the request header.
- Response formats: JSON (recommended for modern applications) and XML (for legacy system compatibility).
The pharmazie.com REST API provides access to 25+ databases through a single endpoint — the same data scope that powers the platform’s Eisbergsuche (parallel search across all databases). This includes shortage data, international product databases, and AI-powered SmPC/PIL chatbot queries via the ChatSmPC API.
“For our pharmacy management system, switching from file-based imports to a REST API reduced our data update latency from 14 days to real time,” reports a CTO at a German health-tech company. “The reduction in support tickets related to outdated pricing was immediate.”
Scheduled Downloads via FTP — Batch Processing
For applications that require a local copy of the full dataset, scheduled downloads offer a practical alternative:
- Delivery method: FTP server or secure download area, with biweekly update cycles aligned to the official IFA/Avoxa publication schedule (1st and 15th of each month).
- Formats: Tab-separated CSV, Excel (.xlsx), or SQL backup files.
- Custom filtering: Receive only the data fields and product groups you need — for example, only prescription drugs, a specific ATC group, or 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 — Tailored Datasets
Some integration scenarios require highly specific datasets that do not fit standard API or download templates:
- Specific product segments — 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.
- Versioned with change logs for audit trail requirements.
pharmazie.com provides all three integration methods. You can explore the technical specifications on the API and Webservices page.
Cost Structure for Drug Database API Integration
The total cost of a German drug data API integration depends on four components. Transparency here is important because many developers underestimate the licensing layer and focus only on the technical integration cost.
| Cost Component | Approximate Cost (2026) | Notes |
|---|---|---|
| IFA raw data license | Varies by use case | Contact IFA directly. Pricing depends on user count, distribution scope, and application type. |
| Avoxa raw data license | Higher than IFA | Contact Avoxa directly. Includes clinical data, active ingredients, ATC codes. Editorial curation is reflected in the price. |
| Data processing service | From approx. EUR 350-450/month | Covers format conversion, normalization, QA, and delivery via API or scheduled download. Priced by data scope and update frequency. |
| Frontend subscription + API access | From EUR 175/month | Includes platform access (Eisbergsuche across 25+ databases) plus data exports up to 5,000 records per export. |
For smaller use cases — occasional PZN lookup API calls 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.
A practical cost-saving consideration: if you only need identification and pricing data (no active ingredients, no clinical data), an IFA license plus a data processing service is significantly less expensive than adding the Avoxa license. Define your minimum viable data scope before negotiating licenses.
Getting Started: Step by Step
Integrating pharmaceutical data into your software follows a structured process. These five steps cover the path from initial requirements to production deployment.
- Define your data requirements. Which data fields do you need — identification only, or including active ingredients and clinical content? Which product segments — all German products, specific ATC groups, international coverage? How many systems or users will access the data? Document these requirements before contacting any data provider.
- Obtain the appropriate 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 (under 5,000 records per export), a platform subscription with export rights may suffice.
- Choose your data processing approach. Option A: Process the proprietary raw data formats in-house (requires dedicated development resources and ongoing maintenance for two to three format changes per year). Option B: Work with a data service provider like pharmazie.com that delivers normalized, API-ready data in JSON, XML, CSV, or SQL format.
- Configure your integration. Set up API credentials, FTP access, or download area access. Map incoming data fields to your internal data model. Implement authentication, error handling, rate limiting, and update scheduling. For REST API integrations, implement exponential backoff for retry logic.
- Test, validate, and go live. Validate your data mapping against known products. Verify that price fields (APU, AEP, AVP), PZN identifiers, and — if applicable — active ingredient data are parsed correctly. Run a parallel operation period of at least two update cycles (four weeks) before switching to production.
pharmazie.com supports customers through each of these steps, from initial data scope consultation to technical onboarding. The platform has been delivering pharmaceutical data services since 1989 — over 36 years of experience with German and international drug data.
Frequently Asked Questions
Is there a free pharmaceutical data API for German drug data?
No. There is no free, publicly accessible API that provides comprehensive German pharmaceutical data. While the U.S. FDA offers openFDA with free API access to adverse event, labeling, and recall data, no equivalent exists for German or EU drug master data with pricing, dosage forms, and active ingredients — this requires a license from IFA or Avoxa. The BfArM publishes some regulatory data (marketing authorization lists, shortage reports) in open formats. The IFA Online-Daten Premium product (approx. EUR 30/month) offers limited online access with Excel export but is not an API and does not include active ingredients or ATC codes. For a fully structured, API-ready dataset, you need either a raw data license or a data service provider subscription.
Can I access pharmaceutical shortage data through the pharmazie.com API?
Yes. pharmazie.com provides daily-updated pharmaceutical shortage API data for the German market, combining official BfArM shortage reports with distributor-level availability information. The platform also identifies alternative products available in other EU member states — a feature that is particularly valuable for hospital pharmacies managing supply chain disruptions. Shortage data is accessible through the same REST API endpoint used for standard product queries.
What response formats does a drug database API typically support?
Most pharmaceutical data APIs deliver responses in JSON (recommended for modern web and mobile applications) and XML (for legacy system compatibility). Scheduled downloads are typically available as tab-separated CSV, Excel (.xlsx), or SQL backup files. The raw data from IFA and Avoxa is delivered in proprietary fixed-field formats, which is one of the primary reasons most companies use a data service provider for format conversion rather than processing raw files in-house.
How often is pharmaceutical data updated, and how do I handle update cycles?
The official IFA and Avoxa raw data is published every 14 days, aligned to the 1st and 15th of each month. If you use scheduled downloads, implement a batch import process on these dates. If you use the REST API, every query automatically returns the latest data — no manual update scheduling required. Shortage data on pharmazie.com is updated daily. For price-sensitive applications (reimbursement calculations, procurement), ensure your system records the data version date to avoid using outdated pricing.
Do I need a separate raw data license if I only use the API for occasional lookups?
Not necessarily. If your use case is limited to occasional PZN lookups, small-volume exports (under 5,000 records), or interactive platform queries, a pharmazie.com frontend subscription with API access may be sufficient. The raw data license becomes mandatory when you store pharmaceutical data locally in your own systems, redistribute it to third parties, or integrate it into products that serve end users. The boundary is defined by whether the data leaves the platform’s interface and enters your own data infrastructure. When in doubt, consult with your data provider to clarify your licensing requirements.
Ready to integrate pharmaceutical data into your software?
Our team advises on data scope, licensing models, and technical integration — backed by 36 years of experience with German and international drug data. From PZN lookup APIs to full master data feeds, we help you find the right path.
