v3

latestOpenAPI 3.1.02026-07-311,0939714.5 MB
Employment template

Create an Employment template for an employer

Activity name : <a href="https://developer.loket.nl/Activities/PostEmploymentTemplateByByEmployerId" target="_blank">PostEmploymentTemplateByByEmployerId</a><br><br>Create a employment template for an employer<br><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 via ../v2/providers/employers/conceptemployees/metadata/payrolladministration/{payrollAdministrationId}.<br>* Possible options for payGrade can be acquired via ../v2/providers/employers/conceptemployees/metadata/payrolladministration/{payrollAdministrationId}/payscale/{payScaleKey}.<br>A payGrade has time based values dictating the wage for a given period. These values can be acquired by performing another metadata request to GET ../v2/providers/employers/conceptemployees/metadata/payrolladministration/{payrollAdministrationId}/payscale/{payScaleKey}/paygrade/{payGradeKey}. 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 POST URL. <br><br> <br>Default values that are dependent on the selected payroll administration can be acquired by adding /v2/providers/employers/employmenttemplates/defaults/payrolladministration/{payrollAdministrationId} to the POST URL.<br><br>NonPayrollAdministrations For nonPayrollAdministrations the equivalent MetaData-endpoints are also available as described above. Default values that are dependent on the selected non-payroll administration can be acquired via /v2/providers/employers/employmenttemplates/defaults/nonpayrolladministration/{nonPayrollAdministrationId}.<br>"

post/v2/providers/employers/{employerId}/employmenttemplates

Path parameters

employerIdstring uuid required

The unique identifier of the employer

Headers

Authorizationstring required
Example:Bearer <TOKEN>

A valid Bearer token for authorizing the request.

Acceptstring required
Example:application/json;version=2018-01-01

The accept header is used to influence what type of output is returned and in most cases the version of the output

X-ValidateOnlyboolean

If set to true only the validations will be performed no changes will be committed.

Response

Created