# Infostud Scraper - Serbian Job Listings · $1.5/1K (`listingworks/infostud-scraper`) Actor

Extract job postings from Poslovi Infostud (Serbia) by keyword and location: title, employer, place, salary range, posting date, category, URL.

- **URL**: https://apify.com/listingworks/infostud-scraper.md
- **Developed by:** [Yusuke Suda](https://apify.com/listingworks) (community)
- **Categories:** Jobs, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.75 / 1,000 result items

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Infostud Scraper — Serbian job listings by keyword and town

Extract job postings from Poslovi Infostud (Serbia) by keyword and location: title, employer, place, salary range, posting date, category, URL.

Poslovi Infostud (poslovi.infostud.com) is Serbia's largest job board, with around 3,600 live
postings. Over 2,000 of them are in Beograd, and there are hundreds in Novi Sad, Niš, Kragujevac and
Subotica. This Actor turns the site's search results into a clean table. Each row gives:

- the job title
- the employer
- the town or towns
- the salary, when the employer states one
- the job category
- the day the posting went online
- the link to the posting

Press Start. The prefilled input searches for `vozač` (driver) in Beograd, so the first run needs no
configuration.

### What a row looks like

```json
{
  "title": "Vozač C i CE kategorije",
  "company": "Mivex d.o.o.",
  "location": "Čačak",
  "salary_min": 100000,
  "salary_max": 100000,
  "salary_currency": "RSD",
  "salary_period": "month",
  "posted_at": "2026-09-24",
  "categories": ["transport"],
  "source_url": "https://poslovi.infostud.com/posao/vozac-c-i-ce-kategorije/mivex-doo/757876",
  "external_id": "757876"
}
```

#### The employer

`company` is the employer as the site names it: a company, an agency or an institution.

- A sole trader is registered in Serbia as "first name, surname, PR, business name". For a sole trader,
  only the business name is kept. "Boško Popović PR Autoprevoznik" becomes `Autoprevoznik`.
- Contact persons, email addresses and phone numbers are never collected.
- This Actor reads the search results only and never opens the job text.

#### The place and remote work

`location` is the place the posting names, as the site writes it:

- one town (`Beograd`)
- several towns (`Beograd, Kragujevac, Novi Sad`)
- a short form (`Novi Sad + 15 mesta`, meaning Novi Sad and 15 more places)
- a country abroad (`Nemačka`, Germany)

The site's work-mode label (`Terenski rad` for field work, `Hibrid` for hybrid) is not part of
`location`. `remote` is `true` when the posting is marked as work from home, and empty otherwise.

#### Pay and category

`salary_*` is the pay the employer states, in dinars or euros, per month, day or hour as the posting
says. The site writes net ("neto") or gross ("bruto") next to the figure. Most postings state net pay,
but the column does not record which one it is. About one posting in four states a salary. Where the
employer states nothing, the columns are empty.

`categories` is the site's own category for the posting, in Serbian, e.g. `transport`, `IT`,
`zdravstvo` (healthcare) or `trgovina, prodaja` (retail, sales).

### Posting dates

`posted_at` is the day the posting went online on the site. The site shows the day, not the time, so
the "posted after" filter compares days. A few very fresh postings carry no day yet. They are kept,
with `posted_at` empty.

The site does not list postings newest first: premium postings come first, then the rest. When a run
uses "posted after", it therefore reads the whole search and keeps the postings from that day on. It
does not stop early.

### What people use it for

- Tracking which companies in a Serbian city are hiring, week by week.
- Salary benchmarking from the pay ranges employers state, by category and town.
- Feeding a job board or a newsletter with Serbian openings in a niche, such as drivers, nurses,
  programmers or warehouse staff.
- Research on the Serbian labour market that needs structured rows rather than a page of links.

### Input

| Field | What it does |
|---|---|
| `searchTerms` | Keywords, with or without Serbian letters: `vozač`, `medicinska sestra`, `programer`. Each keyword is its own search. Leave empty for everything. |
| `location` | A town from the site's own list of 215, with or without Serbian letters: `Beograd` (or `Belgrade`), `Novi Sad`, `Niš`, `Čačak`, `Inđija`. Use `Inostranstvo` (or `Abroad`) for jobs abroad. Leave empty for all of Serbia. |
| `postedAfter` | Only postings that went online on this day or later, e.g. `2026-09-20`. |
| `sinceDays` | The same, as a rolling window: `1` keeps yesterday and today, `7` the last week. Set it once on a scheduled task and never edit the date again. |
| `maxItems` | A hard stop, so your bill is predictable. |
| `proxyConfiguration` | Off by default. Most runs do not need a proxy. |

### How much one run returns

- The site serves 30 postings per page, and the run reads page after page until the list ends or
  `maxItems` is reached.
- The site states how many postings a search holds. The run report shows that number next to the rows
  delivered.
- If you search several keywords, a posting that matches more than one is delivered only once per run.

### Pricing

$1.50 per 1,000 postings, falling to $0.75 per 1,000 on higher Apify plans, plus $0.005 each time a run
starts. Platform usage is not passed on to you.

You are charged only for rows you actually receive. If you set a maximum charge for the run, it stops
cleanly at that limit instead of going over it.

### Scope and limits

The Actor reads public listings only, from the site's search pages. The site's robots.txt allows these
for all crawlers. No API is called, and job pages are not opened. The three promoted "hot" postings at
the top of the unfiltered first page are not part of your search, and they are not delivered.

A town the site does not list fails the run at the start with a clear message. Otherwise the site would
quietly return the list for all of Serbia.

Every page is checked against what you asked for: the keyword, the town and the page number. If the
site answered something else, the run fails. It will not return rows you did not ask for and charge you
for them.

If the site changes its page structure, the run goes red. It does not return zero rows and report
success. A silent scraper is worse than a broken one, because you only find out weeks later.

A run that is blocked or cut short partway also goes red. The rows it did collect are still in the
dataset and yours to keep. Red means "this is not the complete answer", not "you lost the data". On a
schedule, a run that quietly came back short is the thing you most need to hear about.

### Same shape, other sites

This Actor shares its output shape with:

- the Posao.hr Scraper (Croatia)
- the Praca.pl Scraper (Poland)
- the BestJobs Scraper (Romania)
- the Jobs.cz Scraper (Czech Republic)
- the Jobware Scraper (Germany)
- the jobs.ch, jobup.ch and JobScout24 Scrapers (Switzerland)
- the Jobindex Scraper (Denmark)

A parser you write for one keeps working on the others, and on the countries added next.

### Support

Open an issue on this Actor with the run ID and your input. We answer within one business day.

# Actor input Schema

## `searchTerms` (type: `array`):

Keywords to search for, with or without Serbian letters, e.g. vozač, medicinska sestra, programer. Each keyword is its own search. Leave empty for all postings.

## `location` (type: `string`):

A Serbian town from the site's own town list, with or without Serbian letters (e.g. Beograd, Novi Sad, Niš, Čačak, Inđija), or Inostranstvo for jobs abroad. Leave empty for all of Serbia. A town the site does not list fails the run instead of returning an unfiltered list.

## `postedAfter` (type: `string`):

Return only postings that went online on this day or later, e.g. 2026-09-20. The site shows the day, not the time, so the day is what is compared. The list is not in date order, so the whole search is still read.

## `sinceDays` (type: `integer`):

Keep only listings posted in the last N days, counted in UTC from the day the run starts: 1 = yesterday and today. Made for a daily schedule. Ignored when Posted after is set.

## `maxItems` (type: `integer`):

Stop after this many postings. Keeps your cost predictable.

## `proxyConfiguration` (type: `object`):

Off by default. Turn on (residential, in the site's country) only if runs start getting blocked with 403/429.

## Actor input object example

```json
{
  "searchTerms": [
    "vozač"
  ],
  "location": "Beograd",
  "postedAfter": "",
  "maxItems": 100,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

## `overview` (type: `string`):

All Serbian job postings from this run: what the job is, who is hiring, where, the stated pay and the day it went online.

## `employers` (type: `string`):

The same postings ordered around who is hiring.

## `runReport` (type: `string`):

Pages read, records delivered, errors, and the verdict (ok, degraded or broken).

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "searchTerms": [
        "vozač"
    ],
    "location": "Beograd",
    "proxyConfiguration": {
        "useApifyProxy": false
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("listingworks/infostud-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "searchTerms": ["vozač"],
    "location": "Beograd",
    "proxyConfiguration": { "useApifyProxy": False },
}

# Run the Actor and wait for it to finish
run = client.actor("listingworks/infostud-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "searchTerms": [
    "vozač"
  ],
  "location": "Beograd",
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}' |
apify call listingworks/infostud-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,listingworks/infostud-scraper"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/4er0M47GL516kG7DX/builds/7kR6UBODkWVLpzFaY/openapi.json