# MojPosao Scraper - Croatian Job Listings · $1.5/1K (`listingworks/moj-posao-scraper`) Actor

Extract job postings from MojPosao.hr (Croatia) by keyword and location: title, employer, place, salary range, posting date, URL.

- **URL**: https://apify.com/listingworks/moj-posao-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

## MojPosao Scraper — Croatian job listings by keyword and town

Extract job postings from MojPosao.hr (Croatia) by keyword and location: title, employer, place, salary range, posting date, URL.

MojPosao (mojposao.hr, formerly moj-posao.net) is one of Croatia's large job
boards, with about 2,000 live postings: over 1,100 in Zagreb alone. This Actor
turns its search results into a clean table: the job title, the employer, the
towns the job is in, the pay where the employer gives it, when the posting went
online, and the link to the posting.

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

### What a row looks like

```json
{
  "title": "Prodajni predstavnik – središnja Hrvatska (m/ž)",
  "company": "Evapify d.o.o.",
  "location": "Zagreb",
  "salary_min": 1250,
  "salary_max": 1850,
  "salary_currency": "EUR",
  "posted_at": "2026-09-24T11:42:21+00:00",
  "source_url": "https://mojposao.hr/posao/579e5fd1-e756-4abc-bc73-9f04935ff4c7/prodajni-predstavnik-sredisnja-hrvatska-m-z",
  "external_id": "579e5fd1-e756-4abc-bc73-9f04935ff4c7"
}
```

`company` is the employer as the posting names it. When the employer hides its
name, `company` is empty. Contact persons, email addresses and phone numbers are
never collected. This Actor reads the search results only and never opens the
job text.

`location` is the list of towns the posting names, as MojPosao writes it:
"Zagreb", "Zagreb, Zabok" or "Zagreb (Lučko)". A very long list comes cut short
with "...", as the site shows it.

### Pay

A minority of postings state pay: 5 of 100 on one page of Zagreb postings.
`salary_min` and `salary_max` are the figures the employer entered, in EUR.
When only one figure is given, the other stays empty.

MojPosao does not say whether the figures are per month, or gross or net.
`salary_period` is therefore left empty rather than guessed. The amounts seen so
far, 800 to 3,200 EUR, are the size of monthly pay.

### Posting dates

`posted_at` is the time MojPosao gives for the posting, to the second, in UTC.
A "posted after" filter compares that time with yours.

MojPosao lists paid formats first and then the newest, and offers no plain date
order. A run with a cutoff therefore reads the whole search and keeps the
postings at or after it. It takes longer than on a date-ordered site, but no
newer posting further down the list is missed.

### What people use it for

- Tracking which companies in a Croatian town are hiring, week by week.
- Feeding a job board or a newsletter with Croatian openings in a niche, such
  as drivers, retail or accounting.
- Pay benchmarking from the postings that state pay.
- Research on the Croatian labour market that needs structured rows rather than
  a page of links.

### Input

| Field | What it does |
|---|---|
| `searchTerms` | Keywords, e.g. `vozač`, `računovođa`, `konobar`. Each keyword is its own search. Leave empty for everything. |
| `location` | One Croatian town as MojPosao writes it: `Zagreb`, `Split`, `Rijeka`, `Osijek`, `Zadar`. Leave empty for the whole country. |
| `postedAfter` | Only postings from this time on, e.g. `2026-09-20T00:00:00+02:00`. |
| `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

MojPosao serves 100 postings per page, and the run reads page after page until
the search ends or `maxItems` is reached. The site states how many postings a
search holds, and 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. It reads them from the search the site's
own results page uses when you scroll for more, one page at a time. MojPosao's
robots.txt allows this for all crawlers. Job pages are not opened.

**A town MojPosao does not know fails the run.** The site ignores such a town
and answers with every posting in Croatia, without saying so. So every page of
a town search is checked: if most postings on it do not name your town, the run
stops. Give one town, spelled as the site spells it. Use a town rather than a
county: the check looks for the town's own name in each posting.

Every page is also checked against the keyword you asked for. If the site
answered something else, the run fails rather than return rows you did not ask
for and charge you for them.

If MojPosao changes its search, 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, even though the rows
it did collect are in the dataset and yours to keep. Red here 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 Jobs.at Scraper (Austria)
- the Jobware Scraper (Germany)
- the jobs.ch, jobup.ch and JobScout24 Scrapers (Switzerland)
- the Jobindex Scraper (Denmark)
- the Jobs.cz Scraper (Czech Republic)
- the Praca.pl Scraper (Poland)
- the BestJobs Scraper (Romania)

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, e.g. vozač, računovođa, konobar. Each keyword is its own search. Leave empty for all postings.

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

One Croatian town as MojPosao writes it (e.g. Zagreb, Split, Rijeka, Osijek, Zadar). Leave empty for all of Croatia. MojPosao ignores a town it does not know and answers with all of Croatia, so such a run fails instead of delivering the whole country.

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

Return only postings published from this date-time on, e.g. 2026-09-20T00:00:00+02:00. MojPosao lists paid formats first, not by date, so a run with a cutoff reads the whole search and keeps the newer postings.

## `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. MojPosao serves 100 postings a page and every page of a search can be read.

## `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": "Zagreb",
  "postedAfter": "",
  "maxItems": 100,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

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

All job postings from this run: what the job is, who is hiring, where, and the pay the posting shows.

## `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": "Zagreb",
    "proxyConfiguration": {
        "useApifyProxy": false
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("listingworks/moj-posao-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": "Zagreb",
    "proxyConfiguration": { "useApifyProxy": False },
}

# Run the Actor and wait for it to finish
run = client.actor("listingworks/moj-posao-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": "Zagreb",
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}' |
apify call listingworks/moj-posao-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,listingworks/moj-posao-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/H5Cug4r4FIkN0nLbf/builds/ShbdharMuv1Nmhi3G/openapi.json