Search for Vacancies based on free text
Search for Vacancies. Unlike other entities, searching happens based on the job_title
text match by default, not based on Skills match.
Literal string matching is fuzzy, meaning that typo’s and misspellings should still turn up desired results. For example, searching for deceptionist
could still show receptionist
Vacancy results.
Literal search will always result in a score of 1.0
. A combination of both types is possible.
Authorizations
The access token received from the authorization server in the OAuth 2.0 flow.
Query Parameters
The maximal number of results returned.
1 < x < 100
The rank offset for returned matches, return matches starting from rank offset up to rank offset+limit.
x > 0
The minimum score of the results. Due to approximations for fast result-delivery, there might be records with a score slightly lower than the minimum.
0 < x < 1
The language of the input text. auto
will automatically detect the language used.
auto
, nl
, fr
, en
, de
The type of matching. literal
will search text-based. skills
will use the Skills extracted from the input to find the best-matching Vacancies.
literal
, skills
Body
Request structure for free text search.
Input text.
A geographic location, expressed in latitude and longitude. This can represent a home address, an office location... Each entity is limited to having a single location. To get the latitude and longitude for a given address, you can use the Google Maps Geocoding API or a predefined lookup table (for example by zip code). If location is present in matching or filters, it will act as an override for geo-distance calculations.
Response
List of search results.
Was this page helpful?