PATCH/api/v1/s2s/scheduling/appointment-types/{appointmentTypeId}/scheduling-policy
Update an appointment-type scheduling policy
Published Partner endpoint from the stable OpenAPI 1.9.0 contract.
Overview
Use this endpoint only with a Partner API key. Code samples use placeholders and the public sandbox URL.
- Method
- PATCH
- Endpoint
- /api/v1/s2s/scheduling/appointment-types/{appointmentTypeId}/scheduling-policy
- Authentication
- X-API-Key
Request
Parameters
- appointmentTypeIdstring (uuid)pathRequired
- appointmentTypeId path parameter.
- Example: 0d316943-1a82-4c6f-8b6d-72f0fc823c8b
- X-Correlation-IDstringheader
- Optional opaque request correlation ID for tracing API calls across systems. Billing audit paths persist only UUIDv4-shaped values and drop free-form values.
- Example: 33333333-3333-4333-8333-333333333333
Request body
Required- cancellationDeadlineHoursinteger
- Cancellation deadline applied to newly evaluated booking decisions, in hours. When omitted (undefined at the DTO boundary), the field is unchanged; null selects inheritance; 0 is an explicit value.
- Example: 0
- followUpMinutesinteger
- Follow-up time reserved after a newly evaluated booking, in minutes. When omitted (undefined at the DTO boundary), the field is unchanged; null selects inheritance; 0 is an explicit value.
- Example: 0
- minLeadMinutesinteger
- Minimum lead time required when a new booking decision is evaluated, in minutes. When omitted (undefined at the DTO boundary), the field is unchanged; null selects inheritance; 0 is an explicit value.
- Example: 0
- prepMinutesinteger
- Preparation time reserved before a newly evaluated booking, in minutes. When omitted (undefined at the DTO boundary), the field is unchanged; null selects inheritance; 0 is an explicit value.
- Example: 0
- reasonstringRequired
- Required trimmed PHI-free audit justification. The reason is never stored; the audit records only reasonProvided: true.
- Example: Terminvorlauf abgestimmt.
Contract
The versioned OpenAPI contract is the authoritative source for parameters, request bodies, and response schemas.
Version
1.9.0
Expected response
200 OK