Skip to content

Jooble Job Postings via a Single Scraping API Call

Jooble aggregates job listings from thousands of upstream boards, which makes it a useful single entry point for hiring-trend and compensation research.

OUTPUT FORMATSHTMLJSONMarkdown

This page explains how a hosted scraping API turns a Jooble URL into structured job records — job title, company, salary range, location, source board and application link — without you running headless browsers or rotating proxies yourself. It also covers what each request costs in credits and where the option flags matter.

What the API actually does with a Jooble URL

You send a Jooble page URL plus your API key. The service loads the page in a real browser, rotates the outbound IP, and returns the rendered result. For structured output you either apply CSS/XPath extraction rules or let the AI extraction option describe the fields you want in natural language and return JSON. The job attributes the page advertises as parsed by default are job title, company name, salary range, location, employment type, source board and the application URL. Company reviews and required skills are also listed among the parsed outputs. If a field is not in that set, treat it as something you must target explicitly with extraction rules rather than assume it appears automatically.

Three common Jooble data workflows

The page frames three main reasons teams pull Jooble data. First, aggregation: collect postings across the aggregated index to follow hiring volume by role or region over time. Second, compensation research: use posted salary ranges for market analysis and to sanity-check pay bands. Third, company outreach: collect structured company contact details to support business development and networking. Each workflow uses the same request shape; what changes is the extraction target and how often you schedule the pull.

Field map: what comes back and what you must target

Use this as a planning checklist before you write extraction rules.

  • Returned as structured job attributes: job title, company name, salary range, location, employment type, source board, application URL.
  • Also listed as parsed: company reviews, required skills.
  • Anything else visible on the public page: reachable, but only if you define it with extract_rules (CSS selectors) or ai_extract_rules (natural-language description).
  • Post-login content: out of scope. The FAQ explicitly says to avoid it.

A practical rule: if a field is not in the first two bullets, add it to your extraction rules and test it against one live page before scaling the job.

How credits are spent per request

The base request starts at 1 credit. Option flags add cost, and the premium-proxy rate depends on whether JS rendering is on:

  • JavaScript rendering: 5 credits per successful request.
  • Premium proxy without JS rendering: 10 credits.
  • Premium proxy with JS rendering: 25 credits.
  • stealth_proxy: 75 credits.

A worked example: 1,000 Jooble pages per month with JS rendering and no premium proxy is roughly 5,000 credits. The same volume with premium proxy plus JS rendering is roughly 25,000 credits. With stealth_proxy it is roughly 75,000 credits. Compare that against the plan credit allowances before choosing a tier — the Hobby plan at $19/month lists 75,000 credits, which is exactly the stealth_proxy figure for 1,000 pages. Credit allowances are valid for one month and do not roll over.

Distinguishing the three failure modes

Not every failed request means the same thing, and the fix differs:

  • IP-based blocking: the target rejects the source address. The default rotating residential proxies are the first line of defence.
  • CAPTCHA challenge: the page serves a challenge instead of content. Enable stealth_proxy on the request.
  • JavaScript-only content: the HTML arrives but the job data is injected client-side. Enable render_js so the browser executes the page before capture.

If a request returns an empty or partial result, check which of these three conditions applies before changing anything else. The FAQ notes that if a target becomes aggressive, stealth_proxy is the escalation step.

Setup path

  1. Create an account to get an API key and the free starting credits.
  2. Pick a client: the page lists Python, Node, Go, PHP, Ruby and cURL samples, plus a dashboard request builder for testing without code.
  3. Send a GET request with the Jooble URL and your key.
  4. Add option flags only as needed: render_js, stealth_proxy, country_code, ai_extract_rules.

The page states setup can be done in under five minutes and that code samples exist in every major language. Those are the vendor's claims about its own onboarding; test them against your own stack before committing a production pipeline.

Decision checklist: API vs self-managed stack

Use this before you commit either way.

  • Volume: estimate monthly page pulls and multiply by the credit cost of the options you need. Compare against plan allowances.
  • Field coverage: confirm every field you need is either in the default parsed set or expressible in extract_rules / ai_extract_rules.
  • Blocking risk: if the target is aggressive, budget for stealth_proxy at 75 credits per request.
  • Legal review: confirm the target's terms of service permit your use case and that you are not touching post-login content.
  • Operational burden: a self-managed stack means owning proxy rotation, headless browser upgrades and CAPTCHA handling; the API bundles those.
  • Data retention: the vendor states it does not collect or store personal data from scraped sites unless the user explicitly requests it. Confirm this matches your own compliance obligations.
Per-request credit cost by option
OptionCredits per successful request
Base request1
JavaScript rendering5
Premium proxy (no JS rendering)10
Premium proxy + JS rendering25
stealth_proxy75

Premium proxy costs 10 credits with JS rendering disabled and 25 with it enabled. Confirm current credit rules before committing a production budget.

Plan credit allowances (captured reference)
PlanMonthly priceAPI creditsConcurrent requests
Hobby$19 /mo75,00025
Freelance$49 /mo250,00050
Startup (Recommended)$99 /mo1,000,000100
Business$249 /mo3,000,000200
Business +$599 /mo8,000,000400
Enterprise 14$999 /mo14,000,000500
Enterprise 24$1,599 /mo24,000,000600
Enterprise 41 (Recommended)$2,399 /mo41,000,000700
Enterprise 69$3,599 /mo69,000,000800
Enterprise 120$5,799 /mo120,000,000900

Prices are exclusive of VAT. Credit allowances are valid for one month and do not roll over. This is a captured reference; verify current pricing before purchase.

Frequently asked questions

Do I need an account to scrape Jooble?

You do not need a Jooble account. You do need an API key from the scraping service: sign up, get the key, and send the target URL. The free starting allowance is 1,000 credits with no card required.

Is scraping Jooble legal?

Public-facing pages can usually be scraped, but the decision depends on the target site's terms of service and your jurisdiction. Review those terms before deploying, and do not scrape post-login content. This is general guidance, not legal advice.

What data can I extract from Jooble?

Anything that renders on the public page. The default parsed set covers job title, company name, salary range, location, employment type, source board and application URL, plus company reviews and required skills. For other fields, define them with extract_rules (CSS selectors) or ai_extract_rules (natural-language description) to get structured JSON back.

How do I start scraping Jooble?

Sign up, copy your API key, and send a GET request with the Jooble URL. The service renders the page, rotates proxies, and returns the result. The free starting allowance is 1,000 credits for testing.

Will I get blocked when scraping Jooble?

The service rotates residential proxies and uses a real headless browser so requests resemble normal traffic. If a target becomes aggressive, enable stealth_proxy on the request as the escalation step.

How much does it cost to scrape Jooble?

The free starting allowance is 1,000 credits with no card required. Paid plans start at $19/month. Per-request cost depends on the options you enable: 5 credits for JS rendering, 10 for premium proxy without JS rendering, 25 for premium proxy with JS rendering, and 75 for stealth_proxy. See the credit-cost table above for the full breakdown.