🇪🇺 EU-native and sovereign. Built for German healthcare.

🇪🇺 Static IP for ifap.de

Your ifap medication database and THERAFOX interaction checks keep failing because your cloud platform rotates IPs and breaks the German healthcare firewall. Route all ifap API calls through two fixed EU IPs from an EU-native, sovereign provider.

Get Your EU Static IP See How It Works

medication_check.py

# .env

HTTPS_PROXY=https://user:pass@eu-01.outboundgateway.com:8443

import requests

r = requests.get(

"https://api.ifap.de/praxis/medikament",

headers={"Authorization": "Bearer .."}

)

The Problem

ifap connects your practice software to critical drug safety data. German healthcare networks enforce strict IP whitelisting, and your cloud platform's rotating IPs keep breaking it.

German healthcare firewalls enforce IP whitelisting

Medical practices, hospitals, and pharmacy networks in Germany operate under strict data security frameworks (GDPR, SGB V). Ifap API access is restricted to whitelisted IPs. When your cloud app's outbound IP rotates, the firewall blocks the call and doctors can't access drug data.

THERAFOX interaction checks fail mid-consultation

When a doctor prescribes medication and your app calls THERAFOX for interaction safety checks, a blocked IP means the check doesn't return. The doctor either waits or prescribes without the safety check. That's a patient safety risk.

GDPR audits require stable egress

German healthcare data falls under GDPR Article 9 (special category data) and SGB V. Auditors need a documented, stable outbound IP for every ifap API call that processes medication or patient data. Dynamic IPs make compliance reporting impossible.

Data must stay in the EU

Ifap is a German provider serving German healthcare. Your integration traffic must stay within EU jurisdiction. If your cloud platform routes through US data centres, you violate data residency requirements. You need an EU-native, sovereign proxy.

The Solution

Route all ifap API calls through two fixed EU IPs

Every call your app makes to ifap for medication data, THERAFOX interaction checks, or medication plans leaves from the same pair of EU addresses. From an EU-native, sovereign provider. Ifap is German, and so is OutboundGateway.

EU-native and sovereign. OutboundGateway is an EU company, hosted in EU data centres. Your healthcare traffic never leaves EU jurisdiction.

Two fixed EU IPs with automatic failover. German-to-EU routing. If one goes down, the other takes over.

TLS passthrough. The proxy never sees your medication data, patient identifiers, or API credentials.

Implementation

Set HTTPS_PROXY and your existing code works as-is.

Python (medication database query)

Your existing code works as-is. requests reads HTTPS_PROXY automatically.

# .env
HTTPS_PROXY=https://user:pass@eu-01.outboundgateway.com:8443
IFAP_API_TOKEN=your_token

import os
import requests

# requests honours HTTPS_PROXY automatically
r = requests.get(
    "https://api.ifap.de/praxis/medikament",
    headers={"Authorization": f"Bearer {os.environ['IFAP_API_TOKEN']}"},
    params={"pzn": "12345678"},
)

print(r.json())

Node.js (THERAFOX interaction check)

Pass the proxy explicitly with https-proxy-agent.

// .env
HTTPS_PROXY=https://user:pass@eu-01.outboundgateway.com:8443

const { HttpsProxyAgent } = require('https-proxy-agent');

const agent = new HttpsProxyAgent(process.env.HTTPS_PROXY);

// Every ifap call routes through your fixed EU IP
const res = await fetch('https://api.ifap.de/therafox/interactions', {
  headers: { 'Authorization': 'Bearer ..' },
  agent,
});

Docker / Kubernetes / env

Set it wherever your healthcare app runs.

# Docker Compose
services:
  app:
    env_file: .env

# Kubernetes: Secret
env:
  - name: HTTPS_PROXY
    valueFrom:
      secretKeyRef:
        name: outboundgateway-proxy
        key: proxy-url

Two IPs, EU-native and sovereign

Your account comes with two static IP addresses in EU data centres, owned and operated by an EU company. ifap is German, OutboundGateway is EU-based. Your healthcare traffic stays EU-to-EU, sovereign and GDPR-compliant. If one proxy node is briefly unavailable, traffic shifts to the other.

📖 Complete Documentation: For detailed examples, error handling, and other languages, see the Python SSL Proxy Guide, Node.js Guide, and all other language guides.

Why German healthcare teams choose OutboundGateway

A pair of fixed IPs

Two addresses to whitelist on German healthcare firewalls, with automatic failover.

Zero code changes

Set one env var and your existing requests or fetch calls to ifap work as-is.

EU-native and sovereign

An EU company, hosted in EU data centres. Healthcare traffic never leaves EU jurisdiction.

All ifap services

Arzneimitteldatenbank, THERAFOX, Medikationsplan. One pair covers every ifap endpoint.

Encrypted end to end

TLS passthrough means the proxy can't read your traffic. Medication data and patient IDs stay private.

Flexible plans

Starting from €19/month. Flexible plans for every scale. Cancel anytime.

Frequently asked questions

Does ifap enforce IP whitelisting?

Yes. ifap operates under German healthcare regulations and connects to practice software, hospital networks, and pharmacy systems that enforce strict IP whitelisting. When your cloud app's outbound IP rotates, those calls get blocked. OutboundGateway gives you two fixed EU IPs that never change, so the firewall whitelist always passes.

Does this work for all ifap services?

Yes. The proxy isn't endpoint-specific. Whether your app queries the Arzneimitteldatenbank (medication database), calls THERAFOX for interaction checks, or generates a Medikationsplan, all of it routes through the same fixed pair of EU IPs. Set HTTPS_PROXY once and every ifap endpoint is covered.

Is OutboundGateway really EU-native and sovereign?

Yes. OutboundGateway is an EU company, incorporated and operated within the EU. Our proxy infrastructure runs entirely in EU data centres. We are not a US company with EU servers. Your healthcare API traffic stays within EU jurisdiction, under EU law, managed by an EU company. That's what sovereign means.