Jooble Jobs Search Scraper

What does Jooble Jobs Search Scraper do?

This Actor is intended to read public job postings from Jooble using ordinary, unauthenticated direct access to public pages. It does not require or expose credentials or proxy settings in its public input contract.

Current status: SKIPPED for live extraction and qualification. Chrome previously showed a source-authored Cloudflare security-verification page on Jooble’s ordinary public search URL. No current live dataset is qualified, and this README makes no claim that the advertised fields have been validated against a live dataset or Apify Cloud run.

Why use Jooble Jobs Search Scraper?

• Search public Jooble country sites with bounded pages and result limits.
• Collect public detail-page information when the ordinary page is accessible.
• Deduplicate jobs across multiple queries and direct URLs.
• Schedule runs, call the Actor API, export datasets, and use Apify integrations.
• Keep the declared public input limited to ordinary public Jooble URLs and search options.

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. Use only ordinary public Jooble search or detail URLs; do not supply credentials, cookies, or proxy configuration.
5. If Jooble presents an access-verification or denial page, stop. Do not retry or switch routes.
6. When ordinary public access is available, inspect the dataset and run diagnostics before using results.

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 public search and detail URLs.

The declared input contract is for ordinary public pages only. It does not offer Jooble API credentials, Apify Proxy, or a user-configurable concurrency setting.

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.
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 per query; 1–3.
requestTimeoutSecs	integer	25	Per-request timeout; 5–45 seconds.

Example:

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

The input schema and runtime reject undeclared top-level fields.

What data can Jooble Jobs Search Scraper extract?

Potential output field	Type	Description
jobId	string	Stable Jooble job identifier
jobTitle	string	Public job title
employer	string	Hiring organization
location	string	Published location
description	string	Readable public detail text and sections
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 intended public mode uses bounded ordinary HTTP page requests. Actual compute depends on run duration, memory, page/result limits, and whether detail pages are requested. No fixed cost is promised. The current source-access barrier means no live dataset has been qualified; do not start repeated runs to estimate cost while the Actor remains skipped.

Output and run state

When ordinary public access is available, the Actor emits only complete detail-verified job rows: the detail request must succeed, the listing/detail identity and canonical URL must agree, title/employer/location/readable description must be present on the detail page, and at least 21 distinct meaningful source facts must be available. The rich-fact counter excludes IDs, URL-only values, run metadata, aliases, duplicate renderings, and raw source snapshots. Existing parser facts include structured addresses, compensation, dates, employment type, tags, sectioned role text, and explicit apply metadata when Jooble publishes them. No values are invented to meet the threshold. This contract does not qualify a live dataset.

You can download the dataset in various formats such as JSON, HTML, CSV, or Excel. The runtime writes RUN_SUMMARY, RUN_DIAGNOSTICS, RUN_SKIPS, RUN_HEALTH, and REQUEST_RECEIPTS to the default key-value store. A detected source-authored access barrier is terminal: the run is marked SKIPPED, buffered job rows are discarded, and the diagnostic plus bounded request receipt metadata are retained. Ordinary transport failures are reported as DEFERRED rather than as a source block.

The platform status is separate from dataset resultStatus: status is SUCCEEDED or FAILED; the result can be COMPLETE, LIMITED, SKIPPED, DEFERRED, NO_DATA, or FAILED. A later non-block error does not discard job rows whose dataset writes already succeeded; such a run is SUCCEEDED/LIMITED. A fatal zero-row failure is FAILED/FAILED and invokes Actor.fail(). A clean zero-result run is SUCCEEDED/NO_DATA. Diagnostics and request receipts are KVS artifacts, never dataset rows, and the reported stored count increments only after Actor.pushData() resolves.

Public-access boundary and terminal skip policy

The current Actor qualification is SKIPPED because a source-authored Cloudflare security-verification page was observed on Jooble’s ordinary public search route. There is no current live dataset qualified. An access-verification page is a terminal boundary: stop requests to Jooble, do not retry, change routes, use a proxy, cookies, alternate identity, or credentials, and do not publish buffered partial job rows. Preserve the exact available source response evidence, diagnostic, and request receipt(s) for audit. Move to another Actor rather than attempting a workaround.

Runtime alignment and limitations

The runtime rejects undeclared input fields, performs ordinary direct sequential requests, and does not accept target API credentials, proxy settings, cookies, or user-configurable concurrency. REQUEST_RECEIPTS is bounded and records the URL, stage, attempt, outcome, response status when available, bytes read, SHA-256 digest, content type, truncation flag, and error code when present; it does not store response bodies. This aligns the declared input and receipt contracts but does not change the qualification status: no current live dataset is qualified because of the verification barrier.

Local verification

These checks are local and do not contact Jooble:

npm test
npm run check
npm run lint
apify validate-schema
npm run validate

Do not run the Actor against Jooble while this source-access barrier remains. For this audit, Chrome control was unavailable, so fresh source comparison is DEFERRED; the earlier visible security challenge remains the reason for the existing SKIPPED qualification. A passing local check does not qualify a live dataset or establish Cloud qualification. npm run validate is read-only and requires an existing isolated local store.

FAQ, disclaimer, and support

Why is the Actor marked SKIPPED?

The ordinary public search route showed a source-authored Cloudflare security-verification page. Do not retry, use a proxy or cookies, provide alternate credentials, or switch to another route. No current live dataset is qualified.

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

Use only information Jooble makes available through ordinary unauthenticated public access. Respect Jooble’s terms, robots directives, rate limits, and applicable law. Do not bypass a security check, use authenticated access, or harvest candidate personal data. This Actor is not affiliated with Jooble. Report bugs or feature requests in the Actor’s Issues tab with a run ID and concise summary where possible.