CHECK24 Vergleiche API & Open Data Integration

Contract and booking consolidation for enterprises

Companies that use CHECK24 for corporate travel, insurance, or energy comparisons need a single view of all contracts and bookings. We deliver an API that returns contracts and bookings from the customer account (product type, provider, dates, status). This maps to Open Data: structured contract and booking records that can feed ERP or contract-lifecycle tools. Auth uses the user’s CHECK24 session with explicit consent; data is refreshed on a configurable schedule.

Comparison and repricing analytics

Aggregators and advisory tools need to track comparison results over time (e.g. insurance, energy, credit). Our implementation can provide saved comparisons and result sets (prices, conditions, providers) via a dedicated endpoint. Use cases include repricing alerts, market analytics, and compliance with the EU’s Key Principles for Comparison Tools. Fields: comparison_id, category, results[], timestamp; optional filters by category and date range.

CHECK24 Bank and Open Banking aggregation

CHECK24 Bank is BaFin-licensed under PSD2 for account information (AIS) and payment initiation (PIS). The Kontomanager connects 3,000+ German banks. We can integrate with CHECK24 Bank’s API ecosystem (where you have the appropriate licensing and user consent) to expose balances and transactions for multibank dashboards, accounting sync, or payment initiation—aligned with SCA and PSD2 requirements.

B2B partner billing and order sync

Merchants and partners using CHECK24’s marketplace receive orders via FTP in openTRANS XML; billing details are available in the partner portal as CSV. We deliver automation that polls or ingests these feeds (or replicates the flows via protocol analysis) so your ERP or accounting system gets orders and billing data on a schedule. This complements the consumer-app integration and is useful for commission reconciliation and financial reporting.

Compliance and audit trail for comparisons

Regulated firms and auditors may need a record of comparison decisions (which product was chosen, when, and from which session). Our API can provide comparison history and contract metadata (with user consent) so you can demonstrate transparency and adherence to EU comparison-tool principles. Data includes session id, category, selected offer, timestamp, and optional consent flags for GDPR documentation.

Session / login (pseudo-code)

// Authenticate and obtain session token
POST /api/v1/check24/auth
Content-Type: application/json

{
  "username": "user@example.com",
  "password": "***",
  "device_id": "optional-device-fingerprint"
}

Response: {
  "session_token": "eyJ...",
  "expires_at": "2025-03-15T12:00:00Z",
  "user_id": "anon-id"
}

Contracts and bookings list (pseudo-code)

// List contracts and bookings from customer account
GET /api/v1/check24/contracts?from=2024-01-01&to=2025-12-31
Authorization: Bearer <SESSION_TOKEN>

Response: {
  "contracts": [
    {
      "id": "c-123",
      "category": "insurance",
      "provider": "Provider Name",
      "start_date": "2024-06-01",
      "status": "active"
    }
  ],
  "bookings": [ ... ]
}

Error handling and consent

All consumer-data endpoints return 401 when the session expires; 403 when the user has not consented to the requested scope. We recommend retry with exponential backoff for 5xx and storing consent timestamps for GDPR. For CHECK24 Bank PSD2 flows, SCA challenges and consent tokens are handled according to the bank’s developer documentation.

Delivery checklist

• API specification (OpenAPI / Swagger)
• Protocol and auth flow analysis report (session, token, PSD2 consent)
• Runnable source code for account, contracts, and bookings APIs (Python / Node.js / Go)
• Automated test scripts and interface documentation
• Compliance notes (GDPR, PSD2, consent and retention)

Focus integration areas

Customer account and session handling; contracts and bookings list; saved comparisons and comparison result export; CHECK24 Bank PSD2 (AIS/PIS) where applicable; partner billing and order sync; compliance and audit trails. We support single-user and enterprise multi-account scenarios with clear consent and scope documentation.

About us

We are a technical service studio specializing in app interface integration and authorized API integration. We provide efficient, compliant, and professional solutions to global clients. Our team has years of hands-on experience in mobile applications and fintech, offering one-stop services from protocol analysis, interface refactoring, Open Data integration, and third-party interface integration to automated data scripting and interface documentation.

• Marketed to overseas clients; familiar with mainstream apps’ interface standards and authorization methods
• Compliant, lawful interface implementations to meet local laws and privacy requirements
• Android and iOS support; ready-to-use API source code, documentation, and test plans
• Transparent pricing: from $300; option to deliver first and pay upon satisfaction

Contact

For inquiries, quotes, or to submit a target app name and requirements, please visit our contact page:

Contact us

Cooperation and proposal process

1. Confirm requirements: integration scenario and interface needs (e.g. login, contracts, comparisons).
2. Protocol analysis and interface design (2–5 working days, depending on complexity).
3. Development and internal validation (3–8 working days).
4. Delivery of documentation, samples, and test cases (1–2 working days).
5. First delivery often within 5–15 working days; complex or third-party approval may extend the timeline.

FAQ

What do I need to provide?

How long does delivery take?

How do you ensure compliance and privacy?