Loket.nl REST API Data Model
EmploymentFundByEmploymentFundId |
Details of an employment fund__Activity name :__ GetEmploymentFundByEmploymentFundIdGet the details of an employment fund
Catalog: LoketNlRest
Schema: EmploymentFunds
This is a read-only table function. The loket.nl (REST) API may not support changing the data or the Invantive SQL driver for loket.nl (REST) does not cover it. In the latter case, please use the table NativePlatformScalarRequests to upload data to the loket.nl (REST) API.
Select loket.nl (REST) API URL: /providers/employers/employees/employments/employmentfunds/{employmentFundId}
Insert loket.nl (REST) API URL: /providers/employers/employees/employments/employmentfunds/{employmentFundId}
Update loket.nl (REST) API URL: /providers/employers/employees/employments/employmentfunds/{employmentFundId}
Delete loket.nl (REST) API URL: /providers/employers/employees/employments/employmentfunds/{employmentFundId}
Field Selection Method: NotRequired
Base Path: _embedded[*]
Select loket.nl (REST) API Operation: get /providers/employers/employees/employments/employmentfunds/{employmentFundId}
Table Function Parameters
The following parameters can be used to control the behaviour of the table function EmploymentFundByEmploymentFundId. A value must be provided at all times for required parameters, but optional parameters in general do not need to have a value and the execution will default to a pre-defined behaviour. Values can be specified by position and by name. In both cases, all parameters not specified will be treated using their default values.
Value specification by position is done by listing all values from the first to the last needed value. For example with `select * from table(value1, value2, value3)` on a table with four parameters will use the default value for the fourth parameter and the specified values for the first three.
Value specification by name is done by listing all values that require a value. For example with `select * from table(name1 => value1, name3 => value3)` on the same table will use the default values for the second and fourth parameters and the specified values for the first and third.
Name |
Data Type |
Required |
Default Value |
Documentation |
|---|---|---|---|---|
employmentFundId |
guid |
☑ |
|
The unique identifier of the employment fund |
Table Function Columns
The columns of the table function EmploymentFundByEmploymentFundId are shown below. Each column has an SQL data type.
Name |
Data Type |
Label |
Required |
Documentation |
|---|---|---|---|---|
deviations_employmentContributionPercentage |
double |
|
☐ |
Deviating employment contribution percentage. This value will overrule the value of the selected `fund`. Indicates percentage wise how much the employment has to contribute to the payment of the "fund" contribution.__Note:__ Records with a `startDate` before 1-1-2014 have a different regular expression__:__ ^(\d{1,3})(\.\d{1,3})?$ (a scale of 3 instead of 4). |
deviations_totalContributionPercentage |
double |
|
☐ |
Deviating total contribution percentage. This value will overrule the value of the selected `fund`. The difference between `employmentContributionPercentage` and `totalContributionPercentage` will be paid by the employer.__Note:__ Records with a `startDate` before 1-1-2014 have a different regular expression__:__ ^(\d{1,3})(\.\d{1,3})?$ (a scale of 3 instead of 4). |
endDate |
datetime |
|
☐ |
The end date of the entity. The date is up to and including. |
fixedContribution_employmentContribution |
double |
|
☐ |
The employment contribution (in money) that the employee will pay instead of what the calculation of the `fund` indicates.__Note:__ Records with a `startDate` before 1-1-2014 have a different range, from 0.00 up to 9999.99 |
fixedContribution_totalContribution |
double |
|
☐ |
The total contribution (in money) that the employer and employee pay instead of what the calculation of the `fund` indicates.__Note:__ Records with a `startDate` before 1-1-2014 have a different range, from 0 up to 9999.99 |
fund_description |
string(255) |
|
☐ |
The description of the fund |
fund_key |
int32 |
|
☐ |
The key for the fund |
id |
guid |
|
☐ |
The unique identifier of an object (GUID/UUID) |
startDate |
datetime |
|
☐ |
The date on which this fund starts.A (linked chain)[./#section/Data/Date-chains] per fund is maintained within this resource. So multiple funds can be active at the same time but one specific fund can never be active multiple times at the same time. |
13-05-2022 15:37 Version 22.1.40-BETA+3374
