Google Jobs Search API
/api/google/jobs
Scrape Google Jobs search results with q, hl/gl, Google domain, uds filters, and next_page_token pagination when available
Scrape Google Jobs results through a simple API that returns structured JSON for job titles, companies, locations, descriptions, returned filter options, apply links, and pagination tokens when available. Search by q, hl/gl, Google domain, and Google Jobs uds filter strings without maintaining your own browser scraper.
Try it now
Use the first endpoint in this API family with a Scrappa API key. Every account includes 500 free monthly credits, so you can validate the response shape before buying credits.
curl -X GET "https://scrappa.co/api/google/jobs?q=software+engineer+Berlin&hl=en&gl=de" \
-H "Accept: application/json" \
-H "X-API-KEY: YOUR_API_KEY"
{
"jobs_results": [
{
"position": 1,
"title": "Senior Software Engineer",
"company_name": "Delivery Hero",
"location": "Berlin, Germany",
"via": "LinkedIn",
"extensions": ["3 days ago", "Full-time"],
"detected_extensions": {
"posted_at": "3 days ago"
},
"job_id": "base64_encoded_job_id",
"link": "https://www.linkedin.com/jobs/...",
"description": "Join our engineering team to build scalable systems...",
"job_highlights": [
{
"title": "Qualifications",
"items": ["PHP", "Laravel", "JavaScript"]
}
]
}
],
"filters": {
"date_posted": [
{"label": "Last week", "value": "week"}
],
"employment_type": [
{"label": "Full-time", "value": "1"}
]
},
"search_information": {
"query_displayed": "software engineer Berlin",
"total_results": 10
},
"next_page_token": "base64_cursor_when_available"
}
Structured data for real applications. Here are some ideas.
Use Scrappa as a Google Jobs scraper API when you need structured listings from the Google Jobs vertical without running browsers, parsing HTML, or managing proxy logic in your application.
Power search experiences with q-based role queries, hl/gl localization, Google domain selection, returned Google Jobs filter options, uds refinements, and response pagination when a token is available.
Analyze hiring trends, employer activity, skills, locations, posting freshness, and source coverage using normalized job listing fields from Google Jobs responses.
Monitor new postings for specific titles, locations, employment types, and filter combinations, then feed structured JSON into CRMs, ATS workflows, sourcing tools, and alerts.
Build job discovery tools for students and job seekers using public job listings with company names, locations, descriptions, highlights, links, and apply sources.
Google Jobs API
Scrappa is built for teams searching for a Google Jobs API, Google Jobs scraper, job search API, or a practical way to scrape Google Jobs without maintaining extraction infrastructure. Send a role, keyword, or location phrase in q, localize results with hl and gl, target a Google domain, reuse Google-provided uds filter strings, and continue result collection with next_page_token when pagination is available.
Start free with 500 monthly credits and no credit card before moving to flat $0.20 per 1,000 request pricing.
Use q for role and keyword searches such as software engineer jobs, remote marketing manager, or nurse jobs near Berlin.
Localize Google Jobs searches with hl, gl, and google_domain when you need language, country, or domain-specific results.
Refine job searches with uds values returned in the response filter section.
Parse structured JSON fields including jobs_results, title, company_name, location, via, extensions, detected_extensions, job_id, share_link, link, description, job_highlights, filters, and search_information.
Use next_page_token for follow-up requests when the response exposes a pagination token for the current search.
The Google Jobs API starts with a q query and supports localization controls for language, country, and Google domain. Include location terms directly in the query when you need city or region-specific job searches.
Open Google Jobs API docsResponses include structured job result fields plus filter data. Use uds values returned by Google Jobs and next_page_token when available to refine searches and continue collecting result sets without reverse-engineering the Google Jobs page yourself.
Compare Scrappa pricingEverything you need in one API.
/api/google/jobs
Scrape Google Jobs search results with q, hl/gl, Google domain, uds filters, and next_page_token pagination when available
See how Scrappa compares to the official API.
| Feature | Scrappa | Google Jobs (official - no API) |
|---|---|---|
| API available | No public API | |
| Structured JSON data | Not available | |
| Programmatic search | Manual only | |
| Filters and pagination | Manual only | |
| Apply/source links | Yes (manual) | |
| Bulk access | ||
| Free tier | 500 credits/month | N/A |
| Pricing | $0.20/1k requests | N/A |
No. Google Jobs is a search experience, not a public developer API. Scrappa provides a Google Jobs API and job scraper API that turns public Google Jobs results into structured JSON for applications, analytics, sourcing, and monitoring workflows.
Call GET /api/google/jobs with an API key and a q query such as software engineer jobs. You can add hl, gl, google_domain, uds, and next_page_token parameters to localize, refine, and paginate results when those values are available. The response returns structured JSON instead of raw HTML.
Yes. Every Scrappa account includes 500 free credits per month with no credit card required. Use the free allowance to test Google Jobs API responses, filters, pagination behavior, and integration code before buying credits.
Scrappa uses flat usage-based pricing: $0.20 per 1,000 requests after the free monthly credits. There are no per-listing fees or required monthly job-search API subscription tiers.
Yes. Pass uds values returned by Google Jobs for dynamic filter refinements, and use next_page_token for follow-up requests when a response exposes a pagination token.
Responses include jobs_results with title, company_name, location, via, extensions, detected_extensions, job_id, share_link, link, description, and job_highlights when available. Responses can also include filters, search_information, service metadata, and next_page_token for pagination.