Create illness notification
Creates a new illness notification.
Note: This endpoint requires a user-scoped OAuth token. A pure
client_credentialstoken without user context will be rejected. The issuing user is automatically derived from the token and cannot be set manually.
Request
POST /api/oauth/v2/resource/illness-notifications
Header
| Header | Value |
|---|---|
Authorization | Bearer {access_token} |
Content-Type | application/json |
Body parameters
| Field | Type | Required | Description |
|---|---|---|---|
customerUuid | string | Yes | UUID of the assigned customer |
date | string | No | Issue date (YYYY-MM-DD, default: today) |
customStartDate | string | No | Start of incapacity (YYYY-MM-DD) |
customEndDate | string | No | Expected end of incapacity (YYYY-MM-DD) |
diagnose | string | No | Diagnosis code or text |
reason | string | No | Reason for incapacity |
bedrest | boolean | No | Bed rest required |
curfew1StartTime | string | No | Curfew period 1 – start time (HH:MM) |
curfew1EndTime | string | No | Curfew period 1 – end time (HH:MM) |
curfew2StartTime | string | No | Curfew period 2 – start time (HH:MM) |
curfew2EndTime | string | No | Curfew period 2 – end time (HH:MM) |
hospitalCareStartTime | string | No | Hospital admission – start time (HH:MM) |
hospitalCareEndTime | string | No | Hospital discharge – end time (HH:MM) |
hospitalCareStartDate | string | No | Hospital admission – date (YYYY-MM-DD) |
hospitalCareEndDate | string | No | Hospital discharge – date (YYYY-MM-DD) |
occupationalDisease | integer | No | Occupational disease (key number) |
electricalAccident | boolean | No | Electrical accident |
reorderDate1 | string | No | Follow-up appointment date 1 (YYYY-MM-DD) |
reorderDate2 | string | No | Follow-up appointment date 2 (YYYY-MM-DD) |
reorderDate3 | string | No | Follow-up appointment date 3 (YYYY-MM-DD) |
reasonForBackdating | string | No | Reason for backdating |
specialIllnessReason | string | No | Reason for special illness classification |
noticeForInsurance | string | No | Notice to the insurance carrier |
printed | boolean | No | Mark as already printed |
Response
Success (201 Created)
json
{
"data": {
"id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
"date": "2026-06-09",
"customStartDate": "2026-06-09",
"customEndDate": "2026-06-16",
"diagnose": "J06.9",
"reason": null,
"bedrest": false,
"curfew1StartTime": null,
"curfew1EndTime": null,
"curfew2StartTime": null,
"curfew2EndTime": null,
"hospitalCareStartTime": null,
"hospitalCareEndTime": null,
"hospitalCareStartDate": null,
"hospitalCareEndDate": null,
"occupationalDisease": null,
"electricalAccident": false,
"reorderDate1": null,
"reorderDate2": null,
"reorderDate3": null,
"reasonForBackdating": null,
"specialIllnessReason": null,
"noticeForInsurance": null,
"printed": false,
"customer": {
"id": "f0e1d2c3-b4a5-6789-fedc-ba9876543210",
"firstName": "Anna",
"lastName": "Muster"
}
}
}Response fields
See Get illness notification for the full field description.
Beispiele
bash
curl -X POST "https://my.offisy.at/api/oauth/v2/resource/illness-notifications" \
-H "Authorization: Bearer {access_token}" \
-H "Content-Type: application/json" \
-d '{
"customerUuid": "b2c3d4e5-f6a7-8901-bcde-f01234567890",
"date": "2026-04-15T10:00:00",
"customStartDate": "2026-04-15T10:00:00",
"customEndDate": "2026-04-15T10:00:00",
"diagnose": "beispiel",
"reason": "beispiel",
"bedrest": "beispiel",
"curfew1StartTime": "beispiel",
"curfew1EndTime": "beispiel",
"curfew2StartTime": "beispiel",
"curfew2EndTime": "beispiel",
"hospitalCareStartTime": "beispiel",
"hospitalCareEndTime": "beispiel",
"hospitalCareStartDate": "2026-04-15T10:00:00",
"hospitalCareEndDate": "2026-04-15T10:00:00",
"occupationalDisease": "1",
"electricalAccident": "b2c3d4e5-f6a7-8901-bcde-f01234567890",
"reorderDate1": "2026-04-15T10:00:00",
"reorderDate2": "2026-04-15T10:00:00",
"reorderDate3": "2026-04-15T10:00:00",
"reasonForBackdating": "beispiel",
"specialIllnessReason": "beispiel",
"noticeForInsurance": "beispiel",
"printed": "beispiel"
}'Parameter
Zuerst Token anfordern
Possible errors
| Status | Code | Description |
|---|---|---|
| 400 | invalid_request | No user-scoped token provided |
| 400 | validation_error | customerUuid missing or invalid |
| 401 | invalid_client | Invalid or missing access token |
| 403 | insufficient_scope | Scope medicals not present |
| 404 | not_found | Customer not found |