Is There a Google Jobs API? Talent Solution, Indexing and SERP

No, Google doesn't offer an API that returns the job listings you see in Google Search. What it has instead are tools for jobs you already own: Cloud Talent Solution searches jobs you upload, and JobPosting structured data with the Indexing API gets your jobs into Google's job results.

The third thing people mean by "Google Jobs API" is a SERP API, a third-party service that scrapes Google's job results for a query and returns them as JSON. This guide explains each one, what it's for and where its limits are. Google's documentation was checked on November 1, 2026.

At a Glance

Cloud Talent Solution: Search Over Your Own Jobs

Cloud Talent Solution (CTS) is a Google Cloud service that adds machine learning to job search on your site. Its basics page is direct about the data: "You send a list of jobs and companies to CTS, which stores them and indexes them into a searchable form." Google doesn't supply listings. If you have no jobs, a CTS search returns nothing.

What it gives you on top of your own data:

• Machine-learned search that infers structure from your job content
• Commute-time search and location filters
• Facet histograms for building filter counts
• Spelling correction, plus a completeQuery method for autocomplete
• Tenants, which keep each client's jobs separate if you run search for several job boards

The API is v4, served from jobs.googleapis.com. Resources are tenants, companies and jobs, with jobs:search for searches and jobs:searchForAlert for job-alert style queries. A search looks like this:

curl -X POST \
  "https://jobs.googleapis.com/v4/projects/$PROJECT_ID/tenants/$TENANT_ID/jobs:search" \
  -H "Authorization: Bearer $(gcloud auth print-access-token)" \
  -H "Content-Type: application/json" \
  -d '{
    "requestMetadata": {
      "domain": "jobs.example.com",
      "sessionId": "session-123",
      "userId": "user-456"
    },
    "jobQuery": { "query": "backend engineer" }
  }'

requestMetadata is required, and Google asks for real domain, sessionId and userId values so it can tune results. The response carries matchingJobs (each with a job and snippets), totalSize and a nextPageToken.

Is Cloud Talent Solution deprecated?

Not as of November 1, 2026. The v4 docs carry no deprecation or shutdown notice. Its release notes show that older versions were retired: Job Search v2 stopped working on April 3, 2020, and v3, v3p1beta1 and v4beta1 were scheduled to shut down on October 13, 2021, with users told to move to v4.

The product is quiet, though. The most recent release note is from December 19, 2024, and the one before that is from May 2023. That isn't a deprecation, but if you're choosing it for a new build, check the release notes and Google Cloud's deprecation pages first.

Google for Jobs: Getting Your Jobs Into Google

The job results in Google Search, often called Google for Jobs, are built from job pages Google crawls. There's no submission API that accepts job data directly. You publish job detail pages with JobPosting structured data, and Google reads them.

Google requires five properties: title, description, datePosted, hiringOrganization and jobLocation, with jobLocation optional for remote jobs that set applicantLocationRequirements. Our JobPosting schema guide has the full list and a working example.

The Indexing API is the fast path. Per Google, it "can only be used to crawl pages with either JobPosting or BroadcastEvent embedded in a VideoObject", and Google recommends it over sitemaps for job pages because it gets them crawled sooner. You send a URL notification when a job is posted or updated and a removal notification when it closes:

curl -X POST "https://indexing.googleapis.com/v3/urlNotifications:publish" \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"url": "https://jobs.example.com/jobs/123", "type": "URL_UPDATED"}'

Quotas, setup and how to check usage are in our Indexing API quota guide, and the full submission flow is in How to Submit Jobs to Google's Indexing API.

Two limits to know: the job experience isn't available everywhere (Google lists full coverage for North America, Latin America and Sub-Saharan Africa, and specific countries elsewhere), and both tools only publish your jobs. Neither returns anyone else's.

SERP APIs: Reading Google's Job Results

If what you want is "the jobs Google shows for this query", a SERP API is the only route, and it's a third-party scraper rather than a Google product. SerpApi's Google Jobs API is the best-known example: set engine=google_jobs and a query q, and it returns up to 10 results per page with apply_options (the sites you can apply on) and detected_extensions such as posting date, salary and schedule type. Pagination uses next_page_token, because Google dropped the start offset.

import os
import requests
 
res = requests.get(
    "https://serpapi.com/search",
    params={
        "engine": "google_jobs",
        "q": "data engineer austin",
        "api_key": os.environ["SERPAPI_KEY"],
    },
    timeout=30,
)
res.raise_for_status()
for job in res.json().get("jobs_results", []):
    print(job["title"], "|", job.get("company_name"), "|", job.get("location"))

Trade-offs to weigh:

• You get Google's view of the job. Fields are what Google displays, and location is a string rather than structured city, state and country.
• You pay per search. Every page of up to 10 results is a search against your plan (SerpApi doesn't count cached repeats within an hour).
• Results follow Google's layout. When Google changes its job results, the scraper has to catch up.

See CleanJobData vs SerpApi for a field-by-field comparison and Best Job APIs in 2026 for SerpApi's and JSearch's published plans.

If You Need Job Listings, Use a Job Data API

None of Google's products is a feed of other companies' jobs. If you're building a job board, a search feature or an analytics pipeline, you need a source that hands you the listings.

CleanJobData collects jobs directly from employer ATS platforms and career sites and returns them with structured locations, parsed salary, experience_level and the employer's own apply URL. It pairs naturally with the Google side: pull jobs from the API, render detail pages with JobPosting markup, and notify Google through the Indexing API.

curl "https://api.cleanjobdata.com/jobs?title=data%20engineer&location=US&max_age=7d" \
  -H "Authorization: Bearer $CLEANJOBDATA_API_KEY"

It doesn't include Google, Indeed, LinkedIn or Glassdoor data. Try it on the free Trial or read the quickstart.

FAQ

Does Google have a jobs API?

Not one that returns Google's job listings. Cloud Talent Solution searches jobs you upload, and JobPosting markup with the Indexing API publishes your own jobs to Google Search.

Is Google Cloud Talent Solution still available?

Yes. The v4 Job Search API is documented with no deprecation notice as of November 2026. Older versions (v2, v3, v3p1beta1 and v4beta1) were shut down in 2020 and 2021, and the latest release note is from December 2024.

How do I get my jobs on Google for Jobs?

Add JobPosting structured data to each job detail page, then notify Google through the Indexing API when jobs are posted, updated or removed. Google crawls the pages and decides whether to show them.

How can I get Google Jobs results as JSON?

Use a third-party SERP API such as SerpApi with engine=google_jobs. It scrapes Google's job results for a query and charges per search; it isn't a Google product.

Is the Indexing API a way to read Google Jobs data?

No. The Indexing API only accepts notifications about your own URLs so Google crawls or removes them. It never returns job listings.