Jooble Jobs Scraper avatar

Jooble Jobs Scraper

Pricing

from $2.52 / 1,000 results

Go to Apify Store
Jooble Jobs Scraper

Jooble Jobs Scraper

Jooble Jobs Scraper is a Jooble API for 65 countries that returns 41 structured job, salary, employer, application, and public contact fields without a separate Jooble API key.

Pricing

from $2.52 / 1,000 results

Rating

0.0

(0)

Developer

AgentX

AgentX

Maintained by Community

Actor stats

0

Bookmarked

36

Total users

13

Monthly active users

7 days ago

Last modified

Share

Jooble Jobs Scraper is a Jooble API that searches 65 Jooble markets and returns 41 structured job, salary, company, application, and public contact fields. It is built for recruiting research, workforce intelligence, job products, and repeatable data workflows.

Apify Users Apify Runs Price Capability API + MCP ready

  • 65 countries in the public search contract.
  • 5 public inputs with 3 required.
  • 41 normalized Dataset fields.
  • $0.00280 per Result on FREE plus a $0.01000 minimum Actor Start event.

The smallest useful test sets max_results to 1 and costs $0.01280 on FREE when one Result is published and one Actor Start event is charged.

Why Choose Jooble Jobs Scraper

Source-focused coverage. Jooble Jobs Scraper searches 65 Jooble markets while keeping the public source URL on every accepted record, so reviewers can trace individual listings.

A stable 41-field contract. Job content, location, salary, company, application, contact, and processing fields use the same names across repeat runs. Source omissions stay empty instead of being filled with guesses.

Explicit filter boundaries. Keyword, country, and optional location drive discovery without a separate jooble api key; remote, date, distance, and job type are not request inputs. Optional inputs affect a request only when supplied.

Low-risk evaluation. One result is enough to inspect relevance, salary coverage, employer detail, and application URLs before increasing volume or adding a schedule.

Apify delivery surfaces. The same input works through Console, API clients, Datasets, schedules, webhooks, and MCP without changing the result schema.

Jooble's official REST API documentation requires an API key and documents keyword, location, radius, salary, and paging parameters; this independent Actor uses its own narrower public input contract.

Quick Start Guide

Step 1: Configure

Open the Actor input, keep the prefilled working values or use the shared Warehouse Worker scenario, and set only fields listed in Input Parameters.

Step 2: Run

Start with max_results: 1. The limit is the maximum number of published jobs for this single-platform Actor.

Step 3: Collect

Inspect the default Dataset, especially platform_url, official_url, nullable salary fields, company_name, and processed_at. Export JSON, CSV, Excel, XML, or another Apify-supported Dataset format after the shape fits the workflow.

Input Parameters

Jooble Jobs Scraper exposes 5 public inputs in schema order, with 3 required and every other filter optional.

ParameterTypeRequiredDescriptionExample
max_resultsintegerYesMaximum number of Jooble job results to return.1
keywordstringYesJob title, skill, or company search term sent to Jooble.Engineer
countryselectYesCountry used for the Jooble search endpoint.United States
locationstringNoCity, area, or postal code used for the Jooble search.
currencyselectNoOptional target currency for converting salary amounts returned by Jooble.

country has 65 accepted values; currency has 166 accepted values. Inputs are prefilled with a working example, while optional fields without values stay non-restrictive.

Shared scenario:

{
"max_results": 1,
"keyword": "Warehouse Worker",
"country": "Poland",
"location": "Warsaw",
"currency": "USD"
}

Output Data Schema

Each Dataset item represents one accepted public job listing in a 41-field schema, with missing source values left empty.

Field groupFields
Source and linksplatform, platform_url, official_url
Job identitytitle, description, job_type, job_level, job_function, listing_type, skills, experience_range
Dates and availabilityposted_date, valid_through, applicant_count, vacancy_count
Location and work modelocation, is_remote, work_mode
Compensationsalary_period, salary_minimum, salary_maximum, salary_currency
Applicationeasy_apply
Companycompany_name, company_type, company_founded, company_industry, company_url, company_website, company_logo, company_addresses, company_revenue, company_description, company_rating, employee_count, review_count
Public contact signalsemails, phones, social_links
Processing metadataprocessor, processed_at

The following JSON is abbreviated and illustrative; a real item uses all 41 public field names even when some values are null:

{
"platform": "Jooble",
"platform_url": "https://example.com/jooble-jobs-scraper/listing-123",
"official_url": null,
"title": "Warehouse Worker",
"location": {
"raw": "Warsaw",
"country": "Poland"
},
"salary_minimum": null,
"salary_maximum": null,
"salary_currency": null,
"company_name": "Example Employer",
"processed_at": "2026-08-10T12:00:00.000Z"
}

Results can be exported through Apify Datasets in JSON, CSV, Excel, XML, RSS, and other supported formats.

Integration Examples

Call Jooble Jobs Scraper with public Actor ID 8GyhemcELZ9fi55a3 or name form agentx/jooble-jobs-scraper; every example uses the same Warehouse Worker scenario.

Actor ID

8GyhemcELZ9fi55a3

HTTP

curl -X POST "https://api.apify.com/v2/acts/8GyhemcELZ9fi55a3/run-sync-get-dataset-items?token=YOUR_APIFY_TOKEN" \
-H "Content-Type: application/json" \
-d '{"max_results":1,"keyword":"Warehouse Worker","country":"Poland","location":"Warsaw","currency":"USD"}'

Python

from apify_client import ApifyClient
client = ApifyClient("YOUR_APIFY_TOKEN")
run = client.actor("8GyhemcELZ9fi55a3").call(run_input={'max_results': 1, 'keyword': 'Warehouse Worker', 'country': 'Poland', 'location': 'Warsaw', 'currency': 'USD'})
items = client.dataset(run["defaultDatasetId"]).list_items().items

JavaScript

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: 'YOUR_APIFY_TOKEN' });
const run = await client.actor('8GyhemcELZ9fi55a3').call({"max_results": 1, "keyword": "Warehouse Worker", "country": "Poland", "location": "Warsaw", "currency": "USD"});
const { items } = await client.dataset(run.defaultDatasetId).listItems();

Make.com and n8n

Use the Apify module or node with Actor ID 8GyhemcELZ9fi55a3, paste the same JSON input, wait for completion, and read the default Dataset. Store the Apify token in the platform's credential manager.

MCP

{
"mcpServers": {
"apify": {
"url": "https://mcp.apify.com?tools=agentx/jooble-jobs-scraper",
"headers": {"Authorization": "Bearer <APIFY_TOKEN>"}
}
}
}

Use the API page for generated SDK and OpenAPI examples.

Pricing

Jooble Jobs Scraper costs $0.00280 per Result on FREE plus $0.01000 per minimum Actor Start event; one published-result test totals $0.01280.

Event or tierPriceBilling unit
Actor Start$0.01000One event per GB of selected memory, minimum one
FREE Result$0.00280One default Dataset item
BRONZE Result$0.00252One default Dataset item
SILVER Result$0.00224One default Dataset item
GOLD Result$0.00210One default Dataset item
PLATINUM Result$0.00210One default Dataset item
DIAMOND Result$0.00210One default Dataset item

Smallest run: $0.01000 + 1 × $0.00280 = $0.01280. A representative 100-result FREE run with one minimum start event is $0.01000 + 100 × $0.00280 = $0.29000. Batched results share the run start instead of paying a new start for each item. Prices can change; check live pricing.

Use Cases

Aggregated vacancy discovery by role and country. Use the documented filters to define the cohort, retain platform_url for traceability, and compare only fields actually published by Jooble. Start with a one-result run before turning the input into a recurring workflow.

Source triage using Jooble and official application URLs. Use the documented filters to define the cohort, retain official_url for traceability, and compare only fields actually published by Jooble. Start with a one-result run before turning the input into a recurring workflow.

Listing-lifecycle review using posted and expiration fields. Use the documented filters to define the cohort, retain processed_at for traceability, and compare only fields actually published by Jooble. Start with a one-result run before turning the input into a recurring workflow.

Salary monitoring from disclosed source values. Use the documented filters to define the cohort, retain company_name for traceability, and compare only fields actually published by Jooble. Start with a one-result run before turning the input into a recurring workflow.

Recurring market snapshots for job feeds and dashboards. Use the documented filters to define the cohort, retain salary_currency for traceability, and compare only fields actually published by Jooble. Start with a one-result run before turning the input into a recurring workflow.

Alternatives

Manual Jooble browsing is reasonable for checking a handful of listings, reading final descriptions, and making application decisions. It becomes difficult to repeat when a team needs structured snapshots, nullable fields, exports, or scheduled delivery.

The source's own search is the best choice for interactive discovery, account features, saved jobs, alerts, and applications. Jooble Jobs Scraper is the better fit when the requirement is a repeatable Dataset and API/MCP delivery; it does not replace the source experience or claim affiliation.

An unnamed multi-source job-data service may suit teams that want a vendor-managed feed with a broader commercial contract. A custom integration offers maximum control but leaves source changes, normalization, retries, storage, and monitoring with the engineering team.

Choose something else if the project needs private candidate profiles, resume databases, automated applications, guaranteed field completeness, historical vacancies that are no longer public, or a legal determination about downstream use.

Limits and Troubleshooting

The main limits come from live public source inventory and the Actor-specific input contract.

  • Jooble can aggregate listings from other publishers; verify official_url when available — Treat this as expected source behavior, not a promise that the cap will be filled; first verify the same search on the source and then broaden only the restrictive input.
  • One run selects one of 65 country markets — Keep the unsupported dimension out of the request and, when it matters analytically, filter the normalized Dataset after collection.
  • Remote, recency, distance, and employment type are not request filters — Reproduce the condition with max_results: 1, preserve the exact input, and use the source URL to distinguish a parser problem from changing source inventory.
  • Source quality checks can reduce output below the requested cap — Model nullable values explicitly in downstream storage and calculations; an absent value must not be converted into zero or a fabricated category.
  • Expiration values do not independently guarantee a vacancy remains open — For scheduled monitoring, store processed_at and source URLs, expect listings to change, and compare snapshots instead of assuming a permanent record.

For a reproducible issue, run max_results: 1 with the exact keyword and country, then open Apify Issues with the run URL, expected behavior, and affected source. Never include an API token or private data.

Trust and Reliability

Apify records each run, Dataset, input, status, and billed event under the user's account. This Actor declares one Result event per default Dataset item and an Actor Start event tied to selected memory.

The documented Dataset contract contains 41 fields, keeps source URLs, and leaves unavailable public values empty. The Actor does not guarantee relevance, inventory, salary coverage, company completeness, or contact availability that the source does not publish.

Data scope. The Actor collects accessible public job and employer information; it does not request source-account credentials or private candidate data.

User responsibility. Review applicable laws, source terms, database rights, privacy obligations, and retention rules for every country and workflow. This documentation is not legal advice.

Responsible use. Keep attribution where required, verify listings before acting, protect stored data, and do not use public contact fields for spam, unlawful profiling, or discriminatory decisions.

Frequently Asked Questions

Is this a jooble api without an api key?

Yes. No Jooble API key is a public input; authenticated API or MCP calls still require an Apify account and token.

How do I get jooble jobs by keyword and country?

Set the required max_results, keyword, and country values, add only supported optional filters, and inspect a one-result Dataset before scaling.

Does Jooble Jobs Scraper require source credentials?

No source username, password, cookie, or API key is a public input. Apify authentication is required for API and MCP execution.

Why are salary, company, or contact fields empty?

Those fields depend on public source and employer pages. Empty means unavailable, not zero, and the Actor does not invent missing values.

Is there a free jobs API?

The Actor uses pay-per-event pricing under your Apify plan. Start with the one-result calculation in Pricing to measure relevance and populated fields before increasing volume.

Can I schedule runs to monitor Jooble jobs over time?

Yes. Use Apify schedules after testing the input, and retain processed_at plus source URLs because listings can update, close, or reappear.

How does Result billing work?

Each item written to the default Dataset bills one Result event. Actor Start event count depends on memory, with a minimum of one event per run.

AgentX publishes 77 Actors; the three closest choices appear first, followed by the complete catalog grouped by category.

Closest to this Actor:

Business and Market Intelligence

Jobs and Hiring

Social Media

Video, Transcripts and Downloads

E-Commerce and Retail

Classifieds and Automotive

Real Estate

Support and Community

Ask about Jooble job search, input filters, Dataset fields, API, MCP, and billing in the AgentX community on Telegram; for a reproducible bug, open an Issue with the run ID and exact input.

AgentX is an Arcyton brand — arcyton.com.

Last Updated: August 10, 2026