Benefit Schema
Felder
Benefit Schema
Schema for validating benefit catalog entries (Mitarbeiterbenefits, von HR gepflegt)
name
Display name of the benefit (e.g. "JobRad", "Urban Sports Club")
description
Short description shown on the benefit card
longDescription
Full description shown in the detail dialog (Markdown allowed)
category
High-level category, drives icon/color in catalog view
MOBILITYHEALTHFOODFINANCEEDUCATIONEQUIPMENTFAMILYOTHERiconKey
Optional icon name from the shared Icons component (e.g. "Bike", "Heart", "GraduationCap")
coverImageUrl
Optional URL to a cover image displayed on the benefit card
bookingMode
INTERNAL = booked via app with HR approval; EXTERNAL_LINK = redirect to provider page only; HYBRID = both options available
INTERNALEXTERNAL_LINKHYBRIDexternalUrl
Landing page of the benefit provider (used for EXTERNAL_LINK and HYBRID modes)
internalInstructions
Instructions shown to employees when booking via INTERNAL/HYBRID mode
monthlyValue
Optional monetary value per month in EUR (for display purposes only)
eligibility
Free-form eligibility criteria (e.g. "ab 6 Monaten Betriebszugehörigkeit") for display only
availableSlots
Optional cap on the number of active bookings; null means unlimited
isActive
Whether the benefit is visible to employees in the catalog
sortOrder
Optional manual sort order for the catalog view (lower comes first)
tags
Free-form tags for filtering
Keine Felder passen zum Filter.
Standard-Endpoints
Diese Resource folgt dem generischen CRUD-Vertrag der Plattform. Lesen Sie die Konventionen für Pagination, Idempotenz, Optimistic Locking und Audit. Die wichtigsten Endpoints:
GET /api/v1/benefits— Liste, paginiert + filterbarGET /api/v1/benefits/<id>— Einzelne EntityPOST /api/v1/benefits— AnlegenPATCH /api/v1/benefits/<id>— Teil-UpdateDELETE /api/v1/benefits/<id>— Soft-DeleteGET /api/v1/benefits/<id>/timeline— Audit + Aktivitäten