Jooble API: what you get, the limits, and the alternatives

Jooble is one of the largest job-search aggregators most developers have never looked at directly - it operates localized job search in 60+ countries and, unusually for the category, offers a free API. If you need a quick, zero-cost feed of aggregated postings, the Jooble API is a legitimate option. Here is what it actually returns, where it runs out, and what to use when it does.

How the Jooble API works

You request a free key on Jooble’s API page, then POST a JSON query to your keyed endpoint:

curl -X POST "https://jooble.org/api/$JOOBLE_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "keywords": "data engineer",
    "location": "Berlin"
  }'

The response contains a totalCount and a jobs array with title, company, location, a snippet of the description, salary when available, the source name, and a link. Setup to first result is genuinely minutes - among free options, only the single-board feeds are simpler.

Where it runs out

• Snippets, not full records. Descriptions are truncated excerpts, salary is free-text when present, and there are no structured fields to filter on beyond keywords and location.
• Links route through Jooble. The API exists to send traffic to Jooble’s listings - reasonable for a job widget on your site, limiting for a data product.
• Aggregator provenance. Records are collected from job boards and career sites without source attribution you can query, and the same role can appear multiple times via different boards.
• Query-shaped access. Like every search-style API, comprehensive coverage means enumerating queries; there is no firehose, webhook, or change feed.

Jooble API vs the alternatives

Against the other free options - we compare all eight on our free jobs API page - Jooble’s edge is international breadth: 60+ countries from one key beats anything else at the price. Adzuna returns better aggregate analytics; the single-board feeds (Remotive, RemoteOK) return richer records for their niches.

The structural alternative is reading the ATS layer instead of an aggregator’s copy. JobsPipe indexes postings where they are first published - Workday, Greenhouse, Lever, Ashby, and 30+ more - and returns full normalized records: complete descriptions, structured salary, explicit per-source attribution, cross-source dedup, and webhooks on new postings. The trade is a metered free tier (100 requests/month) instead of Jooble’s free-with-catches model.

A fair split: Jooble for a free international job widget; the ATS layer for a product built on the data.