According to § 28a SGB IV, the following sectors must submit an immediate report:

• Construction (Baugewerbe)
• Gastronomy & Hotels (Gaststätten- und Beherbergungsgewerbe)
• Passenger Transport (Personenbeförderungsgewerbe)
• Logistics & Haulage (Speditions- und Transportgewerbe)
• Showmen & Fairgrounds (Schaustellergewerbe)
• Forestry (Forstwirtschaft)
• Building Cleaning (Gebäudereinigungsgewerbe)
• Fairground Construction (Messebau)
• Meat Industry (Fleischwirtschaft)

Our API supports two data structures for employee registration:

Option A: With Insurance Number (Recommended)

Fastest method. Requires only firstName, lastName, insuranceNumber, and startDate.

Option B: Detailed Personal Info

Used when the insurance number is unknown. Requires full birth details (place, date, land) and current address.

The codebase references company number 94217673 in multiple example schemas and test cases. This number is generally designated as a test or development company number.

Empty responses are expected in staging environments under these conditions:

• No matching records exist for the query parameters.
• The check endpoint runs in test mode (probelauf: true).
• The response lacks the packages field, indicating no data found.

To ensure your submission is accepted, please adhere to these German social security (SV) validation standards:

• Insurance Number (RV-Nummer): Positions 3 to 8 must correspond to the employee's date of birth (DDMMYY).
• ZIP Codes: For German addresses, the ZIP code must be a valid 5-digit number between 01000 and 99999.
• Start Date: The startDate cannot be earlier than 01.01.2009 (when Sofortmeldung was introduced).
• Gender Codes: Only M (Male), W (Female), X (Indefinite), and D (Various) are accepted.

To request an eAU, you need the employee's insurance number and the date of incapacity.

{
  "companyNumber": "94217673",
  "healthInsuranceNumber": "67450665",
  "incapacityDate": "2024-03-01",
  "employee": {
    "firstName": "John",
    "lastName": "Snow",
    "insuranceNumber": "68090993D500"
  }
}

The API response for employers never contains:

• ICD-10 diagnosis codes or symptoms.
• Medical history or doctor's notes.
• Accident details (unless relevant for insurance).

You only receive the start date, expected end date, and status (First or Subsequent certificate).

The electronic process does not cover all scenarios yet. Paper is still used for:

• Private patients (they must submit certificates manually).
• Certificates issued by doctors abroad.
• Illness of a child (Kinderkrankengeld).
• Prohibition of employment (e.g., maternity protection).
• Minijobs in private households.

When requesting an eAU, you must specify the employee's insurance type. We support the following three categories:

• Gesetzlich krankenversichert (pflichtversichert, freiwillig oder familienversichert)
• Privat krankenversichert und NICHT berufsständisch versorgt
• Privat krankenversichert und berufsständisch versorgt

Retrieving an eAU involves strict timing and data requirements:

• The "Wait One Day" Rule: You can only retrieve an eAU at least one day after the start of the employee's incapacity.
• Incapacity Date: The incapacityDate must be in the past or today. Future dates will be rejected.
• Insurance Number vs. Birth Details: If the insuranceNumber is provided, you must not include birthName or birthPlace.
• Mandatory Birth Name: If the insuranceNumber is unknown, you must provide their birthName, birthPlace, and birthDate for identification.
• Company Details: Ensure the contactPerson name and telephone number are provided as they are mandatory for health insurance inquiries.

Standardized person group keys (Personengruppenschlüssel) according to German social insurance law.

Standardized country codes used for addresses and birth places. Do not use ISO 3166-1 alpha-2.

Numerical citizenship codes (Staatsangehörigkeitsschlüssel) according to the German Federal Statistical Office.

When receiving a 403 Forbidden, the errors object often contains official German error messages from the DRV engine. Here is a guide to the most common ones:

Tokens have different lifespans based on their generation event:

• Initial Registration: 24 hours
• After Refresh: 365 days