ZipRecruiter Job Scraper

ZipRecruiter Job Scraper creates a structured dataset of job listing records collected from ZipRecruiter. Each dataset item describes one job posting and can include the job title, company name, job URL, full description, employment type, posting dates, location fields, geo coordinates, company links, and the source query that produced it. Query the source using search keywords combined with optional locations and a search radius, control the result limit with maxJobs, and retrieve records through the Apify Dataset API or export them as JSON, CSV, Excel, XML, or another supported format.

Dataset at a glance

Property	Value
Source	ziprecruiter.com
Record unit	One job listing
Input methods	searchQueries + locations + radius (or startUrls)
Main identifiers	url
Delivery	Apify Dataset and API
Export formats	JSON, CSV, Excel, XML
Update model	Fresh records per Actor run
Pricing	$1 per 1,000 jobs

Coverage and available records

The Actor returns job listings from ZipRecruiter search results. Supported coverage includes:

• Search results built from each search keyword, optionally combined with each location.
• A search radius in miles (0 = any distance).
• Direct search URLs via startUrls as an override for power users.
• Title, company name, description, employment type, and posting dates.
• Structured location fields (locality, region, country, postal code) and geo coordinates.
• Company website and social links, and a direct-apply flag.

When both searchQueries and startUrls are provided, the search queries take precedence. Fields that ZipRecruiter does not provide on a listing are returned empty or null rather than guessed.

Data dictionary

Field	Type	Nullable	Description	Example
title	string	No	Job posting title	"Web Developer"
companyName	string	Yes	Hiring company name	"Acme GmbH"
url	string	No	Job posting URL	"https://www.ziprecruiter.com/job/..."
description	string	Yes	Full job description	"We are looking for..."
employmentType	string	Yes	Employment type	"FULL_TIME"
datePosted	string	Yes	Posting date	"2025-07-10"
validThrough	string	Yes	Posting expiry date	"2025-08-09"
locationLocality	string	Yes	City	"Berlin"
locationRegion	string	Yes	State/region	"Berlin"
locationCountry	string	Yes	Country	"DE"
locationPostalCode	string	Yes	Postal code	"10115"
latitude	number	Yes	Location latitude	52.52
longitude	number	Yes	Location longitude	13.405
companyUrl	string	Yes	Company website URL	"https://www.acme.com"
companySameAs	string	Yes	Company social/linked URL	"https://www.linkedin.com/company/acme"
directApply	boolean	Yes	Whether direct application is supported	true
sourceQuery	string	Yes	Search query that produced the record	"Web Developer"

The most stable field for deduplication is url.

Example dataset record

{
  "title": "Web Developer",
  "companyName": "Acme GmbH",
  "url": "https://www.ziprecruiter.de/job/abc123",
  "employmentType": "FULL_TIME",
  "datePosted": "2025-07-10",
  "validThrough": "2025-08-09",
  "locationLocality": "Berlin",
  "locationRegion": "Berlin",
  "locationCountry": "DE",
  "locationPostalCode": "10115",
  "latitude": 52.52,
  "longitude": 13.405,
  "companyUrl": "https://www.acme.com",
  "companySameAs": "https://www.linkedin.com/company/acme",
  "directApply": true,
  "description": "We are looking for a Web Developer to join our team.",
  "sourceQuery": "Web Developer"
}

This record was produced by a search for Web Developer in Berlin with radius 0.

Query and input reference

Input	Type	Required	Default	Accepted values	Description
searchQueries	array of strings	No	[]	Job titles, skills, or keywords	Primary input for building searches.
startUrls	array of URLs	No	[]	Full ZipRecruiter search URLs	Optional override; ignored when searchQueries is provided.
locations	array of strings	No	[]	City, state, or country names	Combined with each search query.
radius	integer	No	0	0–200 miles	Search radius from the location.
maxJobs	integer	No	0	0 (unlimited) or any positive integer	Maximum number of job listings; 0 means unlimited.
proxyConfiguration	object	No	Apify Residential	Apify proxy settings	Proxy configuration.

Minimal request:

{
  "searchQueries": ["Web Developer"]
}

Request with location and result limit:

{
  "searchQueries": ["Web Developer"],
  "locations": ["Berlin"],
  "radius": 0,
  "maxJobs": 50
}

Retrieve the data through the API

1. Start the Actor with a JSON input containing searchQueries (and optional locations).
2. Wait for the run to finish, or use the synchronous run endpoint.
3. Retrieve items from the run's default dataset.
4. Paginate or export the dataset.

Example in Python:

from apify_client import ApifyClient

client = ApifyClient("YOUR_API_TOKEN")
run = client.actor("datascrapers/ziprecruiter-scraper").call(run_input={
    "searchQueries": ["Web Developer"],
    "locations": ["Berlin"],
    "maxJobs": 50,
})
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item["title"], item["companyName"])

For other languages, use the generated API tab in the Apify Console. Never place a real token in a URL or example.

Data quality and record handling

• Fields not present on a listing are returned empty or null; completeness varies by listing.
• Location and geo coordinates are populated when ZipRecruiter provides structured location data.
• Source-side changes to ZipRecruiter's listing markup can reduce field completeness.
• The Actor does not perform internal cross-run deduplication; each run is a fresh dataset.
• The recommended external deduplication key is url.
• Failed requests are retried and logged; they do not abort the whole run.

Export and pipeline examples

Destination	Recommended method	Typical use
PostgreSQL/Supabase	Dataset API or webhook consumer	Job market database
Google Sheets	Apify integration	Manual job tracking
S3/cloud storage	Scheduled export or integration	Nightly job snapshot

Pricing and cost examples

The Actor charges per job record written to the dataset, plus a one-time Actor start event. The per-result rate is $0.001.

Jobs	Estimated base cost
1,000	$1.00
10,000	$10.00

Estimates depend on the verified pricing model and any selected proxy options. Standard Apify plan discounts may apply.

Limitations and responsible data use

• Collects publicly accessible ZipRecruiter job listings only.
• Availability depends on source-site uptime and any listing changes.
• Some fields (employment type, dates, coordinates) are conditional and may be missing.
• No historical snapshots are stored unless you keep the datasets yourself.
• You are responsible for complying with ZipRecruiter's terms and applicable law when using the data.

Dataset questions

What does one dataset item represent?

One ZipRecruiter job listing, including title, company, description, location, employment type, and posting dates.

Which field should I use as a unique identifier?

url is the stable job posting URL and is the recommended deduplication key.

Are fields nullable or conditional?

Yes. employmentType, datePosted, validThrough, location fields, and coordinates depend on the individual listing.

Can I retrieve the records as CSV or JSON?

Yes. The dataset can be exported as JSON, CSV, Excel, or XML from the Apify Console or Dataset API.

How do I paginate large datasets?

Use the Dataset API pagination, or raise maxJobs (set 0 for all results) to collect more records in a single run.

Does the Actor return historical data?

No. Each run returns listings visible at run time.

What counts as a billable result?

Each job record written to the dataset is one billable result, at $0.001 per job.

Related datasets from Data Scrapers

• StepStone Jobs Scraper — European job postings for cross-board market coverage.
• Glassdoor Jobs Scraper — job records with employer ratings that can be joined to listings.
• LinkedIn Company Scraper — company profile records for employer enrichment.
• LinkedIn Profile Scraper — professional profile records for the same talent-market use cases.

Data Scrapers support

Need an additional field, record type, or export workflow? Contact Data Scrapers at stardustspotlight@gmail.com. Include a sample source URL, required fields, expected record volume, and preferred delivery format.