Alternative Sources Gronktayvius Raw
I'll evaluate Jooble and Talent.com against your Adzuna bar with live docs and pages only — OBSERVED vs INFERRED, UNKNOWN when I can't verify.# Jooble vs Talent.com as licensed job-search sources
Method (2026-08-06): Official docs and live HTTP probes from this machine. OBSERVED = page/response we fetched. INFERRED = reasonable reading of marketing/third-party text. UNKNOWN = not verified — do not build on it.
Your Adzuna bar (non-tech inventory, 500-char caps, predicted salary, WAF, account-gated employer URL, Appcast hop) is the right scorecard. Both candidates share pieces of that failure mode; neither clears it cleanly without a paid partner handshake and a live key smoke test.
JOOBLE¶
1. API access — OBSERVED: real, documented, free-key path¶
| Item | Status | Evidence |
|---|---|---|
| Public publisher REST API | Yes | Help Center REST docs (modified 26 May 2025) |
| How to get a key | Form / registration on https://jooble.org/api/about |
Official help: “Register… copy and save the API key” |
| Auth model | Key in URL path, body is POST JSON | POST https://jooble.org/api/{api_Key} |
| Free tier | Claimed free by third-party guides; rate/cost on about page = UNKNOWN | We could not read jooble.org/api/about (Cloudflare challenge 403) |
| Rate limits | UNKNOWN (docs we could read do not state numeric limits) | Help docs only document 403 invalid key / 404 |
| Cost | UNKNOWN for commercial volume | Same |
Developer pages (cite these):
- https://help.jooble.org/en/support/solutions/articles/60001448238-rest-api-documentation
- https://help.jooble.org/en/support/solutions/articles/60000922689-how-to-connect-to-the-jooble-rest-api-after-receiving-the-key
- https://jooble.org/api/about (canonical; blocked to plain HTTP clients today)
OBSERVED: Partnership folder also covers ATS/employer partnership, separate from the job-search API.
2. Payload shape — OBSERVED from official docs¶
Documented response fields:
| Field | Doc meaning | Notes for you |
|---|---|---|
id |
“Unique job identifier” | Stable within Jooble — UNKNOWN if globally stable across rescrapes |
title |
Job title | |
location |
Job location | Free text in examples ("Kyiv") — not structured city/state/country |
snippet |
“Job description snippet displayed in search results” | Not full text. Truncation length UNKNOWN (no char cap in docs) |
salary |
“Salary range in format {val1} - {val2} {currency}” |
No flag for employer-stated vs estimated. Presence/absence when missing: UNKNOWN from official docs |
source |
“The source of the job posting” | Yes — provenance field exists (example value "jooble"; third parties show board domains — treat as INFERRED until you sample with a key) |
type |
“full-time, part-time, etc.” | Employment type present |
link |
“URL to the job posting” | Points at Jooble host, not employer (see §3) |
company |
Company name | |
updated |
Last updated datetime | Not original “posted date” — OBSERVED field name is updated |
Request params of note: keywords, location, radius (fixed set: 0,4,8,16,26,40,80 km), salary (min, integer), page, ResultOnPage, SearchMode, companysearch.
Full description in search response: No (snippet only). Full body only if the link lander has it — separate fetch problem.
3. The link — most important; OBSERVED shape, apply path UNKNOWN without key¶
Official example:
"link": "https://ua.jooble.org/jdp/12345"
https://jooble.org/desc/{id}-style URLs.
OBSERVED from https://jooble.org/robots.txt: crawl disallows include /away/, /redir, /desc/, /m/away/, /m/redir — i.e. Jooble maintains redirect/away endpoints typical of click-tracking landers.
| Question | Answer |
|---|---|
| Points at employer directly? | No in API schema — Jooble lander |
| Tracker hop? | Likely (/away, /redir) — INFERRED from robots path names |
| Employer URL in API payload? | Not documented — treat as absent until proven |
| Account required before employer URL? | UNKNOWN (could not pass Cloudflare to browse live JD pages) |
| One-hop to employer? | UNKNOWN without authenticated browser session + key |
Engineering risk: same class as Adzuna: discovery OK, apply path may be a Jooble lander + redirect chain. Do not assume direct ATS URLs.
4. Bot posture — OBSERVED: hard Cloudflare¶
| Probe | Result |
|---|---|
GET https://jooble.org/api/about |
403, Server: cloudflare, Cf-Mitigated: challenge |
GET https://jooble.org/jobs-nurse-Chicago |
403 same |
GET https://jooble.org/robots.txt |
200, reachable |
So: robots.txt yes; human/browser challenge yes; plain clients and headless will fail the same way Adzuna’s CloudFront did for HTML. API POST with a valid key was not tested (no key) — UNKNOWN whether the API endpoint itself is challenge-gated.
5. Inventory character — partially OBSERVED, not measured like Adzuna¶
| Claim | Label | Source |
|---|---|---|
| ~69 countries, 140,000+ sources | OBSERVED (Play Store app listing text) | Google Play “About this app” |
| 67 countries, “millions” daily visitors | OBSERVED (Jooble Help partnership copy) | help.jooble.org partnership folder |
| Non-tech / hourly heavy like Adzuna | UNKNOWN | No occupation sample run without a key |
| Unique vs syndicated | Aggregator of boards/career pages — INFERRED | Product type; source field exists to measure this once keyed |
INFERRED: global generalist aggregator, not tech-only — but you must re-run your 25-occupation sample after key issuance. Do not seat it on brand reputation alone.
6. Compete with AI-apply? — No ApplyIQ-class product OBSERVED¶
- Jooble app markets job search + CV attach / notifications.
- No public “AI auto-apply / ApplyIQ” product found on Jooble properties in this pass.
- They do have ATS/partner funnels for employers — different threat model than defending candidate apply automation.
Verdict on motive: lower direct product collision than Adzuna ApplyIQ; still monetize via CPC/traffic partnership INFERRED.
7. Jooble verdict¶
Seat as discovery candidate: YES for evaluation, conditional for production.
Why: Only one of the three with public field-level REST docs + self-serve key form + a source field. That is materially better for engineering than Talent’s sales fog.
Blockers before build: 1. Obtain key; measure snippet length distribution, salary fill rate, source histogram, link host histogram. 2. Trace 50 apply clicks: does employer URL ever appear pre-auth? 3. Confirm commercial ToS allow a candidate-side apply product (about page unreadable to us). 4. Rate limit / paid tier still UNKNOWN.
TALENT.COM (ex-Neuvoo)¶
1. API access — OBSERVED marketing, no public field docs¶
Publisher program page: https://employers.talent.com/publishers
OBSERVED claims: - 30M+ jobs in 79 countries - 1,000+ job search websites as publishers - Three products: XML feeds, Job API (“self-serve job API … backfill … high paying jobs”), Affiliate URLs - CTA is “Get in touch with our team of experts” — not a public developer console with schemas
| Item | Status |
|---|---|
| Public publisher/partner job API exists? | Marketed yes |
| Self-serve signup with docs? | Contradictory marketing — page says “self-serve” but only sales CTA; no public API reference found |
| Free tier / rate limits / cost | UNKNOWN |
| Payload schema | UNKNOWN (no developer doc page located) |
| Employer-side integrations | Well documented (XML into Talent for ATS posting) — wrong direction for you: https://www.talent.com/integrations |
Bottom line: treat Talent as sales-gated CPC/affiliate inventory, not an Adzuna-style open developer API, until partnership replies with a written schema and sample payloads.
2. Payload shape — UNKNOWN for licensed API; OBSERVED web surface only¶
No official publisher Job API field list found. Do not invent fields.
From live SERP HTML (warehouse associate + Chicago, 2026-08-06):
OBSERVED provenance signals (logo feedcode=):
| feedcode (sample) | Count (this SERP) | Character |
|---|---|---|
appcast-appcast-agg-usd |
27 | Appcast paid/syndicated — same ad-tech family as Adzuna’s top hop |
jazzhr-ats |
7 | ATS organic |
aimwel-monster-us |
3 | Monster via Aimwel |
potbelly-talentreef-ats, manatal-ats, viterbit-ats-organic, shaker-fedex, logistics Recruitics |
3 each | Mixed ATS / employer |
So inventory is broad + heavily Appcast-weighted on this non-tech query — aligned with Adzuna’s non-tech value, but also aligned with Adzuna’s Appcast dependency.
Description/salary/id for the licensed API: UNKNOWN.
Web surface shows large numeric job ids (e.g. 550249823928856008) — OBSERVED as Talent’s internal id on redirect params.
3. The link — OBSERVED: same failure class as Adzuna¶
| Probe | Result |
|---|---|
Job view https://www.talent.com/view?id={id} |
200 (CloudFront, no JS challenge on HEAD) |
Apply/redirect https://www.talent.com/redirect?id={id} |
403 Forbidden, Server: CloudFront for plain curl |
robots.txt |
Disallows /redirect*, /*/redirect*, /convert*, and /services/api-new/search |
OBSERVED destinations embedded in a job-view page (pre-auth HTML we fetched):
- Dominant: https://click.appcast.io/t/... (dozens)
- Also: apply.j-vers.com, jobsflag.com, plus occasional employer/ATS hosts on SERP (careers.fedex.com, farmersfridge.applytojob.com, jobs.conexusfood.com, cf-apply.jobappnetwork.com, Aimwel redirect)
SERP also contains showSignInModal=true on pagination and many sign_in / “Apply Now” strings — INFERRED account push on the product, but not proven that employer URL is hard-gated behind auth for every listing (unlike your measured Adzuna ~22% hosted-gate).
| Question | Answer |
|---|---|
| API/apply URL = employer? | No for official path — /redirect? tracker |
| Tracker? | Yes — Appcast heavily |
| Employer URL in page before auth? | Sometimes yes in HTML (direct careers hosts + Appcast tokens); not reliable as a product contract |
| Account required? | UNKNOWN systematically; product clearly wants sign-in |
This is the Adzuna-killer pattern again: discovery page works; bot-hostile redirect; Appcast as first-class hop.
4. Bot posture — OBSERVED¶
| Asset | Result |
|---|---|
| Homepage / SERP / view | 200, CloudFront, Next.js (client-heavy) |
/redirect |
403 to plain client |
robots.txt |
Reachable (explicitly blocks redirect/apply crawl paths) |
Less “Cloudflare interactive challenge on every page” than Jooble; more “CloudFront deny on the monetized click path” — still fatal for automated apply resolution without browser cookies / partnership click tokens.
5. Inventory character — OBSERVED + claims¶
| Item | Status |
|---|---|
| Scale claim | 30M+ / 79 countries (publishers page); some locales market “40M+” |
| Non-tech / hourly | Warehouse SERP populated; Appcast + staffing brands dominate sample — looks Adzuna-like, not tech-only |
| Unique vs syndicated | Heavy syndication (Appcast, Monster/Aimwel) + some ATS organic — not unique inventory |
| Countries | Global (79 claimed) |
6. Compete with AI-apply? — Easy Apply yes; ApplyIQ-class no (with caveats)¶
- OBSERVED: product UX has Apply Now / quickapply (
action=quickapplyon redirect params). - Third-party strategy blogs claim a 2024 “Easy Apply” rollout — mark INFERRED (not primary Talent product marketing we verified on a first-party product page this pass).
- No public “AI applies for you while you sleep” product like Adzuna ApplyIQ found on first-party pages.
- Business model is PPC / publisher monetization — motive to protect click funnel and Appcast economics is strong even without an AI-apply product.
7. Talent.com verdict¶
Seat as discovery candidate: ONLY after sales partnership + written schema + apply-URL contract.
Without that, you are reverse-engineering a CPC network that: 1. hides the click behind CloudFront-403 redirects, 2. routes much of non-tech inventory through Appcast (same sink you already measured), 3. has no public payload contract.
Inventory character looks right for non-tech breadth. Apply path character looks wrong for a candidate-side product that needs employer reach.
Ranking for your product (non-tech breadth + usable apply path)¶
| Rank | Source | Role | Why |
|---|---|---|---|
| 1 | Jooble | Best next evaluation | Only one with live REST field docs, key form, source + id, free-key path. Still Jooble landers + Cloudflare HTML; must measure apply hop and snippet cap. |
| 2 | Adzuna | Known quantity | You already measured non-tech gold and apply-path poison. Keep only if you accept discovery-only (no apply) or get a commercial full-description / direct-URL feed. |
| 3 | Talent.com | Sales experiment, not self-serve build | Inventory and Appcast mix look familiar; no public API schema; redirect 403 + Appcast mirror Adzuna’s worst traits. Worth a partner call; not worth engineering until sample feed lands. |
For a candidate-side product that needs non-tech breadth and an apply path: none of the three is currently a clean “licensed apply pipeline.” Best realistic split:
- Discovery: Jooble (test) ± Adzuna (already wired) ± Talent (if partner feed includes destination URL).
- Apply: direct ATS (Greenhouse/Ashby/etc.) + employer career pages you already own — aggregators as coverage, not submission.
If Talent/Jooble partner terms forbid using listings for automated application products, kill them at legal review before build.
Other aggregators still offering publisher/partner access¶
Evaluated only enough to rank “worth a ticket” vs not. All need their own payload/link audit.
Worth evaluating next (real publisher surfaces)¶
| Source | Access model | What we know | Priority |
|---|---|---|---|
| Careerjet | Self-serve publisher signup + documented API | Endpoint https://search.api.careerjet.net/v4/query; Basic auth with API key; fields include title, company, date, description (excerpt, default 120 chars via param), structured salary_*, url → https://jobviewtrack.com/v2/... (tracker, not employer). Requires user_ip + user_agent. Docs: https://www.careerjet.com/partners/api · https://www.careerjet.com/partners/publishers |
High — best-documented peer to Jooble; same lander risk |
| WhatJobs | Publisher program + FeedAPI (JSON/XML REST) | Sales contact to start; FAQ lists partners (Monster, StepStone, LinkedIn, Dice, etc.). https://www.whatjobs.com/affiliates | Medium-high |
| Jobg8 | Network “Receiving Jobs” (sales) | Monetize clicks/applies; styled as your content; US claims 1.5M+ jobs. Not a public open API. https://www.jobg8.com/ReceivingJobs.aspx | Medium (commercial feed, not DIY) |
Different category (data vendors / scrapers — not classic affiliate CPC)¶
| Source | Notes |
|---|---|
| JobsPikr | Paid Job Search API (Apiary docs exist); career-site crawl vendor; pricing often enterprise (third parties cite ~$4k/yr). Good for data, not CPC partnership: https://jobspikr.docs.apiary.io/ |
| Coresignal / Fantastic Jobs / Bright Data / TheirStack | Job datasets for AI/analytics; not publisher CPC. Evaluate if you want full text + employer URL and can pay SaaS rates. |
| Arbeitnow | Free public ATS-oriented board API (EU/UK, Greenhouse etc.) — tech/remote skew, not Adzuna-like non-tech breadth: https://www.arbeitnow.com/api/job-board-api |
| Remotive | Free remote jobs API — tech remote only |
Closed / wrong direction (confirming your scarcity thesis)¶
| Source | Status |
|---|---|
| Indeed Publisher API | Closed (your note matches industry writeups) |
| ZipRecruiter Partner API | Employer/ATS side (post jobs, webhooks) — not candidate discovery inventory |
What to do this week (cheap, high signal)¶
- Jooble: request key at
jooble.org/api/about(browser — Cloudflare). Run the same 25-occupation / 1,200-listing sample you used on Adzuna. Measure: snippet length histogram, salary empty rate,sourcetop-N,linkhost top-N, 50-click employer reach (pre-auth). - Careerjet: publisher signup → same sample. Docs already admit 120-char default excerpt and jobviewtrack URLs — expect discovery-only unless commercial terms expand description + destination.
- Talent.com: one email to publisher sales: ask for (a) sample JSON of Job API, (b) whether
destination_url/ employer URL is in feed pre-click, (c) whether candidate AI-apply products are allowed, (d) Appcast share of US non-tech. No engineering until sample feed arrives. - Do not scrape Jooble/Talent HTML as a substitute for licensed API — both encode anti-bot intent (CF challenge / CF 403 on redirect).
Confidence board¶
| Claim | Confidence |
|---|---|
| Jooble REST fields as documented May 2025 | High (official help) |
| Jooble free commercial use / rate limits | Unknown |
| Jooble description char cap | Unknown |
| Jooble employer URL before auth | Unknown (likely no) |
| Talent Job API self-serve with public schema | Low / contradicted by sales-only page |
| Talent redirect 403 + Appcast dominance on sample | High (live probe) |
| Talent non-tech inventory useful | Medium (one SERP; needs multi-occupation sample) |
| Careerjet API live with jobviewtrack URLs | High (official partners docs) |
| Either ships ApplyIQ competitor | Low product risk observed; Talent Easy Apply is UX, not auto-apply |
I did not invent payload fields or rate numbers where docs were silent. Next concrete unlock is a Jooble key + Careerjet publisher key and a shared measurement harness against the Adzuna notebook you already trust.