v3
latestOpenAPI 3.1.02026-07-311,0939714.5 MBCreate employment for existing employee
Activity name : <a href="https://developer.loket.nl/Activities/PostEmploymentByEmployeeId" target="_blank">PostEmploymentByEmployeeId</a><br><br>Create an additional employment for an already existing employee.<br><br>Please note that the creation of an Employment is not RESTful by design.<br><br>In Loket, when a new Employee is created it will have to be created including its underlying Employment and its accessory resources. This specific endpoint is relevant in the following scenario: there is already an Employee with at least one Employment, and one wishes to create an additional Employment for that currently existing Employee. When successfully calling this endpoint, an Employment with its accessory resources will be created.<br><br>Metadata : <br>* Possible options (metadata) for generic fields of the type \metadata" can be acquired (GET) by adding /metadata to the URL.<br>* Possible options dependent on a specific payrollAdministration can be acquired by adding /metadata/payrolladministration/{payrollAdministrationId} to the url.<br>* Possible options for payGrade can be acquired by adding metadata/payrolladministration/{payrollAdministrationId}/payscale/{payScaleKey} to the url.<br><br>A payGrade has time based values dictating the wage for a given period. These values can be acquired by performing another metadata request by adding /metadata/payrolladministration/{payrollAdministrationId}/payscale/{payScaleKey}/paygrade/{payGradeKey} to the url. This endpoint has the optional parameter "date" that may be used to specifying a measure date.<br><br>Defaults : Default values for a new object can be acquired by adding /defaults to the URL. <br><br> <br>Default values that are dependent on the selected payroll administration can be acquired by adding ../v2/providers/employers/employees/employments/defaults/payrolladministration/{payrollAdministrationId} to the URL.<br><br>NonPayrollAdministrations For nonPayrollAdministrations the equivalent metaData-endpoints are also available as described above. Also, a defaults endpoint is available for the nonPayrollAdministration. Please note that this requires ../nonpayrolladministrations/{nonPayrollAdministrationId} in the path.<br>"
Path parameters
The unique identifier of the employee
Headers
A valid Bearer token for authorizing the request.
The accept header is used to influence what type of output is returned and in most cases the version of the output
Response
OK