Google Cloud Talent Solution API

Name: Cloud Talent Solution API
Brand: Cloud Talent Solution API
Availability: InStock

✓ Official Vendor SpecHR recruitingRecruiting Atsoauth216 EndpointsREST

For Agents

Create, search, and manage job postings with Google's job search ranking. Supports tenants, companies, jobs, batch operations, and client event tracking.

Install Jentic One Beta

Connect the Cloud Talent Solution API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Cloud Talent Solution API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Cloud Talent Solution API.

Create individual or batch job postings under a tenant and company

Run ranked job search with location filters, commute time, and seniority signals

Update or delete job postings in bulk with batchUpdate and batchDelete

GET STARTED

Start building with Cloud Talent Solution API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Cloud Talent Solution API for, with concrete tasks.

★ Power a careers site search

Employers and ATS vendors index their job inventory through Cloud Talent Solution and call jobs:search to render the careers site results page. Google's ranking model factors in title, description, location, commute time, and engagement signals, so candidates see relevant roles without the employer building a search stack.

Call POST /v4/{+parent}/jobs:search with query 'site reliability engineer' and locationFilters lat/lng for Dublin, then return the top 10 ranked job names.

Bulk job ingestion from an ATS

Large employers sync thousands of postings from an applicant tracking system into Cloud Talent Solution every day. Using POST /v4/{+parent}/jobs:batchCreate and batchUpdate keeps the search index fresh without paying per-call overhead, while batchDelete retires roles that are filled or expired.

Submit POST /v4/{+parent}/jobs:batchCreate with 50 job objects under a tenant and confirm the long-running operation completes successfully.

Track candidate engagement with client events

POST /v4/{+parent}/clientEvents records impressions, views, and application starts for individual job postings. Feeding events back to Cloud Talent Solution improves the relevance model over time and gives recruiting teams reliable funnel metrics.

When a candidate views a job, POST a clientEvents record with type IMPRESSION and the job resource name.

Agent-assisted recruiting through Jentic

A recruiting agent can use Jentic to search for relevant jobs, retrieve details, and log application events — all using natural language. Jentic surfaces the jobs:search and jobs.get operations so the agent can answer candidate questions without learning the projects.tenants resource path.

Search for nursing jobs in Boston with commute under 45 minutes via google_jobs_search and return company names and titles.

Key Endpoints

16 endpoints — cloud talent solution is google's hiring api for creating, indexing, and searching job postings with the same machine-learning relevance google applies to its own job search experience.

METHOD

PATH

DESCRIPTION

POST

/v4/{+parent}/jobs

Create a single job posting

POST

/v4/{+parent}/jobs:batchCreate

Create up to 200 job postings in one call

POST

/v4/{+parent}/jobs:search

Run a ranked search across job postings

GET

/v4/{+parent}/jobs

List job postings under a tenant

PATCH

/v4/{+name}

Update fields on an existing job posting

DELETE

/v4/{+name}

Delete a job posting

POST

/v4/{+parent}/companies

POST

/v4/{+parent}/clientEvents

Log a client engagement event

POST

/v4/{+parent}/jobs

Create a single job posting

POST

/v4/{+parent}/jobs:batchCreate

Create up to 200 job postings in one call

POST

/v4/{+parent}/jobs:search

Run a ranked search across job postings

GET

/v4/{+parent}/jobs

List job postings under a tenant

PATCH

/v4/{+name}

Update fields on an existing job posting

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Service account JSON keys are stored encrypted in the Jentic vault. Agents receive a short-lived OAuth 2.0 token scoped to https://www.googleapis.com/auth/jobs at call time, and the private key never reaches the agent context.

Intent-based discovery

Agents search Jentic with phrases like 'search jobs near a location' or 'create a job posting' and Jentic returns the matching projects.tenants.jobs operation with its full input schema, hiding Google's nested resource path.

Time to first call

Direct integration: 1-2 days to wire up the service account, build the projects.tenants.jobs request paths, and handle long-running batch operations. Through Jentic: under 30 minutes — search, load, execute.

FAQs

Specific to using Cloud Talent Solution API through Jentic.

What authentication does the Cloud Talent Solution API use?

OAuth 2.0 with the https://www.googleapis.com/auth/jobs scope, typically issued to a Google Cloud service account in the project that owns the tenant. Through Jentic the service account JSON is encrypted in the vault and only a short-lived access token is exposed to the agent.

Can I search jobs by commute time with this API?

Yes. The jobs:search endpoint accepts a commuteFilter with startCoordinates, travelDuration, and roadTraffic so an agent can return only jobs reachable within, for example, 45 minutes during morning traffic.

What are the rate limits for the Cloud Talent Solution API?

The default per-project quota is 600 read requests and 100 write requests per minute, with batch operations counting as a single request. Higher quotas can be granted on request through the Google Cloud console for high-volume careers sites.

How do I run a ranked job search through Jentic?

Run jentic search 'search jobs near a location' to surface POST /v4/{+parent}/jobs:search, then jentic execute with body containing requestMetadata, jobQuery.query, and jobQuery.locationFilters. Jentic returns the ranked matchingJobs list.

Does the API support batch updates?

Yes. POST /v4/{+parent}/jobs:batchCreate, jobs:batchUpdate, and jobs:batchDelete each accept up to 200 job objects per call and return a long-running operation that an agent can poll for completion.

Is Cloud Talent Solution the same as Google for Jobs?

No. Google for Jobs is the consumer search experience that surfaces JobPosting structured data from any indexed site. Cloud Talent Solution is a paid API for indexing and searching your own job inventory with Google's ranking model.

Google Cloud Talent Solution API

Connect the Cloud Talent Solution API to your agent

Capabilities

Start building with Cloud Talent Solution API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs