Booking Link Schema

all_required = alle Techniker müssen frei sein (1-to-many), any_one = ein verfügbarer reicht (1-of-many)

Only relevant when technicianMode=any_one

Per-link description, mirroring booking_service.description. Same override pattern as durationOverride/locationOverride: the booking page and the created calendar_event take this value over service.description; null (the default, and the value on every link created before this field existed) falls back to the service. Needed because the system services behind the Vorgangs-Links are tenant-wide singletons — editing one link must not rewrite the text shown by every other link on the same service.

Per-link price in cents, mirroring booking_service.price. Falls back to service.price when null. Currency and priceDisplayMode stay on the service — they are presentation, not amount.

Pre-selected company (Firma). When set, a booking made through this link stamps the created calendar_event with this partyId as linkedPartyId (takes precedence over the party derived from the customer email).

Pre-selected contact person (Kontakt, a PERSON party — usually an employee of linkedPartyId). When set, a booking made through this link adds this person as a type=party participant on the created calendar_event.

When set, a booking made through this link stamps the created calendar_event with referenceType=PROJECT / referenceId=linkedProjectId so it appears in the project Termine tab. Legacy shortcut for linkedReferenceType=PROJECT — still written by the project meeting link (project-booking.routes.ts) and honoured as a fallback; the generic pair below wins when both are set.

Vorgang ("Auftrag") the booking belongs to. A booking made through this link stamps the created calendar_event with this referenceType/referenceId pair, so the appointment shows up on the ticket/project/task/asset it was booked for. Values mirror calendar_event.referenceType.

Id of the linked Vorgang. Only meaningful together with linkedReferenceType.

Optional title for the created calendar_event (e.g. project context). Falls back to "service.name — customer" when null.

Per-link location, mirroring booking_service.location. Set when the appointment type differs per link — a ticket link is booked on site, by phone or remote depending on the case, while the shared system service can only carry one. The created calendar_event takes this value over service.location; null (the default, and the value on every link created before this field existed) keeps the previous behaviour of falling back to the service.