Create visit confirmation
Creates a new visit confirmation.
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/visit-confirmations
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 |
customDate | string | No | Date of the visit (YYYY-MM-DD) |
customStart | string | No | Start time of the visit (HH:MM) |
customEnd | string | No | End time of the visit (HH:MM) |
printTime | boolean | No | Print time on the confirmation |
printed | boolean | No | Confirmation has already been printed |
Response
Success (201 Created)
json
{
"data": {
"id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
"customDate": "2026-06-09",
"customStart": "09:00",
"customEnd": "09:30",
"printTime": true,
"printed": false,
"customer": {
"id": "f0e1d2c3-b4a5-6789-fedc-ba9876543210",
"firstName": "Anna",
"lastName": "Muster"
}
}
}Response fields
See Get visit confirmation for the full field description.
Beispiele
bash
curl -X POST "https://my.offisy.at/api/oauth/v2/resource/visit-confirmations" \
-H "Authorization: Bearer {access_token}" \
-H "Content-Type: application/json" \
-d '{
"customerUuid": "b2c3d4e5-f6a7-8901-bcde-f01234567890",
"customDate": "2026-04-15T10:00:00",
"customStart": "beispiel",
"customEnd": "beispiel",
"printTime": "beispiel",
"printed": "beispiel"
}'Parameter
Zuerst Token anfordern
Possible errors
| Status | Code | Description |
|---|---|---|
| 400 | validation_error | Invalid request data (e.g. customerUuid missing) |
| 401 | invalid_client | Invalid or missing access token |
| 403 | insufficient_scope | Scope medicals not present |
| 404 | not_found | Customer not found |