Jooble Jobs Search Scraper

What does Jooble Jobs Search Scraper do?

This Apify Actor extracts complete, publicly available job postings from Jooble. It uses native HTTPS and Cheerio, with optional Apify Proxy support for public HTML and an optional user-supplied first-party Jooble API key. A record is written only after its Jooble URL, identity, employer, location, and public description have been verified.

Why use Jooble Jobs Search Scraper?

• Search public Jooble country sites with bounded pages and concurrency.
• Collect complete detail-page text or official API records with explicit verification flags.
• Deduplicate jobs across multiple queries and direct URLs.
• Schedule runs, call the Actor API, export datasets, and use Apify integrations.
• Keep proxy and API-key use optional, visible, and isolated from dataset output.

How to scrape Jooble jobs

1. Open the input tab and select a mode.
2. Enter a query, country code, and optional location.
3. Start with low maxItems and maxPages values.
4. Optionally add your Jooble API key or enable Apify Proxy for public HTML.
5. Run the Actor and inspect the dataset and structured run diagnostics.
6. Download results or connect them through the Apify API and integrations.

Modes

• search: search one query, then enrich bounded result candidates from their public Jooble detail pages.
• searchMultiple: run up to five queries and deduplicate the verified records.
• single: fetch one official Jooble detail URL.
• multiple: fetch up to ten official Jooble detail URLs.
• startUrls: accept a bounded mixture of official search and detail URLs.

Jooble’s optional first-party REST API can be used by supplying apiKey. API rows are marked as API-verified and are not described as detail-page verified. No API key is included in the reproducible local input.

Input

Field	Type	Default	Description
mode	string	search	search, searchMultiple, single, multiple, or startUrls.
query	string	developer	Search phrase for search.
queries	string[]	[query]	Up to five phrases for searchMultiple.
location	string	—	City, state, or region.
country	string	us	Two-letter Jooble country code used for generated searches.
apiKey	string	—	Optional Jooble-issued API key for the official REST endpoint.
url	string	—	Official detail URL for single.
urls	object[]	—	Objects containing official detail URLs for multiple.
searchUrls	string[]	—	Official search URLs for bounded search runs.
startUrls	object[]	—	Objects containing official search or detail URLs for startUrls.
maxItems	integer	3	Maximum records per query/direct mode; 1–10.
maxPages	integer	2	Maximum search pages/API pages; 1–3.
concurrency	integer	4	Maximum concurrent detail requests; 1–5.
requestTimeoutSecs	integer	25	Per-request timeout; 5–45 seconds.

Example:

{
  "mode": "search",
  "query": "developer",
  "location": "New York",
  "country": "us",
  "maxItems": 3,
  "maxPages": 2,
  "concurrency": 4,
  "requestTimeoutSecs": 25
}

What data can Jooble Jobs Search Scraper extract?

Field	Type	Description
jobId	string	Stable Jooble job identifier
jobTitle	string	Public job title
employer	string	Hiring organization
location	string	Published location
description	string	Complete detail text or official API description
salary	string	Published salary when available
datePosted	string	Normalized posting date
publicUrl	string	Canonical Jooble URL
applicationUrl	string	Explicit application link when published

How much will it cost to scrape Jooble?

The Actor uses lightweight HTTP requests, so compute usage is normally modest. Cost depends on run duration, memory, result limits, and optional proxy traffic. Start with one page and a few jobs to estimate account-specific cost. Proxy use is disabled by default.

Output and run state

Job rows contain stable IDs, canonical/public URLs, title, employer, location, salary fields, employment type, categories/tags, dates, readable description and HTML, description sections, responsibilities/qualifications/benefits when present, explicit application links only, search provenance, verification receipts, retrieval metadata, and quality counts.

You can download the dataset in various formats such as JSON, HTML, CSV, or Excel. RUN_SUMMARY, RUN_DIAGNOSTICS, RUN_SKIPS, and RUN_HEALTH are stored in the default key-value store. Anti-bot or access-denied responses fail closed: they produce no fabricated job rows and retain the target status, redacted URL, HTTP status, and stage in diagnostics.

API keys are treated as secrets, are never written to datasets or diagnostics, and are sent only to the official Jooble API. Proxy routing applies only to public HTML requests.

Local verification

From this directory:

npm install --ignore-scripts --no-audit --no-fund
npm test
npm run lint
npx --yes apify-cli validate-schema .actor\input_schema.json
npx --yes apify-cli run --purge --input-file INPUT.json
npm run validate

The checked-in INPUT.json is the reproducible primary search input. Storage is written below storage/ and is intentionally local.

FAQ, disclaimer, and support

Why is a run BLOCKED?

Jooble may return HTTP 403 or an access-verification page. Review RUN_DIAGNOSTICS, then consider a small proxy-enabled run or the official Jooble API.

Does the Actor collect private candidate data?

No. It collects public job advertisements only and does not access authenticated candidate or employer systems.

Our Actors are ethical and do not extract private user data. Results can still contain personal data published in a job advertisement. Personal data is protected by the GDPR and other regulations. Do not process personal data without a legitimate reason; consult your lawyers if unsure. Use the API tab for programmatic access and the Issues tab for support.

Responsible use

Collect only public job information, respect Jooble’s terms and robots directives, and follow applicable privacy and data-protection requirements. Do not use the Actor for authenticated pages, paywall circumvention, or candidate personal-data harvesting.