Create medical fee service
Creates a new medical fee service.
Note: This endpoint requires a user-scoped OAuth token. A pure
client_credentialstoken without user context will be rejected.
Request
POST /api/oauth/v2/resource/fee-note-services
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 |
name | string | Yes | Name of the service |
quantity | float | No | Number of units (default: 1) |
gross | float | No | Gross amount (default: 0) |
date | string | No | Service date (YYYY-MM-DD, default: today) |
internalNumber | string | No | Internal service number |
diagnose | string | No | Diagnosis (e.g. ICD code) |
unit | string | No | Unit (e.g. "unit", "hour") |
Response
Success (201 Created)
json
{
"data": {
"id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
"name": "Blutabnahme",
"internalNumber": "02",
"description": null,
"diagnose": null,
"date": "2026-06-08",
"quantity": 1.0,
"gross": 25.00,
"net": 20.83,
"netPerUnit": 20.83,
"unit": null,
"billStatus": "open",
"customer": {
"id": "f0e1d2c3-b4a5-6789-fedc-ba9876543210",
"firstName": "Anna",
"lastName": "Muster"
},
"treatingUser": "6f1c1a2b-3c4d-5e6f-7890-abcdef123456",
"insuranceService": "3a8b1c2d-3e4f-5061-7283-94a5b6c7d8e9",
"appointment": "c4d5e6f7-a8b9-4c0d-8e1f-2a3b4c5d6e7f",
"resource": "7c2f5b81-40de-4a19-b6c3-8ea1d0742f95"
}
}Response fields
See Get medical fee service for the full field description.
Beispiele
bash
curl -X POST "https://my.offisy.at/api/oauth/v2/resource/fee-note-services" \
-H "Authorization: Bearer {access_token}" \
-H "Content-Type: application/json" \
-d '{
"customerUuid": "b2c3d4e5-f6a7-8901-bcde-f01234567890",
"name": "Muster GmbH",
"quantity": "beispiel",
"gross": "beispiel",
"date": "2026-04-15T10:00:00",
"internalNumber": "beispiel",
"diagnose": "beispiel",
"unit": "beispiel"
}'Parameter
Zuerst Token anfordern
Possible errors
| Status | Code | Description |
|---|---|---|
| 400 | validation_error | Invalid request data (e.g. customerUuid or name missing) |
| 400 | validation_error | The field date is not a real calendar date in the format YYYY-MM-DD (a timestamp, single-digit values, or an impossible date are rejected; error_description: Invalid date. Expected a date (YYYY-MM-DD).) |
| 401 | invalid_client | Invalid or missing access token |
| 403 | insufficient_scope | Scope medicals not present |
| 404 | not_found | Customer not found |