Delete an employee-attribute
Delete an employee-attribute by ID.
A value can be deleted only when its definition also accepts creation through POST: extensions, work cycles and employment data. For a multi-valued definition, only the targeted value is deleted: the other values of the employee are kept.
Any other value returns a 405. When its definition has isValueReadOnly: false, send a PATCH with value: null instead, which removes the value: analytical axes, absence and expense profiles, time approver, remote work profile, legacy user data. Timmi cost and price are the only exception: null clears the amount but keeps the employee assigned to the project. System attributes (category: system) are read-only here: update them through their primary resource, e.g. PATCH /lucca-api/employees/{id}.
Access
Access
Authorizations
The Lucca API implements the oAuth 2 protocol with the client-credentials-flow. Refer to RFC8725.
Scopes
Create, update or delete employee-attributes.
Headers
Set the API version.
2024-11-01 "2024-11-01"10"2024-11-01"
Query Parameters
Include metadata:
embedded: the partial or complete representations of related resources (e.g. the employee the resource belongs to).links: links to related resources or actions (e.g. approving a leave-request). May benullwhen you do not have access to the resource (or action). Includes the download links of the files the resource references, underlinks.files.totalCount: only applicable on collections (i.e. lists of resources), gives the total number of items across all pages.
Read more about expanding responses.
embedded, links, totalCount Response
No Content