Getting Started

What does your user need to know to try your project?

Search API for job ads - getting started

The aim of this text is to walk you through what you’re seeing in the Swagger-UI to give you a bit of orientation on what can be done with the Job Search API. If you are just looking for a way to fetch all the ads please use our bulk load API The search API is intended for user search not downloading all the job ads. We may invalidate your API Keys if you make excessive amounts of calls that don’t fit the intended purpose of this API.

A bad practice typically means searching for every job of every region every fifth minute. A good practice means making lots of varied calls initiated by real users.

Table of Contents

Short introduction

The endpoints for the ads search API are:

  • search - returning ads matching a search phrase.
  • complete - returning common words matching a search phrase. Useful for autocomplete.
  • ad - returning the ad matching an id.
  • logo - returns the logo for an ad.

Easiest way to try out the API is to go to the swagger page. But first you need a key which you need to authenticate yourself.

If you want to get all ads in a bulk, please use our Stream API.


For this API, you will need to register to get your own API key at


Below we only show the URLs. If you prefer the curl command, you type it like:

curl "{URL}" -H "accept: application/json" -H "api-key: {proper_key}"

/search?q={search text}

The search endpoint in the first section will return job ads that are currently open for applications. The API is meant for searching, we want to offer you the possibility to just build your own customized GUI on top of our free text query field “q” in /search like this …

This means you don’t need to worry about how to build an advanced logic to help the users finding the most relevant ads for, let’s say, Flen. The search engine will do this for you. If you want to narrow down the search result in other ways than the free query offers, you can use the available search filters. Some of the filters need id-keys as input for searching structured data. The id-keys can be found at /taxonomy/search these will help you get sharper hits for structured data. We will always work on improving the hits for free queries hoping you’ll have less and less use for filtering.


/complete?q={typed string}

If you want to help your end users with term suggestions you can use the typeahead function, which will return common terms found in the job ads. This should work great with an auto complete feature in your search box. If you request …

… you’ll get storkök, storhushåll, storesupport, and storage as they are the most common terms starting with “stor*” in ads.

If you request

… you’ll get sverige, stockholms län, stockholm, svenska, and script since they are the most common terms beginning with “s” for ads that contain the word “storage”


This endpoint is used for fetching specific job ads with all available meta data, by their ad ID number. The ID number can be found by doing a search query.


This endpoint returns the logo for a given ad’s id number.


If you need help finding the official names for occupations, skills, or geographic place we have temporarily built an endpoint which you will find at The real version will be launched during fall 2019. Check out for updates.


The results of your queries will be in JSON format. We won’t attempt to explain this attribute by attribute in this document. Instead we’ve decided to try to include this in the data model which you can find in our Swagger GUI.

Successful queries will have a response code of 200 and give you a result set that consists of: 1. Some meta data about your search such as number of hits and the time it took to execute the query and 2. The ads that matched your search.


Unsuccessful queries will have a response code of:

HTTP Status code Reason Explanation
400 Bad Request Something wrong in the query
401 Unauthorized You are not using a valid API key
404 Missing ad The ad you requested is not available
429 Rate limit exceeded You requested too much during too short time
500 Internal Server Error Something wrong on the server side

Use cases

To help you find your way forward, here are some example of use cases:

Searching for a particular job title

The easiest way to get the ads that contain a specific word like a job title is to use a free text query (q) with the Open-Search endpoint. This will give you ads with the specified word in either headline, ad description or place of work.

Request URL

If you want to be certain that the ad is for a “souschef” - and not just mentions a “souschef” - you can use the occupation ID in the field “occupation”. If the ad has been registered by the recruiter with the occupation field set to “souschef”, the ad will show up in this search. To do this query you use both the Jobtech-Taxonomy endpoint and the Open-Search endpoint. First of all, you need to find the occupation ID for “souschef” by text searching (q) in Jobtech Taxonomy for the term in the right category (occupation-name).

Request URL

Now you can use the conceptId (iugg_Qq9_QHH) in Open-Search to fetch the ads registered with the term “souschef” in the occupation-name field:

Request URL

This will give a smaller result set with a higher certainty of actually being for a “souschef”, however the result set will likely miss a few relevant ads since the occupation-name field isn’t always set by employers. You should find that a larger set is more useful since there are multiple sorting factors working to show the most relevant hits first. We’re also working to always improve the API in regards to unstructured data.

Note: The taxonomy endpoint is temporary. Please check for updates.

Searching only within a specific field of work

Firstly, use the Jobtech-Taxonomy endpoint to get the Id for Data/IT (occupation field). You’ll then make a free text search on the term “IT” narrowing down the search to occupation-field

Request URL

In the response body you’ll find the conceptId (apaJ_2ja_LuF)for the term Data/IT. Use this with the search endpoint to define the field in which you want to get all the open-api. So now I want to combine this with my favorite language without all those snake related jobs ruining my search.

Request URL

Note: The taxonomy endpoint is temporary. Please check for updates.

Finding jobs near you

You can filter your search on geographical terms picked up from the Taxonomy just the same way you can with occupation-titles and occupation-fields. (Concept_id doesn’t work everywhere at the time of writing but you can use the numeral id’s, they are very official and way less likely to change as skills and occupations sometimes do) If you want to search for jobs in Norway you may free text query the taxonomy for “Norge”

Request URL

And add that parameter conceptId (QJgN_Zge_BzJ) to the country field

Request URL

If I make a query which includes 2 different geographical filters the most local one will be promoted. As in this case where I’m searching for “lärare” using the municipality code for Haparanda (tfRE_hXa_eq7) and the region code for Norrbottens Län (9hXe_F4g_eTG). The jobs that are in Haparanda will be the first ones in the result set.

You can also use longitude latitude coordinates and a radius in kilometers if you want.

Request URL,17.6&position.radius=10

Note: The taxonomy endpoint is temporary. Please check for updates.

So, this is very simple using our q-field. Let’s say you want to find Unix jobs

Request URL

But you find that you get a lot of jobs expecting you to work with which you dont want. All that’s needed is to use the minus symbol and the word you want to exclude.

Request URL

Finding Swedish speaking jobs abroad

Sometimes a filter can work too broadly and then it’s easier to use a negative search to remove specific results you don’t want. In this case we will show you how to filter out all the jobs in Sweden. Rather than adding a minus Sweden in the q field “-sverige” you can use the country code and the country field in the search. So first you get the country code for “Sverige” from the taxonomy endpoint.

Request URLs to get conceptId for Sweden and Swedish

As return we get id 199 for “Sverige” and id 502 for “Svenska”.

Request URL to get jobs in Swedish outside Sweden

Note: The taxonomy endpoint is temporary. Please check for updates.

Finding jobs in the public sector

In Sweden, organizations number reflect type of organization. For instance is the first figura a two if the organization is a public organization. This could be used in you search.

Request URL to get jobs in Swedish public sector

Customize the result set

There’s a lot of reasons you might want less fields for your search result set. In this case the idea is a map-based job search that plots needles where the jobs can be found based on a user search. Everything needed is the GPS coordinates for the needle and the id, employer, and headline for the ad so more info can be fetched once the user clicks on the needle. Probably, you also like to know total number of ads. In the Swagger GUI it’s possible to use the X-fields to define which fields to include in result set. This mask will look like this

total{value}, hits{id, headline, workplace_address{coordinates}, employer{name}}

This will create an extra header displayed in the curl example in Swagger. So, this example will look like this

curl "" -H "accept: application/json" -H "api-key: <proper_key>" -H "X-Fields: total{value}, hits{id, headline, workplace_address{coordinates}, employer{name}}"

Getting all the jobs since date and time

A very common use case is COLLECT ALL THE ADS. We don’t want you to use the search API for this. It’s expensive in terms of bandwidth, CPU cycles and development time and it’s not even guaranteed you’ll get everything. Instead we’d like you to use our Stream API.

Example Page

A short lead descripton about this content page. It can be **bold** or _italic_ and can be split over multiple paragraphs.

Last modified January 5, 2017