Is There a Google Jobs API? What to Use Instead in 2026

Quick answer: No. Google has no public API for searching Google for Jobs, and Cloud Talent Solution searches a job board's own listings, not Google's. On 29 October 2026 we called 9 job APIs without a key: Arbeitnow, Remotive, The Muse, Jobicy and Himalayas answered with JSON, while USAJOBS, Adzuna, Reed and Jooble did not.

Public APIs, a crowdsourced directory of public APIs, records the auth method and CORS support of every API in its open-source list. So instead of repeating vendor pages, we called Google's two candidate pages and nine job APIs once each, anonymously, and wrote down what came back.

Does Google have a jobs API?

Not one you can query for job listings. The page people land on, jobs.google.com/about, answered our request with a 200 and this headline: "Have your job postings found by millions of job seekers who search on Google every day." It is written for employers and job boards that want their postings to appear in Google, not for developers who want to read them.

Nothing on that page is an endpoint. If your goal is to pull Google for Jobs results into your own app, Google does not sell or give away that access. Your real options are an independent job API, a keyed partner API, or a scraping vendor.

What is Cloud Talent Solution, and why is it not a Google Jobs search API?

Cloud Talent Solution is the closest thing Google offers, and it is the source of most of the confusion. Its documentation URL redirected once on 29 October 2026 and served a page titled "Cloud Talent Solution documentation".

The service searches the job inventory you supply. It is built for a job board, a staffing firm or an employer that already holds its own listings and wants better search over them. It does not return the jobs Google has indexed from the rest of the web. If you have no listings of your own, Cloud Talent Solution has nothing to search.

Which free job APIs can you call without a key?

Five of the nine answered our anonymous request with a 200 and a JSON body. Four of those five sent Access-Control-Allow-Origin: *, which means a browser page on any domain can call them directly.

| API | Endpoint we called | Status | Content type | CORS header | Bytes returned | |---|---|---|---|---|---| | Arbeitnow | /api/job-board-api | 200 | application/json | * | 2,189,737 | | Remotive | /api/remote-jobs?limit=1 | 200 | application/json | * | 131,068 | | The Muse | /api/public/jobs?page=1 | 200 | application/json | * | 123,286 | | Jobicy | /api/v2/remote-jobs?count=1 | 200 | application/json | * | 12,626 | | Himalayas | /jobs/api?limit=1 | 200 | application/json | not sent | 4,446 |

Source: one GET per endpoint on 29 October 2026, no credentials.

Two details matter more than the status codes. First, Himalayas sent no CORS header, so call it from your server, not from browser JavaScript. Second, response sizes vary wildly: Arbeitnow returned 2.19 MB from a call with no parameters, and Remotive returned 131,068 bytes even though we asked for limit=1. Check the size before you load a response into memory, and read our API pagination findings before you loop through pages.

Keyless does not mean unlimited. Cache what you fetch and back off on a 429, as our API rate limiting guide describes, because an anonymous client is the first one a provider throttles.

What did USAJOBS, Adzuna, Reed and Jooble return?

None of the four gave us job data without credentials, and each failed in a different way.

| API | What we called | Status | What came back | |---|---|---|---| | USAJOBS | /api/search?Keyword=developer | 401 | 165 bytes of application/problem+json | | Adzuna | /v1/api/jobs/gb/search/1 | 400 | an HTML error page headed "Well this is embarrassing..." | | Reed | /api/1.0/search?keywords=developer | 401 | an empty body, with Access-Control-Allow-Origin: * | | Jooble | /api/about (the API page) | 403 | a Cloudflare-served HTML page |

Source: one GET per URL on 29 October 2026, no credentials.

USAJOBS returns a structured JSON error, which is the polite way to say "send a key". Adzuna answered a JSON API path with HTML, so your client has to handle a failure that is not JSON at all. Reed sent an empty 401 but already allows cross-origin calls. Jooble refused even the documentation page to our browser user agent, so we cannot report anything about its endpoint.

The anonymous call cannot tell you what each free key includes. Read the provider's own terms before you build on it, and see our guide to API authentication methods for what "needs a key" means in practice. USAJOBS is US federal government data, so it sits alongside the other open government data APIs in the directory.

What about scraping Google Jobs results?

Scraping vendors fill the gap Google leaves. In the search results for google jobs api on 22 October 2026, every non-Google page in the top 10 sold a scraper or a job-data feed, including a SerpApi tutorial at position 4.

The cost is real and so is the risk. SerpApi listed a free plan of 250 searches a month and a Starter plan at $25 a month for 1,000 searches (pricing page, 16 October 2026). DataForSEO priced its SERP API from $0.0006 per SERP in Standard Queue to $0.002 in Live mode (16 October 2026). SerpApi also advertises a U.S. Legal Shield of up to $2 million in coverage, which tells you the vendors take the legal exposure of scraping seriously. Our SerpApi alternatives ranking compares the main vendors; we do not rank them for job data here.

What should you do?

As an API consumer:

1. Start with a keyless API from the first table. Use Arbeitnow, Remotive, The Muse or Jobicy from the browser; call Himalayas from a server.
2. Ask for the smallest page an API supports, and measure what it returns, since limit=1 did not keep Remotive's response small.
3. Move to USAJOBS, Adzuna or Reed when you need their coverage, and plan for a key, an error body that may not be JSON, and the provider's terms.
4. Use a scraping vendor only when you specifically need what Google shows, and budget for it per search.

As an API builder, copy USAJOBS: a missing key should return a 401 with a small JSON problem body, not an HTML page or an empty response.

Browse the jobs APIs in the directory for more options, each with its auth method and CORS support recorded.

How we measured

On 29 October 2026 at 10:31 UTC we sent one GET request to each of 11 URLs from one machine with curl, following redirects, with a desktop Chrome user agent and an English Accept-Language header. We recorded the status code, the decompressed body size, the Server, Content-Type and Access-Control-Allow-Origin headers, and the first <h1> in any HTML. A single call from one location is a small sample: a provider can answer differently from another network or on another day.

FAQ

Is there a free Google Jobs API?

No. Google offers no public API, free or paid, for searching Google for Jobs listings. On 29 October 2026, Arbeitnow, Remotive, The Muse, Jobicy and Himalayas all returned job data as JSON without a key, which makes them the practical free alternatives.

What is the best job search API?

It depends on the data you need. For remote jobs with no sign-up, Remotive, Jobicy and Himalayas answered anonymously in our probe. For US federal jobs, USAJOBS is the official source, but it returned a 401 without a key.

Can I call a job API from browser JavaScript?

Only if it sends a CORS header. Arbeitnow, Remotive, The Muse and Jobicy sent Access-Control-Allow-Origin: * on 29 October 2026, and Himalayas sent none, so route Himalayas calls through your server.

Does Cloud Talent Solution return Google for Jobs results?

No. Cloud Talent Solution searches the job listings you give it, so it suits a job board or employer with its own inventory. It does not expose the jobs Google indexes from other sites.