New location, ID fields and filters

Table of contents

New location_string field and location_str=true query parameter

A new field location_string has been added to the output of the /api/jobs/ endpoint and contains a more "GeoNames-compatible" version of the original location field content of a job post.

This field is primarily used internally to increase the number of relations between jobs and their respective region/country/city objects based on the location information and thereby increasing the accuracy of queries invoking these kind of relations. The issue here was that frequently the location parser couldn't process a given location info properly, so this serves as new step in between and generates a better parsable/normalized location string through an LLM-based approach.

It is not included in the results coming from /api/jobs/ by default but has to be turned on via a new location_str=true parameter (similar to the description_string/description_str=true field/parameter pair).

New job ID query filter parameters min_id and max_id

This might be interesting for queries that demand a "segmentation-based" approach to fetching job info from the /api/jobs/ and /api/jobsexpired/ API endoints. Now you can effectively query all jobs starting or ending with a certain job ID.

These parameters require an active API key subscribed to any of the available access plans and can be applied to both, the /api/jobs/ API endpoint as well as the /api/jobsexpired/ endpoint.

Related Docs