Skip to content

Jooble and Talent.com as licensed sources (WING-404 research)

Researched 2026-08-06 by Gronktayvius (Grok, live doc/page fetches). Jenny's parallel run failed on a tool-permission check and produced nothing, so this is a single-seat finding — treat the uncertain items as uncertain rather than cross-checked.

Motivation: Adzuna is one of the last licensable job-search APIs (Indeed's publisher program closed 2024; ZipRecruiter's is employer-side), and its non-tech breadth is real — IT was 8.6% of 1,200 sampled listings. These two were the other names still running publisher programs.

THE FINDING THAT MATTERS MOST: they share a supply layer

Source Appcast presence
Adzuna click.appcast.io was the largest single destination, 64 of 192 sampled
Talent.com appcast-appcast-agg-usd was the top feedcode, 27 of one live SERP

Two unrelated aggregators, the same ad-tech exchange underneath. Adding aggregators may add far less UNIQUE inventory than their catalogue sizes imply, because they are substantially reselling the same Appcast-mediated supply.

This should be measured before any integration work: pull the same query from two sources and compute overlap on (company, title, location). Catalogue size is a vanity number; unique reach is the one that decides whether a second source is worth building.

Jooble

Item Finding
Public API Yes — documented REST, POST https://jooble.org/api/{key}, key by registration form
Docs help.jooble.org REST API article, modified 2025-05-26
Free tier / limits / cost UNKNOWN — jooble.org/api/about is Cloudflare-403 to plain clients
Description snippet only, not full text; truncation length undocumented
Salary {min} - {max} {currency} string, NO flag for estimated vs employer-stated
source field EXISTS — names the posting's source. Adzuna has no such field.
Stable posting id id present; stability across rescrapes UNKNOWN
Apply link Points at a Jooble lander, not the employer. Employer url not documented in payload.
Bot posture robots.txt 200; HTML pages 403 Cloudflare challenge — same class as Adzuna
Coverage 67 countries
Competes with us? No AI auto-apply product found — lower collision than Adzuna's ApplyIQ

Read: the source field is genuinely valuable — it is exactly the provenance Adzuna withholds, and it would let us route a listing to the board that actually holds it. Everything else is the Adzuna shape: snippet not full text, lander not employer, WAF on HTML.

Salary is worse than Adzuna in one respect: Adzuna at least flags salary_is_predicted. Jooble gives a range with no provenance, so we could not honestly label it.

Talent.com (ex-Neuvoo)

Item Finding
Public API Marketing only. Publisher page claims "self-serve job API" but the CTA is "get in touch"; no public API reference found
Payload schema UNKNOWN — no developer doc located. Do not design against assumed fields.
Free tier / limits / cost UNKNOWN
Coverage claim 30M+ jobs, 79 countries, 1,000+ publisher sites
Job view page talent.com/view?id={id} → 200
Apply/redirect talent.com/redirect?id={id} → 403 CloudFront to plain clients
robots.txt disallows /redirect*, /convert*, /services/api-new/search
Employer url pre-auth Sometimes present in page HTML, but not a reliable contract
Provenance feedcode on SERP logos exposes the supplier — genuinely useful signal

Observed feedcodes on one non-tech SERP: appcast-appcast-agg-usd (27), jazzhr-ats (7), aimwel-monster-us (3), plus potbelly-talentreef-ats, manatal-ats, viterbit-ats-organic, shaker-fedex and Recruitics. So the inventory is broad and non-tech — aligned with why we want Adzuna — and simultaneously Appcast-dependent in the same way.

Read: treat as sales-gated CPC/affiliate inventory, not an open developer API, until a partnership conversation produces a written schema and sample payloads. Designing against UNKNOWN fields would be inventing a contract.

Recommendation

  1. Measure overlap before integrating anything. Same query, Adzuna vs Jooble, dedupe on (company, title, location). If unique reach is small, a second aggregator buys little.
  2. Jooble is the better next source — real docs, obtainable key, and a source provenance field Adzuna lacks. Get a key and measure: snippet length distribution, salary fill rate, source histogram, and link host histogram.
  3. Talent.com needs a sales conversation first. No schema, no verifiable terms.
  4. Neither solves the apply path. Both hand back a lander behind a WAF. The value on offer is discovery breadth, and that is what they should be judged on.

Honesty notes

  • Single seat (Grok). Jenny's cross-check failed and was not rerun.
  • Jooble's API endpoint itself was not tested with a real key — only its docs and public HTML. Whether the API is challenge-gated is UNKNOWN.
  • Talent.com's payload is entirely UNKNOWN; the field observations come from the public web surface, not a licensed API response.