LinkedIn Jobs vs Jooble API for AI agents
LinkedIn documents no public job search API; its jobs API is for approved partners (ATS systems, job distributors) to post jobs to LinkedIn, and it is closed to new partners. Jooble API is a REST API that lets site owners take Jooble job search results and show them on their own website.
The short answer
- LinkedIn Jobs: ATS vendors and job distributors that already partner with LinkedIn and need to publish jobs to it; not for finding jobs.
- Jooble API: Embedding Jooble search results in your own site design for a single country.
Side by side
| LinkedIn Jobs | Jooble API | |
|---|---|---|
| Searches | Not a search API: it posts jobs into LinkedIn on behalf of customers. | Jooble's aggregated job search, one country per key (a jooble.org key covers US listings; other countries use their regional domain). |
| Returns | – | JSON with totalCount and jobs, each with id, title, location, snippet, salary, source, type, link, company and updated. |
| Before the first call | LinkedIn approval, a signed API agreement with data restrictions, and Talent Solutions partner status; currently not accepting new partnerships (points to Apply Connect instead). | Fill in a form (name, position, email, website, phone) to get a key; each country domain needs its own key, sent in the URL path of a POST. |
| Free | – | The free plan has a lifetime limit of 500 requests per key (not monthly). |
| Acting on a result | – | link is the job posting on Jooble. |
| Limits on keeping or showing results | LinkedIn API Terms forbid caching or storing Content except as needed to run your application, and bar content obtained by scraping or crawling outside the APIs. | Not stated on its pages |
| Coverage | – | Per-country keys via Jooble's regional domains (e.g. jooble.org for the US, uk.jooble.org, de.jooble.org). |
| MCP server | – | No official server listed |
Where Openpath fits
If the agent needs a job to apply for in Austin, Texas, or a remote one, Openpath returns the listings themselves, free and with no key. See Openpath vs LinkedIn Jobs and Openpath vs Jooble API.
Questions people ask
What do I need before I can use Jooble API?
Fill in a form (name, position, email, website, phone) to get a key; each country domain needs its own key, sent in the URL path of a POST.
Is Jooble API free?
The free plan has a lifetime limit of 500 requests per key (not monthly).
Sources
Every line about another company comes from its own pages. Prices and terms change, so check the source before you rely on one.
LinkedIn Jobs, read on October 15, 2026:
- learn.microsoft.com/en-us/linkedin/talent/job-postings/api/overview: “We are currently not accepting new partnerships for LinkedIn's Job Posting API.”
- learn.microsoft.com/en-us/linkedin/talent/job-postings/api/overview: “enables authorized third parties such as clients, ATS systems, and job distributors to post jobs directly to LinkedIn”
- learn.microsoft.com/en-us/linkedin/talent/job-postings/api/overview: “The use of these APIs is restricted to those developers approved by LinkedIn.”
- linkedin.com/legal/l/api-terms-of-use: “You must not capture, copy, cache, or store any Content”
- linkedin.com/legal/l/api-terms-of-use: “scraping, crawling, spidering or using any other technology or software to access LinkedIn content outside the APIs”
Jooble API, read on October 15, 2026:
- jooble.org/api/about: “take search queries from Jooble and post the results on your website in your own design”
- jooble.org/api/about: “please fill out the following form. This is required to obtain a key.”
- help.jooble.org/en/support/solutions/articles/60001448238-rest-api-documentation: “The free REST API plan includes a total lifetime limit of 500 requests per key.”
- help.jooble.org/en/support/solutions/articles/60001448238-rest-api-documentation: “Each Jooble domain (country) requires its own unique REST API key.”
- help.jooble.org/en/support/solutions/articles/60001448238-rest-api-documentation: “Direct URL to the job posting on Jooble.”