ZipRecruiter is one of the largest job marketplaces in the United States, listing millions of active job postings from employers ranging from Fortune 500 companies to local small businesses. Its AI-driven matching engine and broad employer base make it a high-signal source of real-time labor market data — not just what jobs exist, but what skills, experience levels, and salary ranges employers are actively hiring for right now.
For researchers, recruiting firms, HR technology companies, and labor market analysts, ZipRecruiter represents an invaluable dataset. Unfortunately, the platform does not offer a public data API. Bulk access to job listings requires a scraping solution that handles the platform’s dynamic rendering, search pagination, and anti-automation measures at scale.
ZipRecruiter is a JavaScript-heavy application. Job search results are rendered client-side via React, and the underlying data is fetched from internal API endpoints that require session cookies, request fingerprinting, and specific header signatures to return valid responses. A raw HTTP request to a ZipRecruiter search URL returns a shell page with no listing data — the actual jobs load asynchronously after the browser executes initialization scripts.
The scale problem: ZipRecruiter search results are paginated at 20–25 listings per page with no straightforward way to jump to arbitrary pages for large result sets. Scraping the full result set for a broad query — say, “software engineer” in the United States — may involve navigating hundreds of pages of results with rate-limiting applied between requests. At the same time, ZipRecruiter applies bot detection at multiple layers: IP reputation scoring, behavioral fingerprinting on mouse and scroll events, and TLS fingerprint analysis. Standard automation frameworks trigger these defenses quickly without residential proxy infrastructure and browser-level stealth measures.
Individual job detail pages present additional challenges. Many fields visible on the job listing — full job description text, specific salary figures, application counts, and employer details — are not present in the search result cards. Accessing the full dataset requires a two-pass approach: first collecting listing URLs from search results, then fetching each job detail page individually. This doubles the request volume and doubles the surface area for detection.
ZipRecruiter also actively monitors for scraping activity and can temporarily suppress listings or redirect traffic from suspicious sources, meaning inconsistent results that look like data rather than errors. A production-grade scraper needs to detect and handle these silent failures to avoid corrupting datasets.
We maintain a ZipRecruiter Jobs Scraper on Apify that handles JavaScript rendering, multi-page result collection, and job detail extraction. You provide search queries and filters; it returns structured job listing data ready for analysis.
Search by keyword and location:
{
"searchQuery": "data engineer",
"location": "New York, NY",
"radius": 25,
"maxResults": 200,
"includeRemote": true
}Or target specific job types and experience levels:
{
"searchQuery": "machine learning engineer",
"location": "United States",
"jobType": "full_time",
"experienceLevel": "senior",
"datePosted": "last_7_days",
"maxResults": 500
}Each job listing returns a structured object:
{
"jobId": "j3q7b26t8kzc4mx9",
"title": "Senior Data Engineer",
"company": "Acme Analytics",
"companyUrl": "https://www.ziprecruiter.com/c/Acme-Analytics",
"location": "New York, NY",
"remote": false,
"hybrid": true,
"salaryMin": 130000,
"salaryMax": 175000,
"salaryCurrency": "USD",
"salaryPeriod": "annual",
"jobType": "Full-Time",
"experienceLevel": "Senior",
"datePosted": "2026-04-24",
"description": "We are looking for a Senior Data Engineer to join our growing data platform team...",
"requirements": [
"5+ years of experience with distributed data systems",
"Proficiency in Python and SQL",
"Experience with Apache Spark or Databricks",
"Strong understanding of data modeling principles"
],
"benefits": ["Health insurance", "401k matching", "Flexible PTO"],
"applicationUrl": "https://www.ziprecruiter.com/jobs/...",
"postedAgo": "3 days ago",
"applicantCount": "100+ applicants",
"url": "https://www.ziprecruiter.com/jobs/acme-analytics-senior-data-engineer"
}| Field | Type | Description |
|---|---|---|
jobId | string | ZipRecruiter internal job identifier |
title | string | Job title as posted by employer |
company | string | Hiring company name |
location | string | Job location (city, state) |
remote | boolean | True if fully remote |
salaryMin | integer | Minimum posted salary (if provided) |
salaryMax | integer | Maximum posted salary (if provided) |
jobType | string | Full-time, part-time, contract, etc. |
datePosted | string | Date the listing was posted |
description | string | Full job description text |
requirements | array | Extracted requirement bullet points |
applicantCount | string | Applicant count label shown on listing |
applicationUrl | string | Direct link to apply |
Output is available as JSON, CSV, or XLSX. You can schedule runs on Apify to monitor job postings in specific roles, locations, or companies on a daily or weekly cadence — useful for tracking hiring velocity over time or alerting when target companies open new positions.
The actor uses Pay Per Event pricing at $0.01 per job listing.
| Volume | Cost |
|---|---|
| 100 listings | $1.00 |
| 500 listings | $5.00 |
| 1,000 listings | $10.00 |
| Weekly monitor (200 listings × 4 weeks) | $8.00/month |
ZipRecruiter Jobs Scraper on Apify →
Apify has a free tier for testing. Sign up here if you do not have an account. The actor integrates with Apify’s scheduling, webhook, and dataset APIs so you can automate job market monitoring pipelines without managing any infrastructure.