Google Cloud Talent Solution API
Browse all Google APIs41
AI ReadinessFoundational (D-)41/100
Official vendor OpenAPI document · agent-readyHR 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.
Use for: I need to post a new job listing to our careers site, Search for software engineering jobs within 30 km of San Francisco, Find all jobs at a specific company in our tenant, Retrieve the full posting for a job by resource name
Not supported: Does not handle candidate pipelines, interview scheduling, or offer letters - use only to index, search, and manage job posting data.
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. It exposes operations for tenants, companies, jobs, and client events under the projects.tenants resource hierarchy, including batch create, update, and delete for high-volume careers sites. The API is designed for ATS providers and large employers that need ranked search across their own job inventory.
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.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgoogleapis.com%2Fjobs" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgoogleapis.com%2Fjobs" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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
Register companies that own job listings within a tenant namespace
Log client events such as impressions and applications for relevance feedback
Retrieve a single job posting by resource name with full attribute payload
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
Register a company within a tenant
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
DELETE
/v4/{+name}
Delete a job posting
POST
/v4/{+parent}/companies
Register a company within a tenant
POST
/v4/{+parent}/clientEvents
Log a client engagement event
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
C
Cloud Talent Solution API
- Foundational (D-)41/100
55
Foundational Compliance56
Developer Experience & Jentic Compatibility19
AI-Readiness & Agent Experience94
Agent Usability63
Security60
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
55
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: CSignals: 4
70%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
50%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
56
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: CSignals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
25%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
19
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
77%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
0%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
0%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
63
Security
Trust, risk posture, and security compliance.
Grade: B-Signals: 1
62%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
60
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: B-Signals: 1
60%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Cloud Talent Solution API by hand means configuring service-account OAuth2, narrowing to the jobs scope, refreshing tokens, and learning its nested tenant and job resource paths yourself. Through Jentic you install once, import the Cloud Talent Solution API from the API Directory, store the credential once, and your agent calls it.
Permission scoping
The tenant parent and job name travel in the URL path (/v4/{parent}/jobs, /v4/{name}), so a rule can pin your agent to one project or tenant's postings: it indexes and searches jobs under that parent and nothing else. You choose the operations it may call, so destructive ones like job deletion are not included unless you add them.
Credential isolation
Your Cloud Talent Solution service-account credential is stored once, encrypted, by your own Jentic One instance and injected at execution time as a short-lived access token scoped to jobs. The private key never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'search jobs near a location' or 'create a job posting', and Jentic returns the matching jobs operation with its input schema so the agent calls the right endpoint without browsing Google's nested resource paths.
Related APIs
Alternatives and complements available in the Jentic catalogue.
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.
Can I limit what my agent is allowed to do with the Cloud Talent Solution API?
Yes. Because you self-host Jentic One, your own rules decide which Cloud Talent Solution operations and credentials the agent may use. Since the tenant parent and job name travel in the URL path (/v4/{parent}/jobs and /v4/{name}), a rule can pin the agent to a single project or tenant so it only indexes and searches postings under that parent. You also choose the operations it may call, so you can allow jobs:search and jobs.get while withholding destructive ones such as job deletion or batchDelete.
GET STARTED