lte
) to €45000POST
request to
vacancies/<external_id>/matching_employees
:
required_driver_license
and driver_license
upfront (to respectively Vacancy & Employee) as well as the
custom property desired_salary
to Employees - more info on this can be found
at the Custom Properties Tutorial.
If the Employee does not have the custom property desired_salary
or
driver_license
, the Employee is not included for matching. If other or more
strict comparisons are needed for the custom_property
filter on
desired_salary
, any of the lt
, lte
, eq
, gte
, gt
or neq
operators
are also supported.
In case you want to compare custom properties that are list[text]
and text
,
you can also use the custom_property_is_in
and custom_property_contains
filters.
weights
attribute in the POST
request body, you can tune the
matching score calculation. You can configure both the contribution of the
skills-match as the (non-)desired functions for Employees. You can also increase
the match score of an entity based on the location or on a custom property.
0.1
when a
Vacancy title resembles a desired function of an Employee.
full_score_distance
of each other. No
boost is applied when the entities are further away than zero_score_distance
.
Between the full_score_distance
and zero_score_distance
, the boost value
decreases linearly.
In the example below, matching scores will be increased by:
0.1
when a Vacancy is within 10km of an Employee.0.05
when a Vacancy is within 30km of an Employee.0.0
when a Vacancy is farther away than 50km of an Employee.POST
request to
vacancies/<external_id>/matching_employees
with the following content, the
Skill Engine API will:
0.05
for the employees that have a desired
salary less than €45000.0.1
for the employees that are immediately
available (assuming the current date is 2021-04-13).0.05
for the employees that are not a
freelancer.desired_salary
,
available_from
and freelancer
set, will still be included in the final match
results, but without a boost to their match score.