# theprotocol.it Jobs Scraper (`datawatcher/theprotocol-scraper`) Actor

Scrapes job offers from theprotocol.it, a Polish IT job board: salaries (also normalised per month), required and optional skills, seniority, contract types, locations and company. Same output schema as our other job portal actors.

- **URL**: https://apify.com/datawatcher/theprotocol-scraper.md
- **Developed by:** [DataWatcher](https://apify.com/datawatcher) (community)
- **Categories:** Jobs
- **Stats:** 3 total users, 2 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.40 / 1,000 job results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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

## theprotocol.it Jobs Scraper

Scrape job offers from [theprotocol.it](https://theprotocol.it), a Polish IT job board, into clean JSON, CSV or Excel: salaries (also normalised per month), required and optional skills, seniority, contract types, locations and company. No browser, no login: it reads the data theprotocol.it's own pages carry.

### 🔎 What does theprotocol.it Jobs Scraper do?

- Searches theprotocol.it by keywords, cities, categories, work type, experience level, contract type and "with salary only", or reads any listing or offer URL you paste.
- Returns one row per offer. With `extractFullDetails` on, each offer's own page is read too: full description (text and HTML), skills, benefits, address and company text.
- Runs on a schedule for daily new-job feeds, from the API, or from an AI agent.

### ⭐ Why this one

> **1️⃣ One schema across job portals.**
> All our job actors share one output schema and one input schema. Build your pipeline once: our other job actors ([NoFluffJobs](https://apify.com/datawatcher/nofluffjobs-scraper), [Just Join IT](https://apify.com/datawatcher/justjoin-scraper), [RocketJobs.pl](https://apify.com/datawatcher/rocketjobs-scraper), [Bulldogjob](https://apify.com/datawatcher/bulldogjob-scraper), [Hollylist](https://apify.com/datawatcher/hollylist-scraper)) take the same input and return the same fields, so adding a portal means changing the actor name, not your code.

- **Low price, no start fee.** $0.40 per 1,000 offers. The one other theprotocol.it scraper on the Store charges $1.00 per 1,000 and has a start fee. You pay only for rows you get.
- **Salaries per month, plus the employer's own figures.** Each pay range starts with a monthly entry; a pay per hour also keeps the employer's own figures as a second entry (`isOriginal` true). Each entry has `min`, `max`, `currency`, `period`, `contractType` and `grossNet`.
- **Skills with a must-have flag.** Every skill says whether the offer requires it or lists it as optional.
- **Filters buyers ask for:** search words, locations, categories, work type, experience level, contract type and "with salary only". Or paste any theprotocol.it listing or offer URL.
- **Company data:** with details on, each row carries the employer's active offers count and its own text about itself, once per company per run.
- **Honest runs:** a run summary and a health status. A search that fails writes an unbilled diagnostic row instead of silently returning nothing.
- **Fast and cheap:** plain page requests, no browser.

### Data

This actor returns only what the site shows publicly at run time. We don't store or keep that data and are not its controller — you decide how you use it.

This is an independent tool, not affiliated with or endorsed by theprotocol.it; trademarks belong to their owners. It reads only public job pages: no login, no recruiter accounts. You are responsible for following theprotocol.it's terms and data-protection law (GDPR and others).

### 🤖 Use with AI agents (MCP)

AI assistants (Claude, ChatGPT, Cursor…) can run this actor through Apify's MCP server. Connect the server in your assistant, then ask, for example:

```text
Use the theprotocol.it Jobs Scraper to find senior Python offers in Warsaw or fully remote that show a salary. Show the 10 best-paid, with company, salary, period and link.
```

### ⚙️ Input

Every job actor of ours takes the same inputs. Example: Python offers in Warsaw, B2B or employment, remote or hybrid, mid or senior, with full details:

```json
{
  "searchQueries": ["python"],
  "locations": ["Warszawa"],
  "contractTypes": ["b2b", "employment"],
  "workType": ["remote", "hybrid"],
  "experience": ["mid", "senior"],
  "maxResults": 50,
  "extractFullDetails": true
}
```

| Field | Default | Notes |
| --- | --- | --- |
| `maxResults` | `50` | Offers in total. `0` = no limit (the run timeout still applies). theprotocol.it serves 50 offers per page |
| `startUrls` | – | theprotocol.it listing pages (`https://theprotocol.it/praca`, `https://theprotocol.it/filtry/senior;p/zdalna;rw`) or offer pages (`https://theprotocol.it/praca/<slug>,oferta,<id>`; `/szczegoly/praca/...` works too). A listing URL is read as that listing, newest first from page 1; an offer URL is always read from its own page. `searchQueries` is not applied (a warning says so). The filters below still apply: rows that do not match are dropped |
| `searchQueries` | – | Keywords, one search per line (a technology or a job title). Empty: every offer. theprotocol.it searches the whole offer text |
| `locations` | – | City names; accents and case do not matter (Krakow = Kraków = KRAKÓW). Any Polish city works; a city search also returns remote offers, as the site does. A city theprotocol.it does not know gives a warning and no search for it, never an unfiltered search. Empty: anywhere |
| `categories` | – | `backend`, `frontend`, `fullstack`, `mobile`, `devops`, `data`, `ai-ml`, `testing`, `security`, `it-admin`, `support`, `embedded`, `gamedev`, `erp`, `architecture`, `project-management`, `product`, `ux-ui`, `business-analysis` |
| `contractTypes` | – | `employment`, `b2b`, `mandate`, `specific-task`, `internship` |
| `workType` | – | `remote`, `hybrid`, `onsite` |
| `experience` | – | `intern`, `junior`, `mid`, `senior`, `expert`, `lead`, `manager`, `executive` |
| `withSalaryOnly` | `false` | Only offers that show a salary |
| `extractFullDetails` | `false` | Off: listing-level rows, cheaper and faster. On: each offer's own page (and its company, once per run) is read for the description, skills, benefits and company details. An offer URL is always read in full |
| `maxConcurrency` | `1` | Searches and detail pages processed in parallel |
| `maxRequestsPerMinute` | `60` | Request rate for the whole run |
| `proxyConfiguration` | off | Apify Proxy settings, useful when many detail pages are requested |
| `maxRequestRetries` | `2` | Retries after a failed request |

theprotocol.it lists about 4,500 offers in total, 50 per page. For a smaller slice, split it with locations, categories or filters.

### 🧭 Input modes: what you give, what you get

One actor, six ways to use it. The mode follows from what you fill in.

| Mode | You give | Rows | Offer pages read |
| --- | --- | --- | --- |
| 🟢 **1. Default search** | nothing (empty input) | Newest offers, up to `maxResults` | Only with `extractFullDetails` on |
| 🔤 **2. Keyword search** | `searchQueries` | One search per keyword | Only with `extractFullDetails` on |
| 🎛️ **3. Filtered search** | one or more filters, keywords optional | Offers matching the filters | Only with `extractFullDetails` on |
| 🔗 **4. Listing / search URL** | `startUrls` with a listing URL | That listing, as the site shows it | Only with `extractFullDetails` on |
| 📄 **5. One offer URL** | `startUrls` with an offer URL | That one offer | Always (a full row either way) |
| 🧩 **6. URLs + filters** | `startUrls` plus filters | Only rows matching the filters | Offer URLs always; listed offers only with `extractFullDetails` on |

Minimal input for each mode (real inputs from our test runs). Add `"extractFullDetails": true` to any of them for full rows.

#### 🟢 1. Default search

```json
{"maxResults": 3}
```

#### 🔤 2. Keyword search

```json
{"searchQueries": ["python"], "maxResults": 3}
```

#### 🎛️ 3. Filtered search

```json
{"searchQueries": ["python"], "locations": ["Warszawa"], "contractTypes": ["b2b", "employment"], "workType": ["remote", "hybrid"], "experience": ["senior"], "maxResults": 3}
```

#### 🔗 4. Listing / search URL

```json
{"startUrls": [{"url": "https://theprotocol.it/praca?kw=ai+devops"}], "maxResults": 3}
```

#### 📄 5. One offer URL

```json
{"startUrls": [{"url": "https://theprotocol.it/praca/senior-ai-devops-engineer-warszawa,oferta,01000000-326a-b7bb-0cf8-08df13fcc123?s=-10604388607&searchId=ce6f673a-5b8d-4044-9404-987b1b653b03"}]}
```

#### 🧩 6. URLs + filters

```json
{"startUrls": [{"url": "https://theprotocol.it/praca?kw=ai+devops"}, {"url": "https://theprotocol.it/praca/senior-ai-devops-engineer-warszawa,oferta,01000000-326a-b7bb-0cf8-08df13fcc123?s=-10604388607&searchId=ce6f673a-5b8d-4044-9404-987b1b653b03"}], "locations": ["Warszawa"], "contractTypes": ["b2b"], "workType": ["remote"], "experience": ["senior"], "withSalaryOnly": true, "maxResults": 3}
```

With details off, no offer page is read to check a filter: a row the listing alone cannot confirm is left out, and a warning in the run log says how many. Turn on `extractFullDetails` to check them.

### 📦 Output

A real row from a keyword search with details on (shortened; empty fields left out):

```json
{
  "recordType": "job",
  "source": "theprotocol",
  "url": "https://theprotocol.it/szczegoly/praca/senior-python-developer-warszawa,oferta,01000000-af85-32bc-1c9b-08df25d4aa13",
  "title": "Senior Python Developer",
  "company": {
    "name": "ASTEK Polska",
    "profileUrl": "https://theprotocol.it/praca?kw=astek+polska",
    "activeOffersCount": 51
  },
  "locations": [{"city": "Warszawa", "region": "mazowieckie", "countryCode": "PL"}],
  "workType": [{"type": "hybrid"}],
  "categories": [{"value": "backend", "original": "Backend"}],
  "experience": {"levels": [{"value": "senior", "original": "senior", "minYears": 3}]},
  "contractTypes": [{"value": "employment", "original": "umowa o pracę"}, {"value": "b2b", "original": "kontrakt B2B"}],
  "workTime": "full-time",
  "salaries": [
    {"contractType": "employment", "currency": "PLN", "grossNet": "gross", "min": 16000, "max": 18000, "period": "month", "isOriginal": true},
    {"contractType": "b2b", "currency": "PLN", "grossNet": "net", "min": 20160, "max": 25200, "period": "month", "isOriginal": false},
    {"contractType": "b2b", "currency": "PLN", "grossNet": "net", "min": 120, "max": 150, "period": "hour", "isOriginal": true}
  ],
  "skills": [
    {"name": "Python", "required": true, "source": "portal"},
    {"name": "FastAPI", "required": true, "source": "portal"},
    {"name": "Django", "required": true, "source": "portal"}
  ],
  "benefits": ["Pakiet benefitów pracowniczych"],
  "languages": {"offer": "pl"},
  "description": {"text": "…", "html": "…"},
  "dates": {"posted": "2026-10-09", "expires": "2026-11-08", "scraped": "2026-10-09T07:18:46Z"},
  "extensions": {"isQuickApply": true, "openToUkrainians": false}
}
```

Missing data is `null`, never a guess.

**Run status.** After each run, open the run's key-value store (Storage tab) to see how it went:

- **`RUN_HEALTH`**: `ok`, or `degraded` with the reason (no rows, a failed request, a warning, or a row that broke a data rule).
- **`RUN_SUMMARY`**: the run's numbers: rows, requests, retries, failed requests, warnings and billed events.

### 💰 Pricing (Pay-Per-Event)

| Event | Price | Trigger |
| --- | --- | --- |
| Result row (`job-scraped`) | $0.0004 (= $0.40 / 1,000) | Per offer returned |
| Details row (`job-details-scraped`) | +$0.0015 (= +$1.50 / 1,000) | Per offer whose own page was read (`extractFullDetails` on, or an offer URL) |

No start fee: a run costs only the rows it returns. Diagnostic rows are never billed. Example: 1,000 offers with details = $0.40 + $1.50 = $1.90.

### 🎯 Use cases

- Track new IT openings for a role or stack on a daily schedule.
- Feed a job board aggregator or a personal job-search dashboard.
- Compare pay by contract type, city and experience level, in the employers' own currencies.
- Market research: which skills and seniority levels are in demand.
- Lead lists of hiring companies.
- Run the same pipeline over several Polish job portals, since they share one schema.

### ❓ FAQ

#### How many offers can I get?

As many as `maxResults` says (`0` = no limit). theprotocol.it serves 50 offers per page and lists about 4,500 offers in total; for a smaller slice, filter by city, category or experience.

#### Why is the salary empty for some offers?

Not every employer publishes pay. Then `salaries` is an empty list, never a guess. Turn on `withSalaryOnly` to get only offers with a salary.

#### What is the monthly salary?

Each pay range starts with a monthly item (`period` "month"). If the employer gives pay per hour, we compute it: hour × 168, rounded to a whole unit. The employer's own figures follow it with `isOriginal` true.

#### Can I combine it with other portals?

Yes. All our job actors share one output schema and one input schema, so rows from different portals fit one table. See the list below.

#### Can I run it on a schedule, through the API or from an AI agent?

Yes to all three: use Apify schedules, the Apify API and clients, or the MCP server (see "Use with AI agents" above).

#### What if my search finds nothing?

You pay nothing: no rows, no charge, and `RUN_HEALTH` says `degraded` (no rows). If the search failed (the site did not answer), you also get one unbilled diagnostic row (`recordType` "diagnostic") with the search and the reason in `errorMessage`.

### 🔗 Other Polish job scrapers (same schema)

- [NoFluffJobs Jobs Scraper](https://apify.com/datawatcher/nofluffjobs-scraper)
- [Just Join IT Jobs Scraper](https://apify.com/datawatcher/justjoin-scraper)
- [Bulldogjob Jobs Scraper](https://apify.com/datawatcher/bulldogjob-scraper)
- [RocketJobs.pl Jobs Scraper](https://apify.com/datawatcher/rocketjobs-scraper)
- [Hollylist Jobs Scraper (US entertainment jobs)](https://apify.com/datawatcher/hollylist-scraper)

### 💬 Feedback

Found a missing field or a bug? Open an issue on the Issues tab.

# Changelog

This Actor's version history is a separate document: https://apify.com/datawatcher/theprotocol-scraper/changelog.md

# Actor input Schema

## `maxResults` (type: `integer`):

Maximum number of offers returned, in total. 0 = no limit (the run timeout still applies). theprotocol.it serves 50 offers per page.

## `startUrls` (type: `array`):

URLs from which the actor starts scraping, instead of a search: a listing/search URL is read as that listing, a specific offer URL is read directly. locations, categories, contractTypes, workType, experience and withSalaryOnly still apply: rows that do not match are dropped. searchQueries is not applied (a warning says so). theprotocol.it listing pages (https://theprotocol.it/praca, https://theprotocol.it/filtry/senior;p/zdalna;rw), read newest first from page 1, or offer pages (https://theprotocol.it/szczegoly/praca/...).

## `searchQueries` (type: `array`):

Keywords to search for, one search per line (a technology or a job title). Empty - every offer. theprotocol.it searches the whole offer text.

## `locations` (type: `array`):

Only offers in these cities, written as normal city names; accents and case do not matter (Krakow = Kraków = KRAKÓW). A city the portal does not know gives a warning and no search for it, never an unfiltered search. Empty - anywhere. Any Polish city works; a city search also returns the remote offers (as the site does). A city the site does not know gives a warning and no search.

## `categories` (type: `array`):

Only offers in these categories (the output's `categories[].value` values). Empty - all. theprotocol.it has no specialization for 16 of these values (such as sales, marketing, hr, finance): they are ignored (a warning says so); with only such values, no search is made.

## `contractTypes` (type: `array`):

Only offers that allow one of these contracts (the output's `contractTypes` values). Empty - all.

## `workType` (type: `array`):

Only offers with one of these work types (the output's `workType[].type` values). Empty - all. theprotocol.it has no `mobile` work type: that value is ignored (a warning says so); with only that value, no search is made.

## `experience` (type: `array`):

Only offers for these experience levels (the output's `experience.levels[].value` values). Empty - all. theprotocol.it has a filter for every level, `expert` included (its own search, not grouped with `senior`); `junior` also covers its assistant level and `manager` also its head level.

## `withSalaryOnly` (type: `boolean`):

Only offers that show a salary (the output's `salaries` is not empty). Off - all offers. Sent to the site as its salary filter (a minimum of 1); core also drops any row without a salary.

## `includePremiumOffers` (type: `boolean`):

Some sites mark offers as members-only (premium). On - they are returned as metadata-only rows (title, company, locations, link; the text stays locked, the actor never logs in). Off - they are skipped and never billed, an offer start URL of a premium offer too. Sites without premium offers ignore this input.

## `extractFullDetails` (type: `boolean`):

Fetch each offer's own page (and its company once per run) and return the full data: the description, skills, benefits, languages, company details. Off - listing-level data only, cheaper and faster. An offer start URL is always read. A filter whose field the listing lacks still reads that offer's page to decide.

## `maxConcurrency` (type: `integer`):

Maximum number of searches/details processed in parallel.

## `maxRequestsPerMinute` (type: `integer`):

Maximum HTTP request rate, for the whole run.

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

Proxy settings, especially useful when many detail pages are requested. Off by default.

## `maxRequestRetries` (type: `integer`):

Number of retries after a failed HTTP request.

## Actor input object example

```json
{
  "maxResults": 50,
  "searchQueries": [
    "python"
  ],
  "withSalaryOnly": false,
  "includePremiumOffers": true,
  "extractFullDetails": false,
  "maxConcurrency": 1,
  "maxRequestsPerMinute": 60,
  "proxyConfiguration": {
    "useApifyProxy": false
  },
  "maxRequestRetries": 2
}
```

# Actor output Schema

## `results` (type: `string`):

One row per item; a search that failed completely adds one unbilled recordType "diagnostic" row.

## `runSummary` (type: `string`):

Rows, requests and budget, retries, failures, early stop, warnings, billing events, data-rule problems.

## `runHealth` (type: `string`):

{status, reason}: ok, degraded, or failed (health-check mode only).

# 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 = {
    "searchQueries": [
        "python"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("datawatcher/theprotocol-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 = { "searchQueries": ["python"] }

# Run the Actor and wait for it to finish
run = client.actor("datawatcher/theprotocol-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 '{
  "searchQueries": [
    "python"
  ]
}' |
apify call datawatcher/theprotocol-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,datawatcher/theprotocol-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/2IflhhOf1Iy00onCW/builds/qfiTEALKLzHS0dEiG/openapi.json