# Posao.hr Scraper - Croatian Job Listings · $1.5/1K (`listingworks/posao-hr-scraper`) Actor

Job postings from posao.hr by occupation or county, with title, employer and place.

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

## Posao.hr Scraper — Croatian job listings by occupation and county

posao.hr is one of Croatia's large job boards, with over 7,000 live postings:
nearly 300 for drivers, over 900 in the City of Zagreb, and close to 1,000 for
work abroad. This Actor turns its lists into a clean table: the job title, the
employer, the workplace and the link to the posting.

Press Start. The prefilled input lists `vozač` (driver) postings, so the first
run needs no configuration.

### What a row looks like

```json
{
  "title": "Profesionalni vozač s iskustvom u vožnji kamiona s prikolicom (m/ž)",
  "company": "Humanus Personalservice GmbH",
  "location": "Schwendi, Njemačka",
  "remote": null,
  "source_url": "https://www.posao.hr/oglasi/profesionalni-vozac-s-iskustvom-u-voznji-kamiona-s-prikolicom-m-z/1170516/",
  "external_id": "1170516"
}
```

`company` is the employer or agency as the list shows it. Contact persons, email
addresses and phone numbers are never collected. When a sole trader's name ends
with its owner's name (", vl. …"), the owner's name is cut. This Actor reads the
lists only and never opens the job text.

`location` is the workplace the posting names: a town, several towns, a
district of a town ("Zagreb (Jankomir)"), or a place abroad ("Ulm, Njemačka").
`remote` is `true` when the posting's place is "Rad od kuće" (work from home),
and empty otherwise.

### What the lists do not have

posao.hr shows no posting date on its lists, only how many days a posting has
left. So there is no `posted_at` and no "posted after" filter. A run with one
fails at the start instead of returning rows it did not filter. The lists show
no salary figures either, only a "salary disclosed" mark, so no salary is
delivered.

### What people use it for

- Tracking which employers and agencies in a Croatian county are hiring, week
  by week.
- Watching demand for one trade (drivers, cooks, electricians, carers) across
  Croatia and for work abroad.
- Feeding a job board or a newsletter with Croatian openings in a niche.
- Research on the Croatian labour market that needs structured rows rather than
  a page of links.

### Input

| Field | What it does |
|---|---|
| `searchTerms` | Occupations, one word each, as posao.hr names them: `vozač`, `konobar`, `prodavač`, `električar`, `programer`. Each occupation is its own list. Leave empty for everything. |
| `location` | A Croatian county, in Croatian or English: `Grad Zagreb`, `Zagrebačka`, `Splitsko-dalmatinska`, `Istria`, or `Abroad` for work outside Croatia. Leave empty for the whole country. |
| `maxItems` | A hard stop, so your bill is predictable. |
| `proxyConfiguration` | Off by default. Most runs do not need a proxy. |

Give occupations **or** a county, not both: posao.hr lists by one or the other,
and a run with both fails at the start instead of guessing. A county list
includes the postings employers marked as open nationwide, as it does on the
site.

### Why occupations, not keywords

posao.hr's free-text search runs through a form whose result pages the site's
robots.txt closes to crawlers. This Actor respects that and reads only the pages
that are open: the whole list, one list per occupation, and one per county. An
occupation is one word; a phrase such as "vozač kamiona" is refused rather than
searched some other way. Occupations the site does not list on its own pages
still work (`programer` returned 12 postings); one with no postings is the
site's own "No jobs found", which returns no rows and a green run.

### How much one run returns

posao.hr serves 15 postings per page, and the run reads page after page until
the list ends or `maxItems` is reached. The last page of the City of Zagreb's
60 pages was read to its last posting. Page 1 also carries the site's premium
employers' postings above the ordinary ones: on the whole list these are nearly
400 postings that do not appear again further down, and all of them are
delivered. A posting shown twice on one page is delivered once. If you list
several occupations, a posting in more than one is delivered only once per run.

posao.hr states no count per list, so the run report shows the rows delivered
without a site total.

### 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 pages posao.hr's robots.txt
leaves open to all crawlers. No API is called, and job pages are not opened.

Every page is checked against what you asked for: the occupation or county, and
the page number. If the site answered something else, the run fails rather than
return rows you did not ask for and charge you for them.

If posao.hr 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, 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 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`):

Occupations to list, one word each, as posao.hr names them, e.g. vozač, konobar, prodavač, programer. Each occupation is its own list. posao.hr's keyword search cannot be used, so a phrase is refused. Leave empty for all postings (or for a county).

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

A Croatian county, in Croatian or English (e.g. Grad Zagreb, Splitsko-dalmatinska, Istria, Abroad). Leave empty for all of Croatia. posao.hr lists by occupation or by county, not both, so give one or the other. A county the site does not have fails the run.

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

Stop after this many postings. posao.hr serves 15 postings a page (page 1 also carries its premium employers' postings), and every page of a list 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": "",
  "maxItems": 100,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

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

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

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

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

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

```

## MCP server setup

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