# Bulldogjob Jobs Scraper (`datawatcher/bulldogjob-scraper`) Actor Scrapes job offers from bulldogjob.pl, a Polish IT job board, from its public pages: salaries per contract type, skills, seniority, contract types, locations and company. Same output schema as our other job portal actors. - **URL**: https://apify.com/datawatcher/bulldogjob-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 ## Bulldogjob Jobs Scraper Scrape job offers from [bulldogjob.pl](https://bulldogjob.pl), a Polish IT job board, into clean JSON, CSV or Excel: salaries per contract type, skills, seniority, contract types, locations and company. No browser, no login: it reads bulldogjob.pl's own public pages. ### 🔎 What does Bulldogjob Jobs Scraper do? - Searches bulldogjob.pl by technologies, cities, categories, experience level and "with salary only", or reads any listing or offer URL you paste. Work type and contract type are applied to the rows after they arrive. - Returns one row per offer. With `extractFullDetails` on, each offer's own page is read too: full description (text and HTML), benefits, languages and company profile. - 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), [theprotocol.it](https://apify.com/datawatcher/theprotocol-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. - **No start fee.** $0.40 per 1,000 offers. The only other bulldogjob.pl scraper on the Store charges $9.99 per 1,000 offers and a start fee. You pay only for rows you get. - **Salaries per contract.** Each entry has `min`, `max`, `currency`, `period`, `contractType` and `grossNet`, one per contract type the offer pays under. - **Hidden salaries.** When an offer hides its pay bracket, the actor asks the site's own salary check and returns the top of the bracket (`extensions.salaryMaxFromCheck`), for up to 20 such offers per run. - **Filters buyers ask for:** technologies, locations, categories, experience level and "with salary only". Or paste any bulldogjob.pl listing or offer URL. - **Company data:** with details on, the employer's bulldogjob.pl profile is read too (size, active offers, history, address, website), 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 HTTP, 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 bulldogjob.pl; trademarks belong to their owners. It reads only public job pages: no login, no recruiter accounts. You are responsible for following bulldogjob.pl'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 Bulldogjob Jobs Scraper to find senior Python offers in Warsaw 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, mid or senior, with full details: ```json { "searchQueries": ["Python"], "locations": ["Warszawa"], "experience": ["mid", "senior"], "maxResults": 50, "extractFullDetails": true } ``` | Field | Default | Notes | | --- | --- | --- | | `maxResults` | `50` | Offers in total. `0` = no limit (the run timeout still applies). bulldogjob.pl serves 50 offers per page | | `startUrls` | – | bulldogjob.pl listing pages (`https://bulldogjob.pl/companies/jobs/s/city,Warszawa/role,backend`) or offer pages (`https://bulldogjob.pl/companies/jobs/257354-...`). A listing URL is read as that listing; 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` | – | Technologies, one search per line, as bulldogjob.pl names them (Python, Java, React, SQL). The site has no free-text search: a job title word finds nothing. Empty: every offer | | `locations` | – | `Warszawa`, `Kraków`, `Wrocław`, `Gdańsk`, `Łódź`, `Poznań`, `Katowice`, `Białystok`, `Rzeszów`, `Lublin`, `Remote`. Case does not matter (Krakow = Kraków = KRAKÓW); Warsaw and Cracow work too. Any other city 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`, `ux-ui`, `business-analysis`, `hr` | | `contractTypes` | – | `employment`, `b2b` | | `workType` | – | `remote`, `hybrid`, `onsite` | | `experience` | – | `junior`, `mid`, `senior`, `lead` | | `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, benefits, languages 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 | bulldogjob.pl has no filter for contract type or work type: those two are applied to the rows after they arrive, so a narrow filter reads more pages than it returns rows. ### 🧭 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 technology | 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"], "experience": ["mid", "senior"], "maxResults": 3} ``` #### 🔗 4. Listing / search URL ```json {"startUrls": [{"url": "https://bulldogjob.pl/companies/jobs/s/role,analyst,ai"}], "maxResults": 3} ``` #### 📄 5. One offer URL ```json {"startUrls": [{"url": "https://bulldogjob.pl/companies/jobs/255099-llm-application-engineer-klient-bulldogjob"}]} ``` #### 🧩 6. URLs + filters ```json {"startUrls": [{"url": "https://bulldogjob.pl/companies/jobs/s/role,analyst,ai/experienceLevel,medium"}, {"url": "https://bulldogjob.pl/companies/jobs/255099-llm-application-engineer-klient-bulldogjob"}], "contractTypes": ["b2b"], "experience": ["mid"], "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": "bulldogjob", "url": "https://bulldogjob.pl/companies/jobs/257697-senior-software-engineer-linux-krakow-luxoft-dxc", "title": "Senior Software Engineer (Linux)", "company": { "name": "Luxoft DXC", "url": "https://career.luxoft.com/locations/poland/", "profileUrl": "https://bulldogjob.pl/companies/profiles/382-luxoft-dxc", "size": "2000", "address": "Krakowska 280, 31-476", "activeOffersCount": 75 }, "locations": [{"city": "Kraków", "region": "małopolskie", "countryCode": "PL"}], "workType": [{"type": "onsite", "remotePercent": 0, "remoteCountries": []}], "categories": [{"value": "embedded", "original": "Embedded/System Developer"}], "experience": {"levels": [{"value": "senior", "original": "senior", "minYears": 5}]}, "contractTypes": [{"value": "employment", "original": "Employment contract"}], "workTime": "full-time", "salaries": [], "skills": [ {"name": "C++", "source": "portal"}, {"name": "Python", "source": "portal"}, {"name": "Linux", "required": true, "source": "description"}, {"name": "Buildroot", "required": false, "source": "description"} ], "languages": {"offer": "en"}, "description": {"text": "…", "html": "…"}, "dates": {"posted": "2026-10-09", "expires": "2026-11-08", "scraped": "2026-10-09T07:18:41Z"}, "extensions": {"hiddenBrackets": false, "state": "published", "applyViaProfile": false, "internalApplication": true} } ``` 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 technology 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 technologies 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). bulldogjob.pl serves 50 offers per page, and the actor follows the pages until it has enough. #### 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. #### Why does a job title search find nothing? bulldogjob.pl has no free-text search. `searchQueries` are technologies as the site names them (Python, Java, React, SQL). For a role, use `categories`. #### 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 "Other Polish job scrapers" 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) - [RocketJobs.pl Jobs Scraper](https://apify.com/datawatcher/rocketjobs-scraper) - [theprotocol.it Jobs Scraper](https://apify.com/datawatcher/theprotocol-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/bulldogjob-scraper/changelog.md # Actor input Schema ## `maxResults` (type: `integer`): Maximum number of offers returned, in total. 0 = no limit (the run timeout still applies). bulldogjob.pl 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). bulldogjob.pl listing pages (https://bulldogjob.pl/companies/jobs/s/city,Warszawa/role,backend) or offer pages (https://bulldogjob.pl/companies/jobs/257354-...). ## `searchQueries` (type: `array`): Keywords to search for, one search per line (a technology or a job title). Empty - every offer. bulldogjob.pl has no free-text search: give technologies as it names them (Python, Java, React, SQL); a job title word finds nothing. ## `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. bulldogjob.pl knows only its own cities: Warszawa, Kraków, Wrocław, Gdańsk, Łódź, Poznań, Katowice, Białystok, Rzeszów, Lublin and Remote; any other city gives a warning and no search. ## `categories` (type: `array`): Only offers in these categories (the output's `categories[].value` values). Empty - all. ## `contractTypes` (type: `array`): Only offers that allow one of these contracts (the output's `contractTypes` values). Empty - all. bulldogjob.pl has no contract filter: applied to the rows after they arrive, not by the site. It shows only employment, b2b and other contracts: `mandate`, `specific-task` and `internship` are ignored (a warning says so); with only such values, no search is made. ## `workType` (type: `array`): Only offers with one of these work types (the output's `workType[].type` values). Empty - all. bulldogjob.pl cannot filter by work type: applied to the rows after they arrive, not by the site. It has no `mobile`: 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. bulldogjob.pl filters only junior, mid, senior and lead: intern, expert, manager and executive are ignored (a warning says so); with only such values, no search is made. ## `withSalaryOnly` (type: `boolean`): Only offers that show a salary (the output's `salaries` is not empty). Off - all offers. ## `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 '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = { "searchQueries": [ "Python" ] }; // Run the Actor and wait for it to finish const run = await client.actor("datawatcher/bulldogjob-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 '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "searchQueries": ["Python"] } # Run the Actor and wait for it to finish run = client.actor("datawatcher/bulldogjob-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/bulldogjob-scraper --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,datawatcher/bulldogjob-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 ` 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/CMJF5ZgyCKLxNCNv4/builds/yKLRJfIARNNQsyiyM/openapi.json