ZipRecruiter Jobs Scraper

Tracking hiring on ZipRecruiter by hand gets old fast. You run the same searches, copy out pay ranges by hand, and half the time a posting is gone before you note it down. This scraper handles that part. Give it the roles and places you care about, and it hands back every matching posting as a tidy row: role title, employer, pay range, location, a direct link, and more. Turn on full details and it also opens each posting for the complete description, posted date, and work type. Run one search or a few hundred in a single pass.

What you get

Every posting comes back as one flat row, so the results drop straight into a sheet or database. Fields that ZipRecruiter doesn't show arrive as null rather than going missing, which keeps your columns lined up. Three groups of data per job:

• The role — roleTitle, employerName, jobLocation, remoteFriendly, quickApply, workType
• Pay — payRange (raw text) plus parsed payMin, payMax, and payPeriod
• Links and detail — listingUrl, listingId, employerUrl, roleDescription, postedDate, and the searchTermUsed / searchLocationUsed that produced each row

Quick start

1. Hit Try for free and open the input form.
2. Add your roles and keywords under Job search terms, one per line.
3. Add any cities and states under Search locations, or leave it blank to sweep nationwide and remote roles.
4. Turn on Pull full posting details if you want the complete description and posted date, set a Results limit, then press Start.
5. Export the dataset as JSON, CSV, Excel, or XML when the run finishes.

Use cases

• Salary benchmarking — pull live pay ranges for a role across dozens of real postings instead of relying on aggregate averages
• Recruiting research — see how rival employers word their openings and what they pay before you write your own
• Job board feeds — pipe fresh listings into your own app, spreadsheet, or database on a schedule
• Resume targeting — gather a stack of postings for one role and spot the requirements that keep showing up
• Labor market analysis — track which roles, employers, and locations are hiring over time

Input

Field	Type	Required	Description
jobSearchTerms	array of strings	Yes	Roles, skills, or keywords to look up. Each line runs its own search.
searchLocations	array of strings	No	Cities and states to cover; blank means a nationwide and remote sweep. Each location pairs with every term.
includeFullDetails	boolean	No	Open each posting for the full description, posted date, and work type. Adds one request per job. Default false.
resultsLimit	integer	No	Cap on total postings gathered across all terms and places. Default 50; up to 1000.
timeoutSeconds	integer	No	Seconds to wait on a single request before giving up. Default 90.

Example input

{
    "jobSearchTerms": ["customer success manager", "warehouse associate", "react developer"],
    "searchLocations": ["Chicago, IL", "Seattle, WA", "Remote"],
    "includeFullDetails": true,
    "resultsLimit": 50,
    "timeoutSeconds": 90
}

Output

Each posting becomes one row, and every field is always present — values ZipRecruiter doesn't publish come back as null so the dataset stays rectangular.

Example output

{
    "searchTermUsed": "react developer",
    "searchLocationUsed": "Seattle, WA",
    "roleTitle": "Senior React Developer",
    "employerName": "Northpoint Software",
    "jobLocation": "Seattle, WA",
    "remoteFriendly": true,
    "payRange": "$120K - $155K/yr",
    "payMin": 120000,
    "payMax": 155000,
    "payPeriod": "YEAR",
    "quickApply": true,
    "listingUrl": "https://www.ziprecruiter.com/c/Northpoint-Software/Job/Senior-React-Developer/-in-Seattle,WA?jid=9f2a71c4",
    "listingId": "9f2a71c4",
    "employerUrl": "https://www.ziprecruiter.com/co/Northpoint-Software/Jobs",
    "roleDescription": "We're hiring a Senior React Developer to lead front-end work on our customer platform...",
    "postedDate": "2026-06-22",
    "workType": "FULL_TIME",
    "collectedAt": "2026-06-30T09:15:00+00:00"
}

Output fields

Field	Type	Description
searchTermUsed	string	The keyword or role title that surfaced this listing
searchLocationUsed	string	The place value passed to this search; blank means nationwide
roleTitle	string	Headline of the advertised position
employerName	string	Company that posted the opening
jobLocation	string	City and state attached to the posting
remoteFriendly	boolean	True when the post is tagged remote or hybrid
payRange	string	Salary line exactly as printed, e.g. $40 - $75/hr
payMin	number	Lower salary figure parsed from the pay line
payMax	number	Upper salary figure parsed from the pay line
payPeriod	string	How pay is quoted: HOUR, YEAR, MONTH, or WEEK
quickApply	boolean	True when a one-click apply button is offered
listingUrl	string	Direct link to the posting on ZipRecruiter
listingId	string	ZipRecruiter's own job identifier from the link
employerUrl	string	Link to the company's ZipRecruiter profile
roleDescription	string	Full plain-text role write-up (only with full details on)
postedDate	string	ISO date the post went live (only with full details on)
workType	string	Arrangement such as FULL_TIME (only with full details on)
collectedAt	string	ISO timestamp marking when the row was captured

Tips for best results

• Start small. Run a handful of terms before launching a big batch — search format and pairing issues show up fast in the first few rows.
• Skip full details for speed. With Pull full posting details off, the scraper reads roughly 20 postings per page request. Turn it on only when you actually need the description, posted date, and work type, since it costs an extra request per job.
• Cap your spend with resultsLimit. Keep it low while you confirm the output fits your pipeline, then raise it for the full pull.
• Empty pay fields are normal. ZipRecruiter shows salary only when the employer lists it, so payMin, payMax, and payPeriod come back null on many postings.
• Raise timeoutSeconds if you see frequent timeout errors on slower proxy tiers.

How can I use ZipRecruiter jobs data?

How can I use the ZipRecruiter Jobs Scraper to benchmark salaries for a role? List the role under Job search terms, add the places you want under Search locations, and run the scraper. Each posting returns payRange along with parsed payMin, payMax, and payPeriod, so you can pull live pay figures from real openings rather than leaning on aggregate averages. Group the rows by location to see how pay shifts from one market to the next.

How can I export ZipRecruiter job listings to a spreadsheet? Run the scraper with your terms and locations, then export the dataset as CSV or Excel when it finishes. Every posting is one flat row with the role, employer, location, pay, and a direct link, so it opens cleanly in any spreadsheet tool — no cleanup or reformatting needed.

How can I collect full ZipRecruiter job descriptions in bulk? Turn on Pull full posting details before you start. The scraper then opens each posting and adds roleDescription, postedDate, and workType to every row. It's the right setting for resume targeting or recruiting research, where the wording of the description matters as much as the headline.

How can I monitor hiring trends on ZipRecruiter over time? Schedule the scraper to run on a fixed cadence with the same terms and locations. Because each row carries collectedAt, searchTermUsed, and searchLocationUsed, you can stack runs over weeks and watch which roles, employers, and markets are actively hiring.

Is it legal to scrape data?

Our actors are ethical and do not extract any private user data, such as email addresses or private contact information. They only extract what the user has chosen to share publicly. We therefore believe that our actors, when used for ethical purposes by Apify users, are safe.

However, you should be aware that your results could contain personal data. Personal data is protected by the GDPR in the European Union and by other regulations around the world. You should not scrape personal data unless you have a legitimate reason to do so. If you're unsure whether your reason is legitimate, consult your lawyers.

You can also read Apify's blog post on the legality of web scraping.

Support

Questions, feature requests, or a field you'd like added? Reach out at data.apify@proton.me and we'll get back to you.